| 1 | Index: /home/nagyv/versioning/svn/django/docs/templates.txt
|
|---|
| 2 | ===================================================================
|
|---|
| 3 | --- /home/nagyv/versioning/svn/django/docs/templates.txt (revision 7882)
|
|---|
| 4 | +++ /home/nagyv/versioning/svn/django/docs/templates.txt (working copy)
|
|---|
| 5 | @@ -1168,7 +1168,7 @@
|
|---|
| 6 | takes a client ID (here, ``client()`` is a method inside the views file
|
|---|
| 7 | ``app_views.py``). The URLconf line might look like this::
|
|---|
| 8 |
|
|---|
| 9 | - ('^client/(\d+)/$', 'app_views.client')
|
|---|
| 10 | + ('^client/(\d+)/$', 'app_name.app_views.client')
|
|---|
| 11 |
|
|---|
| 12 | If this app's URLconf is included into the project's URLconf under a path
|
|---|
| 13 | such as this::
|
|---|
| 14 | @@ -1177,7 +1177,7 @@
|
|---|
| 15 |
|
|---|
| 16 | ...then, in a template, you can create a link to this view like this::
|
|---|
| 17 |
|
|---|
| 18 | - {% url app_views.client client.id %}
|
|---|
| 19 | + {% url app_name.app_views.client client.id %}
|
|---|
| 20 |
|
|---|
| 21 | The template tag will output the string ``/clients/client/123/``.
|
|---|
| 22 |
|
|---|