Referencing Form Field Errors Lists in Views

I'm trying to reference errors on a new form. In the html file code I reference them as "{{ form.fieldname.errors }}". How do I reference those same field's errors lists in a view before I display the screen? My goal here is to assign the focus of the screen which is about to be displayed to be the

Form Field References When Writing Field Validators

I'm writing a new field validator and I don't want it to raise an error if another field on the same form is not set to a certain value. When I reference the other field which I'm not editting with this validator I get this error: global name 'rptlist' is not defined So can I reference the othe

Documentation Checked But Unclear: How to supress form.errors from views when needed?

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

Screen Fields and Dropdowns Not Capturing Changes To Data on Edit Screen

I have a screen with a form on it and the text fields values and the dropdown box selected values that are changed do not appear to be posted back to the view. How is this possible? When I go to the screen originally I see all of the data that supposed to be there (often times much of it is from th

Need help: request.POST.copy() ?

I need to know when I can or should use request.POST.copy() when processing screens, as opposed to when not to use it. I've used it some, on one screen in particular, which seems to work fine for displaying the data that I want to display, when I put the data on the screen programatically from with

Re: Need help: request.POST.copy() ?

en I try to write it to the database, but nothing new is being saved, so that's why I'm wondering why no new data is being saved. On Mar 31, 8:07 pm, Sam Walters wrote: > Hi hank23 > request.POST would be immutable. > > "QueryDict instances are immutable, unless you

Re: Need help: request.POST.copy() ?

. On Mar 31, 8:24 pm, hank23 wrote: > Currently I have logic in place that makes a copy of request.POST so > it can put data from a record using a key, gotten from the previous > bunch of POSTed data, on the screen for display purposes. This all > works fine. But when I go in

Re: Need help: request.POST.copy() ?

t;             return render_to_response('contact.html', { 'form':form }, > context_instance=RequestContext(request)) >     form = ContactEmailForm() >     return render_to_response('contact.html', { 'form':form }, > context_instance=RequestContext

Need Help Understanding How To Use Built-In Authentication

I'm trying to understand the authentication built-in to django and have some questions. Since the built-in authentication seems to provide many if not all of the forms and views needed, then do I need to code anything but calls to those views, from my own views, which will pass the various bits of

<    1   2