Ok, there is an open ticket for this one already: http://code.djangoproject.com/ticket/6809
-al On Apr 30, 8:34 pm, Alrex <[EMAIL PROTECTED]> wrote: > *Correction: > > I run a debug on BaseForm and can say that the error does get appended > to the field named '__all__' ...but it seems that the newforms-admin > form doesn't get the error message. > > -al > > On Apr 30, 8:22 pm, Alrex <[EMAIL PROTECTED]> wrote: > > > As per the doc: > > > """Note that any errors raised by your Form.clean() override will not > > be associated with any field in particular. They go into a special > > “field” (called __all__), which you can access via the > > non_field_errors() method if you need to.""" > > > I can confirm that my ModelForm-based class raises a > > forms.ValidationError in clean() method. > > The non_field_errors() is empty (empty ErrorList) even when error is > > raised. No error message is displayed on top of my newforms-admin form > > as it should to my understanding. > > > -Alen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
