mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-08-04 19:08:28 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 4

Fixed #12053 - form examples don't validate according to w3c

Browse source 
Thanks to skyl for the report.



git-svn-id: http://code.djangoproject.com/svn/django/trunk@12086 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Luke Plant 2010-01-04 21:55:52 +00:00
parent 77e27e7de7
commit 48edb177ed
8 changed files with 19 additions and 19 deletions
Download patch file Download diff file Expand all files Collapse all files

8
docs/topics/forms/modelforms.txt
View file

@ -705,14 +705,14 @@ There are three ways to render a formset in a Django template.
First, you can let the formset do most of the work::
<form method="POST" action="">
<form method="post" action="">
{{ formset }}
</form>
Second, you can manually render the formset, but let the form deal with
itself::
<form method="POST" action="">
<form method="post" action="">
{{ formset.management_form }}
{% for form in formset.forms %}
{{ form }}
@ -725,7 +725,7 @@ form as shown above. See the :ref:`management form documentation
Third, you can manually render each field::
<form method="POST" action="">
<form method="post" action="">
{{ formset.management_form }}
{% for form in formset.forms %}
{% for field in form %}
@ -738,7 +738,7 @@ If you opt to use this third method and you don't iterate over the fields with
a ``{% for %}`` loop, you'll need to render the primary key field. For example,
if you were rendering the ``name`` and ``age`` fields of a model::
<form method="POST" action="">
<form method="post" action="">
{{ formset.management_form }}
{% for form in formset.forms %}
{{ form.id }}