X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=catagits%2FCatalyst-Manual.git;a=blobdiff_plain;f=lib%2FCatalyst%2FManual%2FTutorial%2FAuthorization.pod;fp=lib%2FCatalyst%2FManual%2FTutorial%2FAuthorization.pod;h=66c6612e396e12f37c22b2a8ca27a408e8ee1809;hp=2c3451fa14102ce54db9b214c7e9898ed7ef4957;hb=4b4d38842b2383a70a54bcadb493505950b469dd;hpb=636ba9f78f6ce788549fbfa7f1a1507d0579e978 diff --git a/lib/Catalyst/Manual/Tutorial/Authorization.pod b/lib/Catalyst/Manual/Tutorial/Authorization.pod index 2c3451f..66c6612 100644 --- a/lib/Catalyst/Manual/Tutorial/Authorization.pod +++ b/lib/Catalyst/Manual/Tutorial/Authorization.pod @@ -1,11 +1,11 @@ =head1 NAME -Catalyst::Manual::Tutorial::Authorization - Catalyst Tutorial - Part 6: Authorization +Catalyst::Manual::Tutorial::Authorization - Catalyst Tutorial - Chapter 6: Authorization =head1 OVERVIEW -This is B for the Catalyst tutorial. +This is B for the Catalyst tutorial. L @@ -56,8 +56,8 @@ L =head1 DESCRIPTION -This part of the tutorial adds role-based authorization to the -existing authentication implemented in Part 5. It provides simple +This chapter of the tutorial adds role-based authorization to the +existing authentication implemented in Chapter 5. It provides simple examples of how to use roles in both TT templates and controller actions. The first half looks at basic authorization concepts. The second half looks at how moving your authorization code to your model @@ -248,7 +248,7 @@ way to demonstrate that TT templates will not be used if the response body has already been set. In reality you would probably want to use a technique that maintains the visual continuity of your template layout (for example, using the "status" or "error" message feature added in -Part 3 or C to an action that shows an "unauthorized" page). +Chapter 3 or C to an action that shows an "unauthorized" page). B: If you want to keep your existing C method, you can create a new copy and comment out the original by making it look like a