Fixed #7951 -- Corrected typo in FAQ. Thanks to vulcan_eager for the report.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@8071 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
dd5194ad7e
commit
ecdd071794
|
@ -425,7 +425,7 @@ Using a ``FileField`` or an ``ImageField`` in a model takes a few steps:
|
||||||
of ``MEDIA_ROOT`` it should upload files.
|
of ``MEDIA_ROOT`` it should upload files.
|
||||||
|
|
||||||
#. All that will be stored in your database is a path to the file
|
#. All that will be stored in your database is a path to the file
|
||||||
(relative to ``MEDIA_ROOT``). You'll must likely want to use the
|
(relative to ``MEDIA_ROOT``). You'll most likely want to use the
|
||||||
convenience ``get_<fieldname>_url`` function provided by Django. For
|
convenience ``get_<fieldname>_url`` function provided by Django. For
|
||||||
example, if your ``ImageField`` is called ``mug_shot``, you can get the
|
example, if your ``ImageField`` is called ``mug_shot``, you can get the
|
||||||
absolute URL to your image in a template with
|
absolute URL to your image in a template with
|
||||||
|
|
Loading…
Reference in New Issue