Ticket #1653: forms.txt.diff

docs/forms.txt

@@ -581 +581 @@
     the executable specified in the ``JING_PATH`` setting (see the settings_
     document for more details).
 
+FileField, ImageField and forms
+===============================
+
+Where most, if not all, model fields only require a simple addition in the
+form of ``{{ form.fieldname }}`` to a template, the situation is a bit
+different for the FileField and ImageField fields.
+
+Say that in the model definition there is a declaration for::
+
+    file = model.FileField('/path/to/upload/location')
+
+Normally this would be used in a template form like the following::
+
+    <p><label for="file">File:</label> {{ form.file }}</p>
+
+The first thing that is noticeable when the page is opened in a browser is
+that there is no typical text field with a browse button, as would be
+expected.
+
+To get this behaviour a little change to the template is needed to get the
+following::
+
+    <p><label for="file">File:</label> {{ form.file }}{{ form.file_file }}</p>
+
+If you would reload the page it should now show a file upload text field
+complete with a browse button.
+
+Also make sure to use ``form.file_file`` with validation and not
+``form.file``.
+
+In the view make sure that the ``update(request.FILES)`` method is called
+after the object has been created with the ``request.POST.copy()`` call, as
+such::
+
+    new_data = request.POST.copy()
+    new_data.update(request.FILES)
+
 .. _`generic views`: http://www.djangoproject.com/documentation/generic_views/
 .. _`models API`: http://www.djangoproject.com/documentation/model_api/
 .. _settings: http://www.djangoproject.com/documentation/settings/