[1.4.x] Fixed a couple links that didn't backport cleanly
This commit is contained in:
parent
6ebb6f9188
commit
33d11463a0
|
@ -56,7 +56,7 @@ algorithm the system follows to determine which Python code to execute:
|
|||
|
||||
4. Once one of the regexes matches, Django imports and calls the given
|
||||
view, which is a simple Python function (or a :doc:`class based view
|
||||
</topics/class-based-views/index>`). The view gets passed an
|
||||
</topics/class-based-views>`). The view gets passed an
|
||||
:class:`~django.http.HttpRequest` as its first argument and any values
|
||||
captured in the regex as remaining arguments.
|
||||
|
||||
|
@ -674,7 +674,7 @@ The style you use is up to you.
|
|||
Note that if you use this technique -- passing objects rather than strings --
|
||||
the view prefix (as explained in "The view prefix" above) will have no effect.
|
||||
|
||||
Note that :doc:`class based views</topics/class-based-views/index>` must be
|
||||
Note that :doc:`class based views</topics/class-based-views>` must be
|
||||
imported::
|
||||
|
||||
from mysite.views import ClassBasedView
|
||||
|
|
Loading…
Reference in New Issue