X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=lib%2FCatalyst%2FManual%2FCookbook.pod;h=f689e411636752cfff6bdb80c55eb72739dc0128;hb=682c50f154e3c9fdcb599dd9caf6f95289322703;hp=6b5d47ad64520beb7311553a7c3df2c6f7e858fc;hpb=7e4aa7c669d1a0e4e8183c6c9186a77b0079ad3d;p=catagits%2FCatalyst-Manual.git diff --git a/lib/Catalyst/Manual/Cookbook.pod b/lib/Catalyst/Manual/Cookbook.pod index 6b5d47a..f689e41 100644 --- a/lib/Catalyst/Manual/Cookbook.pod +++ b/lib/Catalyst/Manual/Cookbook.pod @@ -112,7 +112,7 @@ retrieve the user data for you. =head3 Using a session Once the session modules are loaded, the session is available as C<< -$c->session >>, and can be writen to and read from as a simple hash +$c->session >>, and can be written to and read from as a simple hash reference. =head3 EXAMPLE @@ -851,7 +851,7 @@ organization provided makes it much easier to standardize pages and make changes when they are (inevitably) needed. The template files that you will create for your application will go -into root/src, and you don't need to worry about putting the the +into root/src, and you don't need to worry about putting the or sections; just put in the content. The WRAPPER will the rest of the page around your template for you. @@ -1425,13 +1425,13 @@ And in the controller: $c->stash->{template} = 'file_upload.html'; } -Creq->upload)> loops automatically over all file +C<< for my $field ($c->req->upload) >> loops automatically over all file input fields and gets input names. After that is basic file saving code, just like in single file upload. Notice: Cing might not be what you want to do, when an error occurs, but it works as an example. A better idea would be to store -error C<$!> in $c->stash->{error} and show a custom error template +error C<$!> in C<< $c->stash->{error} >> and show a custom error template displaying this message. For more information about uploads and usable methods look at