Thanks required=False is what I needed :). "ImageField is not required as expected" Isn't that what you want? :) Yes that is exactly what I wanted but also wanted to display the actual <img> setting the required=False allows me to have my cake and eat it too :). Not sure why required vs blank, null slipped my mind.
PS: It gives great JOY :D On Wednesday, December 12, 2012 1:39:36 PM UTC-8, Chris Cogdon wrote: > > > > NOTE: I tried adding null=True, blank=True to forms.ImageField however I >> get errors __init__() got an unexpected keyword argument so I guess I can't >> use them options. If I comment out the def formfield_for_dbfield(self, >> db_field, **kwargs): then the ImageField is not required as expected. >> > > "ImageField is not required as expected" Isn't that what you want? :) > > Anyway, the attribute for allowing a FormField to be "left blank" is > required=False... blank=True and null=True are for ModelFields > > If that knowledge doesn't give you any joy, try constructing a simple > model that is not inherited from AbstractBaseUser... does that still end up > having the picture be required? > > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/csQYMquCKr0J. 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.
