From 855bc7b09d5f511fe7eb71e2f35cd0154451e357 Mon Sep 17 00:00:00 2001 From: James Bennett Date: Tue, 18 Mar 2008 21:13:12 +0000 Subject: [PATCH] Fixed #6266: Added note to docs/modelforms.txt pointing out that they're just standard forms and have all the same methods as standard forms git-svn-id: http://code.djangoproject.com/svn/django/trunk@7305 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/modelforms.txt | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/docs/modelforms.txt b/docs/modelforms.txt index 47eaa9a769a..05f9b1b3d4a 100644 --- a/docs/modelforms.txt +++ b/docs/modelforms.txt @@ -231,6 +231,16 @@ For example:: # Create and save the new author instance. There's no need to do anything else. >>> new_author = f.save() +Other than the ``save()`` and ``save_m2m()`` methods, a ``ModelForm`` +works exactly the same way as any other ``newforms`` form. For +example, the ``is_valid()`` method is used to check for validity, the +``is_multipart()`` method is used to determine whether a form requires +multipart file upload (and hence whether ``request.FILES`` must be +passed to the form), etc.; see `the standard newforms documentation`_ +for more information. + +.. _the standard newforms documentation: ../newforms/ + Using a subset of fields on the form ------------------------------------