summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorOla Sitarska <ola@sitarska.com>2014-09-21 17:15:44 +0200
committerBaptiste Mispelon <bmispelon@gmail.com>2014-09-21 17:34:23 +0200
commita6c294a5a293b1096e4e8dd86933c76356c70d71 (patch)
treef851abfdcada020d94e77d5a21e129a9bbc92050 /docs
parentaa1939c1d1e923d98fb00250dee34e00421bcee5 (diff)
[1.6.x] Fixed #23529 -- Replaced comments tag library with humanize in docs
Backport of ee442e97da390b7136dc12b66ddfa70263a60b5c from master.
Diffstat (limited to 'docs')
-rw-r--r--docs/topics/templates.txt16
1 files changed, 8 insertions, 8 deletions
diff --git a/docs/topics/templates.txt b/docs/topics/templates.txt
index 2856664f80..8a8b16b33f 100644
--- a/docs/topics/templates.txt
+++ b/docs/topics/templates.txt
@@ -659,18 +659,18 @@ Custom tag and filter libraries
Certain applications provide custom tag and filter libraries. To access them in
a template, use the :ttag:`load` tag::
- {% load comments %}
+ {% load humanize %}
- {% comment_form for blogs.entries entry.id with is_public yes %}
+ {{ 45000|intcomma }}
-In the above, the :ttag:`load` tag loads the ``comments`` tag library, which then
-makes the ``comment_form`` tag available for use. Consult the documentation
+In the above, the :ttag:`load` tag loads the ``humanize`` tag library, which then
+makes the ``intcomma`` filter available for use. Consult the documentation
area in your admin to find the list of custom libraries in your installation.
The :ttag:`load` tag can take multiple library names, separated by spaces.
Example::
- {% load comments i18n %}
+ {% load humanize i18n %}
See :doc:`/howto/custom-template-tags` for information on writing your own custom
template libraries.
@@ -682,9 +682,9 @@ When you load a custom tag or filter library, the tags/filters are only made
available to the current template -- not any parent or child templates along
the template-inheritance path.
-For example, if a template ``foo.html`` has ``{% load comments %}``, a child
+For example, if a template ``foo.html`` has ``{% load humanize %}``, a child
template (e.g., one that has ``{% extends "foo.html" %}``) will *not* have
-access to the comments template tags and filters. The child template is
-responsible for its own ``{% load comments %}``.
+access to the humanize template tags and filters. The child template is
+responsible for its own ``{% load humanize %}``.
This is a feature for the sake of maintainability and sanity.