Fixed #15375 -- clarified apparent contradiction in Form Wizard documentation. Thanks to codysomerville for the report.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@15633 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
b9a20d1e3b
commit
6ce03dd888
|
@ -7,8 +7,8 @@ Form wizard
|
||||||
|
|
||||||
Django comes with an optional "form wizard" application that splits
|
Django comes with an optional "form wizard" application that splits
|
||||||
:doc:`forms </topics/forms/index>` across multiple Web pages. It maintains
|
:doc:`forms </topics/forms/index>` across multiple Web pages. It maintains
|
||||||
state in hashed HTML :samp:`<input type="hidden">` fields, and the data isn't
|
state in hashed HTML :samp:`<input type="hidden">` fields so that the full
|
||||||
processed server-side until the final form is submitted.
|
server-side processing can be delayed until the submission of the final form.
|
||||||
|
|
||||||
You might want to use this if you have a lengthy form that would be too
|
You might want to use this if you have a lengthy form that would be too
|
||||||
unwieldy for display on a single page. The first page might ask the user for
|
unwieldy for display on a single page. The first page might ask the user for
|
||||||
|
|
Loading…
Reference in New Issue