Commit c5653529 authored by Gary Wilson Jr's avatar Gary Wilson Jr
Browse files

Fixed #9780 -- Fixed an undefined internal link in the model forms documentation, thanks ramiro.


git-svn-id: http://code.djangoproject.com/svn/django/trunk@9670 bcc190cf-cafb-0310-a4f2-bffc1f526a37
parent d66e63f2
Loading
Loading
Loading
Loading
+2 −0
Original line number Diff line number Diff line
@@ -110,6 +110,8 @@ attempt to provide an article, but fail to do so::
As we can see the formset properly performed validation and gave us the
expected errors.

.. _understanding-the-managementform:

Understanding the ManagementForm
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+7 −5
Original line number Diff line number Diff line
@@ -197,7 +197,8 @@ accepts either ``True`` or ``False``. If you call ``save()`` with
the database. In this case, it's up to you to call ``save()`` on the resulting
model instance. This is useful if you want to do custom processing on the
object before saving it, or if you want to use one of the specialized
:ref:`model saving options <ref-models-force-insert>`. ``commit`` is ``True`` by default.
:ref:`model saving options <ref-models-force-insert>`. ``commit`` is ``True``
by default.

Another side effect of using ``commit=False`` is seen when your model has
a many-to-many relation with another model. If your model has a many-to-many
@@ -583,7 +584,8 @@ itself::
    </form>

When you manually render the forms yourself, be sure to render the management
form as shown above. See the :ref:`management form documentation <understanding-the-managementform>`.
form as shown above. See the :ref:`management form documentation
<understanding-the-managementform>`.

Third, you can manually render each field::