On Sat, Oct 18, 2008 at 12:20 PM, Rob Goedman <[EMAIL PROTECTED]> wrote: > I couldn't find this in the ticket list. Has anybody else encountered/ > tried this?
This is really sort of intended behavior; auto_now and auto_now_add on a model field implicitly set "editable=False", which means it's not meant to ever be shown in a form (since user input will always be disregarded in favor of the automatic value). As a result, things like ModelForm and the admin which automatically generate forms for you will refuse to include these fields (since they skip any field with editable=False), which is most likely what's causing your problem. The answer is not to try to display a form field for something which has auto_now=True or auto_now_add=True. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
