From 1b910d7fbcc664ae22bef010af05746027b82138 Mon Sep 17 00:00:00 2001 From: Luke Plant Date: Tue, 7 Sep 2010 20:54:13 +0000 Subject: [PATCH] [1.2.X] Fixed #13350 - Documentation on autoescape should mention endautoescape Thanks to mountainpaul@gmail.com for report and to dwillis for patch. Backport of [13694] from trunk git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.2.X@13695 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/ref/templates/builtins.txt | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/docs/ref/templates/builtins.txt b/docs/ref/templates/builtins.txt index b5ce71e321..4f33bd212c 100644 --- a/docs/ref/templates/builtins.txt +++ b/docs/ref/templates/builtins.txt @@ -23,7 +23,7 @@ autoescape Control the current auto-escaping behavior. This tag takes either ``on`` or ``off`` as an argument and that determines whether auto-escaping is in effect -inside the block. +inside the block. The block is closed with an ``endautoescape`` ending tag. When auto-escaping is in effect, all variable content has HTML escaping applied to it before placing the result into the output (but after any filters have @@ -34,6 +34,12 @@ The only exceptions are variables that are already marked as "safe" from escaping, either by the code that populated the variable, or because it has had the ``safe`` or ``escape`` filters applied. +Sample usage:: + + {% autoescape on %} + {{ body }} + {% endautoescape %} + .. templatetag:: block block