summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRussell Keith-Magee <russell@keith-magee.com>2007-04-01 01:25:01 +0000
committerRussell Keith-Magee <russell@keith-magee.com>2007-04-01 01:25:01 +0000
commitf271e0896bb74dd06a10d8de3221ce34c8e4d9dc (patch)
treecda244de1ff50cb522ae9997673c06c1f30d1773
parent9191fa1f644481d2e9a0495f9585f9bf1e83d87e (diff)
Fixed #2841 -- Clarified documentation on procedure for field validation. Thanks, dave@avaragado.org.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@4886 bcc190cf-cafb-0310-a4f2-bffc1f526a37
-rw-r--r--docs/forms.txt8
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/forms.txt b/docs/forms.txt
index f76f6d27ef..ce1010235f 100644
--- a/docs/forms.txt
+++ b/docs/forms.txt
@@ -517,10 +517,10 @@ to put punctuation at the end of your validation messages.
When are validators called?
---------------------------
-After a form has been submitted, Django first checks to see that all the
-required fields are present and non-empty. For each field that passes that
-test *and if the form submission contained data* for that field, all the
-validators for that field are called in turn. The emphasized portion in the
+After a form has been submitted, Django validates each field in turn. First,
+if the field is required, Django checks that it is present and non-empty. Then,
+if that test passes *and the form submission contained data* for that field, all
+the validators for that field are called in turn. The emphasized portion in the
last sentence is important: if a form field is not submitted (because it
contains no data -- which is normal HTML behavior), the validators are not
run against the field.