1
0
mirror of https://github.com/django/django.git synced 2025-06-05 11:39:13 +00:00

Revised the text in the 'Using a form in a view' section.

This commit is contained in:
Audrey Roy 2012-06-07 20:06:47 +02:00 committed by Aymeric Augustin
parent d2ad3b0f96
commit 3c05b500a5

View File

@ -104,25 +104,29 @@ The standard pattern for processing a form in a view looks like this:
}) })
There are three code paths here: There are three possible code paths here:
1. If the form has not been submitted, an unbound instance of ContactForm is +------------------+---------------+-----------------------------------------+
created and passed to the template. | Form submitted? | Data? | What occurs |
2. If the form has been submitted, a bound instance of the form is created +==================+===============+=========================================+
using ``request.POST``. If the submitted data is valid, it is processed | Unsubmitted | None yet | Template gets passed unbound instance |
and the user is re-directed to a "thanks" page. | | | of ContactForm. |
3. If the form has been submitted but is invalid, the bound form instance is +------------------+---------------+-----------------------------------------+
passed on to the template. | Submitted | Invalid data | Template gets passed bound instance |
| | | of ContactForm. |
+------------------+---------------+-----------------------------------------+
| Submitted | Valid data | Valid data is processed. Redirect to a |
| | | "thanks" page. |
+------------------+---------------+-----------------------------------------+
The distinction between **bound** and **unbound** forms is important. An unbound The distinction between :ref:`ref-forms-api-bound-unbound` is important:
form does not have any data associated with it; when rendered to the user, it
will be empty or will contain default values. A bound form does have submitted
data, and hence can be used to tell if that data is valid. If an invalid bound
form is rendered it can include inline error messages telling the user where
they went wrong.
See :ref:`ref-forms-api-bound-unbound` for further information on the * An unbound form has no data associated with it. When rendered to the user,
differences between bound and unbound forms. it will be empty or will contain default values.
* A bound form has submitted data, and hence can be used to tell if that data
is valid. If an invalid bound form is rendered, it can include inline error
messages telling the user what data to correct.
Handling file uploads with a form Handling file uploads with a form
--------------------------------- ---------------------------------
@ -294,7 +298,7 @@ templates:
The field's label wrapped in the appropriate HTML ``<label>`` tag, The field's label wrapped in the appropriate HTML ``<label>`` tag,
e.g. ``<label for="id_email">Email address</label>`` e.g. ``<label for="id_email">Email address</label>``
``{{ field.value }}`` ``{{ field.value }}``
The value of the field. e.g ``someone@example.com`` The value of the field. e.g ``someone@example.com``
``{{ field.html_name }}`` ``{{ field.html_name }}``