From 306e12aab8645c4682dec33f3dd25001934409c3 Mon Sep 17 00:00:00 2001 From: Chris McDonough Date: Thu, 18 Jun 2009 23:48:35 +0000 Subject: IForbiddenView utility directive -> forbidden zcml directive --- docs/tutorials/bfgwiki2/authorization.rst | 17 ++++++++--------- 1 file changed, 8 insertions(+), 9 deletions(-) (limited to 'docs/tutorials') diff --git a/docs/tutorials/bfgwiki2/authorization.rst b/docs/tutorials/bfgwiki2/authorization.rst index a8100999e..9988602d5 100644 --- a/docs/tutorials/bfgwiki2/authorization.rst +++ b/docs/tutorials/bfgwiki2/authorization.rst @@ -159,15 +159,14 @@ class="main_content">`` div: Changing ``configure.zcml`` ~~~~~~~~~~~~~~~~~~~~~~~~~~~ -Change your application's ``configure.zcml`` to add a slightly -inscrutable ``utility`` stanza which "provides" ``IForbiddenView``. -This configures our login view to show up when BFG detects that a view -invocation can not be authorized. Also, add ``permission`` attributes -with the value ``edit`` to the ``edit_page`` and ``add_page`` routes. -This indicates that the views which these routes reference cannot be -invoked without the authenticated user possessing the ``edit`` -permission. When you're done, your ``configure.zcml`` will look like -so: +Change your application's ``configure.zcml`` to add a ``forbidden`` +stanza which points at our login view. This configures our login view +to show up when BFG detects that a view invocation can not be +authorized. Also, add ``permission`` attributes with the value +``edit`` to the ``edit_page`` and ``add_page`` routes. This indicates +that the views which these routes reference cannot be invoked without +the authenticated user possessing the ``edit`` permission. When +you're done, your ``configure.zcml`` will look like so: .. literalinclude:: src/authorization/tutorial/configure.zcml :linenos: -- cgit v1.2.3