On Tue, 2008-07-22 at 15:20 -0700, John-Scott wrote: > All, > > I had previously been using a bit of a hack (thought I found examples > of this on the mailing list, but can't find any evidence now) so that > I could actually associated field specific errors with the actual > field instead of having everything stuffed into __all__ / > non_field_errors. > > The hack went something like this: > > class MyForm(forms.Form): > field_A = forms.SomeField() > # many other fields etc. > field_Z = forms.SomeField(required=False) # not required in > isolation, but required if field_A... > > def clean(self): > if 'field_A' in self.cleaned_data and 'field_Z' not in > self.cleaned_data: > self.errors['field_Z'] = forms.util.ErrorList([u"Field Z > is required if-and-only-if Field A has input, and passes validation"]) > return self.cleaned_data > > I have a very long complicated form with many interrelated fields, so > it helps to have the errors physically near the fields that need > attention, rather than just say at the top "These 5 field names had > errors, now go find the fields!" (I wish the form were more sane, but > I have no control over this, I just have to deal as best I can). > > Obviously the first step is to stop using the hack,
Well, no. Why is this a hack? You have multi-field cleaning to do, so Form.clean() is the first place it's valid to do that, since all the fields will be available. You have access to self._errors in the subclass if you want to adjust it like this. Your usability case is thought out as being something that works (and I have to say that I do the same thing for inter-related stuff). So I'm not granting your premise here. Aside from "my greengrocer said this was a bad idea and I should buy more milk", so you thought you'd remove this, what is the actual problem you're having? Your setup looks like something workable to me, so is there something else that's a problem? Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
