From: Kennedy Clark Date: Sun, 1 Jun 2008 23:43:44 +0000 (+0000) Subject: Fix erroneous "Part #" cross references between parts of the tutorial. X-Git-Tag: v5.8005~284 X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=catagits%2FCatalyst-Manual.git;a=commitdiff_plain;h=9ad715b3a89ba2d34123a2d0f4624302bc169f78 Fix erroneous "Part #" cross references between parts of the tutorial. --- diff --git a/lib/Catalyst/Manual/Tutorial/AdvancedCRUD.pod b/lib/Catalyst/Manual/Tutorial/AdvancedCRUD.pod index f05d79a..a357ecd 100644 --- a/lib/Catalyst/Manual/Tutorial/AdvancedCRUD.pod +++ b/lib/Catalyst/Manual/Tutorial/AdvancedCRUD.pod @@ -57,7 +57,7 @@ L =head1 DESCRIPTION This part of the tutorial explores more advanced functionality for -Create, Read, Update, and Delete (CRUD) than we saw in Part 3. In +Create, Read, Update, and Delete (CRUD) than we saw in Part 4. In particular, it looks at a number of techniques that can be useful for the Update portion of CRUD, such as automated form generation, validation of user-entered data, and automated transfer of data between diff --git a/lib/Catalyst/Manual/Tutorial/Authentication.pod b/lib/Catalyst/Manual/Tutorial/Authentication.pod index 652d210..e312ea8 100644 --- a/lib/Catalyst/Manual/Tutorial/Authentication.pod +++ b/lib/Catalyst/Manual/Tutorial/Authentication.pod @@ -58,7 +58,7 @@ L Now that we finally have a simple yet functional application, we can focus on providing authentication (with authorization coming next in -Part 5). +Part 6). This part of the tutorial is divided into two main sections: 1) basic, cleartext authentication and 2) hash-based authentication. @@ -77,7 +77,7 @@ application. First, we add both user and role information to the database (we will add the role information here although it will not be used until the -authorization section, Part 5). Create a new SQL script file by opening +authorization section, Part 6). Create a new SQL script file by opening C in your editor and insert: -- diff --git a/lib/Catalyst/Manual/Tutorial/Authorization.pod b/lib/Catalyst/Manual/Tutorial/Authorization.pod index 02d7358..61c5e29 100644 --- a/lib/Catalyst/Manual/Tutorial/Authorization.pod +++ b/lib/Catalyst/Manual/Tutorial/Authorization.pod @@ -57,7 +57,7 @@ L =head1 DESCRIPTION This part of the tutorial adds role-based authorization to the existing -authentication implemented in Part 4. It provides simple examples of +authentication implemented in Part 5. It provides simple examples of how to use roles in both TT templates and controller actions. The first half looks at manually configured authorization. The second half looks at how the ACL authorization plugin can simplify your code. @@ -238,7 +238,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 2). +Part 3). 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 diff --git a/lib/Catalyst/Manual/Tutorial/MoreCatalystBasics.pod b/lib/Catalyst/Manual/Tutorial/MoreCatalystBasics.pod index 48982ab..cf413cd 100644 --- a/lib/Catalyst/Manual/Tutorial/MoreCatalystBasics.pod +++ b/lib/Catalyst/Manual/Tutorial/MoreCatalystBasics.pod @@ -762,7 +762,7 @@ will use static schema files for more control. This is typical of most One option would be to create a separate schema file for each table in the database, however, lets use the same L used earlier with C to build the static files for us. -First, lets remove the schema file created in Part 2: +First, lets remove the schema file created earlier: $ rm lib/MyApp/Schema.pm diff --git a/lib/Catalyst/Manual/Tutorial/Testing.pod b/lib/Catalyst/Manual/Tutorial/Testing.pod index 2a8a88a..ffadf76 100644 --- a/lib/Catalyst/Manual/Tutorial/Testing.pod +++ b/lib/Catalyst/Manual/Tutorial/Testing.pod @@ -288,7 +288,7 @@ or Experiment with the C, C and C<-v> settings. If you find that there are errors, use the -techniques discussed in the "Catalyst Debugging" section (Part 6) to +techniques discussed in the "Catalyst Debugging" section (Part 7) to isolate and fix any problems. If you want to run the test case under the Perl interactive debugger,