X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=catagits%2FCatalyst-Manual.git;a=blobdiff_plain;f=lib%2FCatalyst%2FManual%2FCookbook.pod;h=a550208b3b65c9b434fbc0eefa1a7f0e44224ae8;hp=6127ceca053c560cc50026da9f5489fb9f6acefe;hb=429d1caf111575afa4c25287cc48d7ed712af327;hpb=5336f54651dd781138086b9081b85b6839452a76 diff --git a/lib/Catalyst/Manual/Cookbook.pod b/lib/Catalyst/Manual/Cookbook.pod index 6127cec..a550208 100644 --- a/lib/Catalyst/Manual/Cookbook.pod +++ b/lib/Catalyst/Manual/Cookbook.pod @@ -70,7 +70,7 @@ Normally you enable the debugging info by adding the C<-Debug> flag to your C statement . However, you can also enable it using environment variable, so you can (for example) get debug info without modifying your application scripts. Just set C or -CMYAPPE_DEBUG> to a true value. +C<< _DEBUG >> to a true value. =head2 Sessions @@ -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 @@ -1625,7 +1625,7 @@ static content to the view, perhaps like this: This code will only forward to the view if a template has been previously defined by a controller and if there is not already data in -C<$c-Eres-Ebody>. +C<< $c->res->body >>. Next, create a controller to handle requests for the /static path. Use the Helper to save time. This command will create a stub controller as