[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
This commit is contained in:
Luke Plant 2010-09-07 20:54:13 +00:00
parent 79d9206711
commit 1b910d7fbc
1 changed files with 7 additions and 1 deletions

View File

@ -23,7 +23,7 @@ autoescape
Control the current auto-escaping behavior. This tag takes either ``on`` or 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 ``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 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 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 escaping, either by the code that populated the variable, or because it has had
the ``safe`` or ``escape`` filters applied. the ``safe`` or ``escape`` filters applied.
Sample usage::
{% autoescape on %}
{{ body }}
{% endautoescape %}
.. templatetag:: block .. templatetag:: block
block block