X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=catagits%2FCatalyst-Manual.git;a=blobdiff_plain;f=lib%2FCatalyst%2FManual%2FTutorial%2F05_Authentication.pod;h=f3f0f126f40c29f5773fe69728c20e49567e5a52;hp=7b187a4a529757ee6c11a6c866f819a0f3c84c94;hb=24acc5d75bb4208eeef4d1bad0974f0fd5893454;hpb=d8e9b469736c9313a09ce5f08d10d1a467ffae09 diff --git a/lib/Catalyst/Manual/Tutorial/05_Authentication.pod b/lib/Catalyst/Manual/Tutorial/05_Authentication.pod index 7b187a4..f3f0f12 100644 --- a/lib/Catalyst/Manual/Tutorial/05_Authentication.pod +++ b/lib/Catalyst/Manual/Tutorial/05_Authentication.pod @@ -63,8 +63,9 @@ L). This chapter of the tutorial is divided into two main sections: 1) basic, cleartext authentication and 2) hash-based authentication. -You can checkout the source code for this example from the catalyst -subversion repository as per the instructions in +Source code for the tutorial in included in the F directory +of the Tutorial Virtual machine (one subdirectory per chapter). There +are also instructions for downloading the code in L. @@ -166,7 +167,7 @@ C<1;>: # 2) Name of has_many() relationship this many_to_many() is shortcut for # 3) Name of belongs_to() relationship in model class of has_many() above # You must already have the has_many() defined to use a many_to_many(). - __PACKAGE__->many_to_many(roles => 'user_roles', 'role_id'); + __PACKAGE__->many_to_many(roles => 'user_roles', 'role'); The code for this update is obviously very similar to the edits we made to the C and C classes created in @@ -694,7 +695,7 @@ Then run the following command: $ DBIC_TRACE=1 perl -Ilib set_hashed_passwords.pl -We had to use the C<-Ilib> argument to tell perl to look under the +We had to use the C<-Ilib> argument to tell Perl to look under the C directory for our C model. The DBIC_TRACE output should show that the update worked: @@ -863,6 +864,8 @@ C to the list of plugins: ConfigLoader Static::Simple + StackTrace + Authentication Session @@ -951,6 +954,10 @@ token, it is ignored -- thereby keeping the state of our status/error messages in sync with the users actions). +You can jump to the next chapter of the tutorial here: +L + + =head1 AUTHOR Kennedy Clark, C