Fixed #18625 -- Removed old-style use of url tag
from the documentation.
This commit is contained in:
parent
c57abd3c29
commit
fb46f243b4
|
@ -250,7 +250,7 @@ Redirecting after the comment post
|
||||||
To specify the URL you want to redirect to after the comment has been posted,
|
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::
|
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:
|
.. _notes-on-the-comment-form:
|
||||||
|
|
||||||
|
|
|
@ -704,8 +704,8 @@ target each pattern individually by using its name:
|
||||||
|
|
||||||
.. code-block:: html+django
|
.. code-block:: html+django
|
||||||
|
|
||||||
{% url arch-summary 1945 %}
|
{% url 'arch-summary' 1945 %}
|
||||||
{% url full-archive 2007 %}
|
{% url 'full-archive' 2007 %}
|
||||||
|
|
||||||
Even though both URL patterns refer to the ``archive`` view here, using the
|
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.
|
``name`` parameter to ``url()`` allows you to tell them apart in templates.
|
||||||
|
|
|
@ -596,7 +596,7 @@ apply.
|
||||||
Reverse URL lookups cannot be carried out within the ``blocktrans`` and should
|
Reverse URL lookups cannot be carried out within the ``blocktrans`` and should
|
||||||
be retrieved (and stored) beforehand::
|
be retrieved (and stored) beforehand::
|
||||||
|
|
||||||
{% url path.to.view arg arg2 as the_url %}
|
{% url 'path.to.view' arg arg2 as the_url %}
|
||||||
{% blocktrans %}
|
{% blocktrans %}
|
||||||
This is a URL: {{ the_url }}
|
This is a URL: {{ the_url }}
|
||||||
{% endblocktrans %}
|
{% endblocktrans %}
|
||||||
|
@ -790,7 +790,7 @@ To use the catalog, just pull in the dynamically generated script like this:
|
||||||
|
|
||||||
.. code-block:: html+django
|
.. 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.
|
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
|
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:" %}
|
{% trans "View this category in:" %}
|
||||||
{% for lang_code, lang_name in languages %}
|
{% for lang_code, lang_name in languages %}
|
||||||
{% language lang_code %}
|
{% language lang_code %}
|
||||||
<a href="{% url category slug=category.slug %}">{{ lang_name }}</a>
|
<a href="{% url 'category' slug=category.slug %}">{{ lang_name }}</a>
|
||||||
{% endlanguage %}
|
{% endlanguage %}
|
||||||
{% endfor %}
|
{% endfor %}
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue