Author: timo Date: 2011-06-04 14:42:53 -0700 (Sat, 04 Jun 2011) New Revision: 16329
Modified: django/trunk/docs/topics/forms/modelforms.txt Log: Fixed #15990 - Simplified a sentence regarding form validation for ModelForms; thanks jblaine for the suggestion. Modified: django/trunk/docs/topics/forms/modelforms.txt =================================================================== --- django/trunk/docs/topics/forms/modelforms.txt 2011-06-04 17:05:38 UTC (rev 16328) +++ django/trunk/docs/topics/forms/modelforms.txt 2011-06-04 21:42:53 UTC (rev 16329) @@ -195,14 +195,11 @@ The ``is_valid()`` method and ``errors`` ---------------------------------------- -.. versionchanged:: 1.2 - The first time you call ``is_valid()`` or access the ``errors`` attribute of a -``ModelForm`` has always triggered form validation, but as of Django 1.2, it -will also trigger :ref:`model validation <validating-objects>`. This has the -side-effect of cleaning the model you pass to the ``ModelForm`` constructor. -For instance, calling ``is_valid()`` on your form will convert any date fields -on your model to actual date objects. +``ModelForm`` triggers form validation as well as :ref:`model validation +<validating-objects>`. This has the side-effect of cleaning the model you pass +to the ``ModelForm`` constructor. For instance, calling ``is_valid()`` on your +form will convert any date fields on your model to actual date objects. The ``save()`` method @@ -359,7 +356,7 @@ --------------------------------------------- .. versionadded:: 1.2 - The ``widgets`` attribute is new in Django 1.2. + The ``widgets`` attribute is new in Django 1.2. The default field types, as described in the `Field types`_ table above, are sensible defaults. If you have a ``DateField`` in your model, chances are you'd -- You received this message because you are subscribed to the Google Groups "Django updates" group. To post to this group, send email to django-updates@googlegroups.com. To unsubscribe from this group, send email to django-updates+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-updates?hl=en.