summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorAymeric Augustin <aymeric.augustin@m4x.org>2012-07-15 11:19:00 +0200
committerAymeric Augustin <aymeric.augustin@m4x.org>2012-07-15 11:19:50 +0200
commitfb46f243b4c48ab42ed2f33a2636f7c33f5861a9 (patch)
tree0eab0060263c999dd65255b9824e2451aef539ae /docs
parentc57abd3c29cedcca00821d2a0d5708f10977f3c6 (diff)
Fixed #18625 -- Removed old-style use of url tag
from the documentation.
Diffstat (limited to 'docs')
-rw-r--r--docs/ref/contrib/comments/index.txt2
-rw-r--r--docs/topics/http/urls.txt4
-rw-r--r--docs/topics/i18n/translation.txt6
3 files changed, 6 insertions, 6 deletions
diff --git a/docs/ref/contrib/comments/index.txt b/docs/ref/contrib/comments/index.txt
index 40b1b662b7..af937e036e 100644
--- a/docs/ref/contrib/comments/index.txt
+++ b/docs/ref/contrib/comments/index.txt
@@ -250,7 +250,7 @@ Redirecting after the comment post
To specify the URL you want to redirect to after the comment has been posted,
you can include a hidden form input called ``next`` in your comment form. For example::
- <input type="hidden" name="next" value="{% url my_comment_was_posted %}" />
+ <input type="hidden" name="next" value="{% url 'my_comment_was_posted' %}" />
.. _notes-on-the-comment-form:
diff --git a/docs/topics/http/urls.txt b/docs/topics/http/urls.txt
index 2310fac413..4e75dfe55f 100644
--- a/docs/topics/http/urls.txt
+++ b/docs/topics/http/urls.txt
@@ -704,8 +704,8 @@ target each pattern individually by using its name:
.. code-block:: html+django
- {% url arch-summary 1945 %}
- {% url full-archive 2007 %}
+ {% url 'arch-summary' 1945 %}
+ {% url 'full-archive' 2007 %}
Even though both URL patterns refer to the ``archive`` view here, using the
``name`` parameter to ``url()`` allows you to tell them apart in templates.
diff --git a/docs/topics/i18n/translation.txt b/docs/topics/i18n/translation.txt
index ec6159d538..c912bf9575 100644
--- a/docs/topics/i18n/translation.txt
+++ b/docs/topics/i18n/translation.txt
@@ -596,7 +596,7 @@ apply.
Reverse URL lookups cannot be carried out within the ``blocktrans`` and should
be retrieved (and stored) beforehand::
- {% url path.to.view arg arg2 as the_url %}
+ {% url 'path.to.view' arg arg2 as the_url %}
{% blocktrans %}
This is a URL: {{ the_url }}
{% endblocktrans %}
@@ -790,7 +790,7 @@ To use the catalog, just pull in the dynamically generated script like this:
.. code-block:: html+django
- <script type="text/javascript" src="{% url django.views.i18n.javascript_catalog %}"></script>
+ <script type="text/javascript" src="{% url 'django.views.i18n.javascript_catalog' %}"></script>
This uses reverse URL lookup to find the URL of the JavaScript catalog view.
When the catalog is loaded, your JavaScript code can use the standard
@@ -992,7 +992,7 @@ template tag. It enables the given language in the enclosed template section:
{% trans "View this category in:" %}
{% for lang_code, lang_name in languages %}
{% language lang_code %}
- <a href="{% url category slug=category.slug %}">{{ lang_name }}</a>
+ <a href="{% url 'category' slug=category.slug %}">{{ lang_name }}</a>
{% endlanguage %}
{% endfor %}