X-Git-Url: https://git.decadent.org.uk/gitweb/?a=blobdiff_plain;f=lib%2FMaypole%2FView%2FTT.pm;h=7106b7a563f0d5593fdbe3860752aa488b1b575f;hb=28823167d12d4cd1419cc6a58900c0fc5819e1af;hp=8b12debb15be5217a95022770a064f920129e4e1;hpb=ad04e7a4a8d154b90262dbc4464c3494fcb46253;p=maypole.git diff --git a/lib/Maypole/View/TT.pm b/lib/Maypole/View/TT.pm index 8b12deb..7106b7a 100644 --- a/lib/Maypole/View/TT.pm +++ b/lib/Maypole/View/TT.pm @@ -4,6 +4,9 @@ use Maypole::Constants; use Template; use File::Spec::Functions qw(catdir tmpdir); +our $error_template; +{ local $/; $error_template = ; } + use strict; our $VERSION = 2.11; @@ -36,7 +39,27 @@ sub template { } } -1; + +sub report_error { + my ($self, $r, $error, $type) = @_; + my $output; + # Need to be very careful here. + my $tt = Template->new; + if ($tt->process(\$error_template, + { err_type => $type, error => $error, + config => { %{$r->{config}}}, + request => $r, # We have that at least + eval{$self->vars($r)} }, \$output )) { + $r->{output} = $output; + if ($tt->error) { $r->{output} = "Even the error template + errored - ".$tt->error.""; } + $r->{content_type} ||= "text/html"; + $r->{document_encoding} ||= "utf-8"; + return OK; + } + return ERROR; +} + =head1 NAME @@ -118,6 +141,9 @@ or CALL a method or operation which will also not return anything. You can specify expressions using the logical (and, or, not, ?:) and mathematic operators (+ - * / % mod div). +Results of TT commands are interpolated in the place of the template tags, unless +using SET or CALL, i.e. [% SET foo = 1 %], [% GET foo.bar('quz'); %] + =over 4 [% template.title or default.title %] @@ -253,6 +279,34 @@ and useful macros in the templates/ directory of the package and these are used in the beerdb and default templates. See the MACRO section of the L documentation. +=head1 ACCESSING MAYPOLE VALUES + +=head2 request + +You can access the request in your templates in order to see the action, table, etc as well +as parameters passed through forms : + +for example + +Hello [% request.params.forename %] [% request.params.surname %] ! + +or + +Are you want to [% request.action %] in the [% request.table %] ? + +=head2 config + +You can access your maypole application configuration through the config variable : + + + +=head2 object and objects + +Objects are passed to the request using r->objects($arrayref) and are accessed in the templates +as an array called objects. + +[% FOR objects %] [% object %] [% END %] + =head1 MAYPOLE MACROS AND FILTERS Maypole provides a collection of useful and powerful macros in the templates/factory/macros @@ -298,3 +352,55 @@ Simon Cozens =cut +1; + +__DATA__ +Maypole error page + + +

Maypole application error

+ +

This application living at [%request.config.uri_base%], +[%request.config.application_name || "which is unnamed" %], has +produced an error. The adminstrator should be able to understand +this error message and fix the problem.

+ +

Some basic facts

+ +

The error was found in the [% err_type %] stage of processing +the path "[% request.path %]". The error text returned was: +

+
+    [% error %]
+
+ +

Request details

+ + + [% FOR thing = ["model_class", "table", "template", "path", + "content_type", "document_encoding", "action", "args", "objects"] %] + + [% END %] +
[%thing %] [% + request.$thing.list.join(" , ") %]
+ +

Application configuration

+ + [% FOR thing = config.keys %] + + [% END %] +
[%thing %] [% + config.$thing.list.join(" , ") %]
+ + + + +