Hello Pierre. I recently came across the exact same problem (and for the exact same reason)
I don't think my solution was any less ugly that yours. I modified fieldset.html to look for a specific fieldset name. Anything in that fieldset is displayed in a manner which honors the hidden field property. (so still a hack!) Andy On May 7, 10:01 am, PierreR <p.radermec...@gmail.com> wrote: > Thanks for your reply. > > My intention is to use this field as a version/timestamp to implement > a form of optimistic locking. I need to receive it back from the user > through a form and check it against the current version/timestamp of > the updated record. > > I don't think "exclude" will work for me. > > > > > Hmm. Does the field need to be in the form at all? You could just add > > it to the 'exclude' tuple in the ModelAdmin declaration, then it won't > > show up. > > -- > > DR. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
