diff --git a/docs/ref/forms/api.txt b/docs/ref/forms/api.txt
index 4aacbf0..d1f877f 100644
|
a
|
b
|
form data *and* file data::
|
| 716 | 716 | Testing for multipart forms |
| 717 | 717 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 718 | 718 | |
| | 719 | .. method:: Form.is_multipart |
| | 720 | |
| 719 | 721 | If you're writing reusable views or templates, you may not know ahead of time |
| 720 | 722 | whether your form is a multipart form or not. The ``is_multipart()`` method |
| 721 | 723 | tells you whether the form requires multipart encoding for submission:: |
diff --git a/docs/topics/forms/index.txt b/docs/topics/forms/index.txt
index 9b5794a..a3c17e1 100644
|
a
|
b
|
context variable ``form``. Here's a simple example template::
|
| 197 | 197 | The form only outputs its own fields; it is up to you to provide the surrounding |
| 198 | 198 | ``<form>`` tags and the submit button. |
| 199 | 199 | |
| | 200 | If your form includes uploaded files, be sure to include |
| | 201 | ``enctype="multipart/form-data"`` in the ``form`` element. If you wish to write |
| | 202 | a generic template that will work whether or not the form has files, you can |
| | 203 | use the :meth:`~django.forms.Form.is_multipart` attribute on the form:: |
| | 204 | |
| | 205 | <form action="/contact/" method="post" |
| | 206 | {% if form.is_multipart %}enctype="multipart/form-data"{% endif %}> |
| | 207 | |
| 200 | 208 | .. admonition:: Forms and Cross Site Request Forgery protection |
| 201 | 209 | |
| 202 | 210 | Django ships with an easy-to-use :doc:`protection against Cross Site Request |