mirror of
https://github.com/django/django.git
synced 2025-10-24 06:06:09 +00:00
[1.0.X] A whole lotta documentation fixes, backported from r10303 on trunk.
I got my commit message cut off the first try, but luckily I get to still thank Kevin Kubasik for rolling all these fixes up into a single easy patch. git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.0.X@10306 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
@@ -67,3 +67,13 @@ Using a :class:`~django.db.models.FileField` or an
|
||||
Django. For example, if your :class:`~django.db.models.ImageField` is
|
||||
called ``mug_shot``, you can get the absolute URL to your image in a
|
||||
template with ``{{ object.mug_shot.url }}``.
|
||||
|
||||
How do I make a variable available to all my templates?
|
||||
-------------------------------------------------------
|
||||
|
||||
Sometimes your templates just all need the same thing. A common example would
|
||||
be dynamically-generated menus. At first glance, it seems logical to simply
|
||||
add a common dictionary to the template context.
|
||||
|
||||
The correct solution is to use a ``RequestContext``. Details on how to do this
|
||||
are here: :ref:`subclassing-context-requestcontext`.
|
||||
|
||||
Reference in New Issue
Block a user