From cb1368bbc6d487a60986891edbe8cada3778ada3 Mon Sep 17 00:00:00 2001
From: Jacob Kaplan-Moss <jacob@jacobian.org>
Date: Tue, 12 Aug 2008 23:34:45 +0000
Subject: [PATCH] Fixed #8189, another use of get_FOO_url() missed in the docs
after filestorage.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@8335 bcc190cf-cafb-0310-a4f2-bffc1f526a37
---
docs/model-api.txt | 9 ++++-----
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/docs/model-api.txt b/docs/model-api.txt
index 8001b1cee9..6dee963621 100644
--- a/docs/model-api.txt
+++ b/docs/model-api.txt
@@ -295,11 +295,10 @@ specified storage system takes a few steps:
subdirectory of ``MEDIA_ROOT`` it should upload files.
3. All that will be stored in your database is a path to the file
- (relative to ``MEDIA_ROOT``). You'll most likely want to use the
- convenience ``get_<fieldname>_url`` function provided by Django. For
- example, if your ``ImageField`` is called ``mug_shot``, you can get
- the absolute URL to your image in a template with ``{{
- object.get_mug_shot_url }}``.
+ (relative to ``MEDIA_ROOT``). You'll most likely want to use
+ ``object.<field>.url`` to get the actual URL. For example, if your
+ ``ImageField`` is called ``mug_shot``, you can get the absolute URL to
+ your image in a template with ``{{ object.mug_shot.url }}``.
For example, say your ``MEDIA_ROOT`` is set to ``'/home/media'``, and
``upload_to`` is set to ``'photos/%Y/%m/%d'``. The ``'%Y/%m/%d'`` part of