I just found out that they had removed the 0.96 documentation. The documentation can be found here http://web.archive.org/web/*/http://www.djangoproject.com/documentation/0.96/
Instead you can redefine the full_clean() method of the Form and return different data in the exception and set multiple error fields. Or let the clean methods return a dictionary with clean data and errors. Based on the return type do different things. And in the errors part specify for which fields you want to set which errors. You can use the original method as a template. 2011/2/3 Jachin Rupe <jachin.r...@gmail.com>: > It worked great with one caveat. When I raise an error I can only attach it > to one form field. > Say I wanted to attach the error message to both the start and end date > field. Is there a way to do that? > It looks like one of the fields gets "cleaned" before the other one, so what > ever one gets cleaned second will have the error message attached to it, > better then what I had before, but maybe that just doesn't work in 0.96. > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
