let's make an example: in the datetime fields of the forms there will only be a time, which is ok for the user. the date will be added later by some background logic, for convenience.
practically: - the user enters "0300" in the datetime field. - I make "0300" into date=0, time=03:00, valid field. if you have any other idea how to do this - don't hesitate :) . and maybe (hopefully) this will also solve the mysteriously vanished datetime values. Thanks! Axel. 2011/2/5 Shawn Milochik <sh...@milochik.com> > What exactly are you trying to accomplish? I'm not sure overriding is_valid > is a good idea; it's not a part of the validation -- it's how a model knows > that the validation was successful. > > In your sample view, you're calling is_valid on the formset, not the forms > in the formset. That would explain why your 'is_valid' is never called. > > You can iterate through the formset to get at the actual form instances > inside. > > Shawn > > -- > 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<django-users%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > -- 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.
