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

Edited docs/topics/forms/index.txt changes from [9569] and fixed a typo in the visible_fields() docstring

Browse source 
git-svn-id: http://code.djangoproject.com/svn/django/trunk@9592 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Adrian Holovaty 2008-12-08 04:07:42 +00:00
parent 33c0f0de67
commit 352efd1893
2 changed files with 13 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

17
docs/topics/forms/index.txt
View file

@ -304,16 +304,17 @@ templates:
Looping over hidden and visible fields
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If you are manually laying out a form in a template, you will often want to
work with any hidden fields in a single loop and then treat the visible fields
differently. For example, since hidden fields don't display anything, putting
their error messages "next to" the field isn't going to be very clear to the
reader. So you need to handle errors for those fields a bit differently.
If you're manually laying out a form in a template, as opposed to relying on
Django's default form layout, you might want to treat ``<input type="hidden">``
fields differently than non-hidden fields. For example, because hidden fields
don't display anything, putting error messages "next to" the field could cause
confusion for your users -- so errors for those fields should be handled
differently.
Django provides two methods on a form that allow you to loop over the hidden
and visible fields independently: ``hidden_fields()`` and
``visible_fields()``. In a template, you might use these like this (this is a
modification of an earlier example)::
``visible_fields()``. Here's a modification of an earlier example that uses
these two methods::
<form action="/contact/" method="POST">
{% for field in form.visible_fields %}
@ -336,7 +337,7 @@ modification of an earlier example)::
This example does not handle any errors in the hidden fields. Usually, an
error in a hidden field is a sign of form tampering, since normal form
interaction won't alter them. However, you could easily insert some error
displays for those form errors as well.
displays for those form errors, as well.
.. versionadded:: 1.1
The ``hidden_fields`` and ``visible_fields`` methods are new in Django