From: Jesse Sheidlower Date: Fri, 15 Jul 2005 01:21:39 +0000 (+0000) Subject: Custom Error Page added to Cookbook X-Git-Tag: 5.7099_04~1259 X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=catagits%2FCatalyst-Runtime.git;a=commitdiff_plain;h=6d23e1f47ee595a56d8e7ac825ccae1451a8826f Custom Error Page added to Cookbook --- diff --git a/lib/Catalyst/Manual/Cookbook.pod b/lib/Catalyst/Manual/Cookbook.pod index af8d13e..7c6dcf6 100644 --- a/lib/Catalyst/Manual/Cookbook.pod +++ b/lib/Catalyst/Manual/Cookbook.pod @@ -485,8 +485,7 @@ When using Apache, you can completely bypass Catalyst and the Static controller by intercepting requests for the C path at the server level. All that is required is to define a DocumentRoot and add a separate Location block for your static content. Here is a complete -config for this application under mod_perl 1.x; variations, some of -which could be simpler, are left as an exercise for the reader: +config for this application under mod_perl 1.x: use lib qw(/var/www/MyApp/lib); @@ -505,6 +504,13 @@ which could be simpler, are left as an exercise for the reader: +And here's a simpler example that'll get you started: + + Alias /static/ "/my/static/files/" + + SetHandler none + + =head2 Forwarding with arguments Sometimes you want to pass along arguments when forwarding to another @@ -602,20 +608,43 @@ simple component in Catalyst that slurps in an outside Model: and that's it! Now C is part of your Cat app as C. -=head1 Serving static files with Apache. +=head2 Delivering a Custom Error Page -When deploying your application it's a waste to serve static files -with Catalyst. Instead, set up something like this: +By default, Catalyst will display its own error page whenever it +encounters an error in your application. When running under C<-Debug> +mode, the error page is a useful screen including the error message and +a full Data::Dumper output of the C<$c> context object. When not in +C<-Debug>, users see a simple "Please come back later" screen. - Alias /static/ "/my/static/files/" - - SetHandler none - +To use a custom error page, use a special C method to short-circut +the error processing. The following is an example; you might want to +adjust it further depending on the needs of your application (for +example, any calls to C will probably need to go into this +C method; see L). -To match the location of your static files. + sub end : Private { + my ( $self, $c ) = @_; + + if ( scalar @{ $c->error } ) { + $c->stash->{errors} = $c->error; + $c->stash->{template} = 'errors.tt'; + $c->forward('MyApp::View::TT'); + $c->{error} = []; + } + + return 1 if $c->response->status =~ /^3\d\d$/; + return 1 if $c->response->body; + + unless ( $c->response->content_type ) { + $c->response->content_type('text/html; charset=utf-8'); + } + + $c->forward('MyApp::View::TT'); + } +You can manually set errors in your code to trigger this page by calling -=cut + $c->error( 'You broke me!' ); =head1 AUTHOR