Fixed #17390 - Added a note to topics/auth.txt regarding how to decorate class-based generic views; thanks zsiciarz for the patch.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@17564 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
e1bbf3b6bc
commit
9e62428c28
|
@ -1457,9 +1457,16 @@ The permission_required decorator
|
|||
Limiting access to generic views
|
||||
--------------------------------
|
||||
|
||||
To limit access to a :doc:`generic view </ref/generic-views>`, write a thin
|
||||
wrapper around the view, and point your URLconf to your wrapper instead of the
|
||||
generic view itself. For example::
|
||||
Controlling access to a :doc:`class-based generic view </ref/class-based-views>`
|
||||
is done by decorating the :meth:`View.dispatch <django.views.generic.base.View.dispatch>`
|
||||
method on the class. See :ref:`decorating-class-based-views` for the details.
|
||||
|
||||
Function-based generic views
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
To limit access to a :doc:`function-based generic view </ref/generic-views>`,
|
||||
write a thin wrapper around the view, and point your URLconf to your wrapper
|
||||
instead of the generic view itself. For example::
|
||||
|
||||
from django.views.generic.date_based import object_detail
|
||||
|
||||
|
|
|
@ -584,6 +584,8 @@ This approach applies the decorator on a per-instance basis. If you
|
|||
want every instance of a view to be decorated, you need to take a
|
||||
different approach.
|
||||
|
||||
.. _decorating-class-based-views:
|
||||
|
||||
Decorating the class
|
||||
--------------------
|
||||
|
||||
|
|
Loading…
Reference in New Issue