From 171c7cc863eafc2346aa84ffd1d540644539f1a4 Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Tue, 24 Oct 2017 13:25:55 -0400 Subject: [PATCH] Fixed #28737 -- Clarified {% cache %} tag's handling of arguments. Thanks Tom Aratyn for the report. --- docs/topics/cache.txt | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/docs/topics/cache.txt b/docs/topics/cache.txt index 927e035c90..7c72075817 100644 --- a/docs/topics/cache.txt +++ b/docs/topics/cache.txt @@ -660,8 +660,9 @@ example: Sometimes you might want to cache multiple copies of a fragment depending on some dynamic data that appears inside the fragment. For example, you might want a separate cached copy of the sidebar used in the previous example for every user -of your site. Do this by passing additional arguments to the ``{% cache %}`` -template tag to uniquely identify the cache fragment: +of your site. Do this by passing one or more additional arguments, which may be +variables with or without filters, to the ``{% cache %}`` template tag to +uniquely identify the cache fragment: .. code-block:: html+django @@ -670,9 +671,6 @@ template tag to uniquely identify the cache fragment: .. sidebar for logged in user .. {% endcache %} -It's perfectly fine to specify more than one argument to identify the fragment. -Simply pass as many arguments to ``{% cache %}`` as you need. - If :setting:`USE_I18N` is set to ``True`` the per-site middleware cache will :ref:`respect the active language`. For the ``cache`` template tag you could use one of the