Yes. First thanks for the response. I'm doing some experimenting with the forms and well as the requests and possibly reusing them as much as possible, and one thing I thought I'd try was to reuse values from a previous screen which some of the same fields names and types, so that when the new screen comes up as much data as possible has already been formatted on the screen and therefore requires fewer user keystrokes. The actual issue I seem to be having is when I display the new screen for the first time, but with the previously POSTed information it seems to want to display errors, which I can understand, because since it thinks it's not the first time in that it should display errors, when there is no data in one or more of the required fields on the screen. I think I have it figured out how to get around this unless there are some pitfalls, in doing this a little differently, which I'm unaware of. Thanks again.
-----Original Message----- From: django-users@googlegroups.com [mailto:django-users@googlegroups.com] On Behalf Of Sam Walters Sent: Monday, April 04, 2011 1:46 AM To: django-users@googlegroups.com Subject: Re: Documentation Checked But Unclear: How to supress form.errors from views when needed? I dont understand so you render a view with a form once and you get form errors on the initial view? Or Is there a POST/GET with formdata being submitted generating this issue? *which would be by design as fas as i can tell you want form verification to work Note: http://docs.djangoproject.com/en/1.3/topics/forms/ If you are binding data to a form for a view and rendering it im pretty sure you will see form errors if you leave fields blank etc. cheers sam_w On Thu, Mar 31, 2011 at 8:10 AM, hank23 <hversem...@stchas.edu> wrote: > I have an edit screen with more than a dozen fields on it of various > types (text/CharField, select/CharField, date/DateField). When I > refresh the screen sometimes I want to suppress all of the field > required errors generated by empty fields prior to the refresh > actually taking place. So far I have not found anything that works. I > know in a view that I can check if there are errors for particular > fields(like this if form.errors.has_key('title') : > titleerrors = len(form.errors['title'] titleerrors = > str(titleerrors))) and then display the counts on the screen, but I > have not figured out how to suppress them yet once I know they exist. > I do not believe that I can suppress them at the form level in > forms.py, in an overridden clean() method, without suppressing them > all of the time, which is not my intent. Thanks for the help. > > -- > 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. > > -- 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. !DSPAM:4d996ba5317541655416946! -- 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.
