From 516051bfd2b537f441c46359cce7eacbf15fc4b8 Mon Sep 17 00:00:00 2001 From: Jacob Kaplan-Moss Date: Tue, 31 Mar 2009 23:34:03 +0000 Subject: A whole lotta documentation fixes: Fixes #8704, #8826, #8980, #9243, #9343, #9529, git-svn-id: http://code.djangoproject.com/svn/django/trunk@10303 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/faq/usage.txt | 10 ++++++++++ 1 file changed, 10 insertions(+) (limited to 'docs/faq') diff --git a/docs/faq/usage.txt b/docs/faq/usage.txt index e335403ace..6c3c518bb2 100644 --- a/docs/faq/usage.txt +++ b/docs/faq/usage.txt @@ -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`. -- cgit v1.3