Fixed #13949 - Note that readonly fields can't be modified via custom clean methods. thanks alk for the suggestion and elbarto and Gabriel Hurley whose language I used in the final patch.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@15060 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
4b2b2eda24
commit
38d60c3941
|
@ -139,7 +139,11 @@ While you could access ``request.POST`` directly at this point, it is better to
|
||||||
access ``form.cleaned_data``. This data has not only been validated but will
|
access ``form.cleaned_data``. This data has not only been validated but will
|
||||||
also be converted in to the relevant Python types for you. In the above example,
|
also be converted in to the relevant Python types for you. In the above example,
|
||||||
``cc_myself`` will be a boolean value. Likewise, fields such as ``IntegerField``
|
``cc_myself`` will be a boolean value. Likewise, fields such as ``IntegerField``
|
||||||
and ``FloatField`` convert values to a Python int and float respectively.
|
and ``FloatField`` convert values to a Python int and float respectively. Note
|
||||||
|
that read-only fields are not available in ``form.cleaned_data`` (and setting
|
||||||
|
a value in a custom ``clean()`` method won't have any effect) because these
|
||||||
|
fields are displayed as text rather than as input elements, and thus are not
|
||||||
|
posted back to the server.
|
||||||
|
|
||||||
Extending the above example, here's how the form data could be processed:
|
Extending the above example, here's how the form data could be processed:
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue