X-Git-Url: https://git.decadent.org.uk/gitweb/?a=blobdiff_plain;f=lib%2FMaypole%2FView%2FTT.pm;h=b7a59a2f565813c9a5c3c4a7ffaee12d845ac232;hb=1c8db728a3fb5adb4f0ea876ea1316457700edf8;hp=8b12debb15be5217a95022770a064f920129e4e1;hpb=ad04e7a4a8d154b90262dbc4464c3494fcb46253;p=maypole.git diff --git a/lib/Maypole/View/TT.pm b/lib/Maypole/View/TT.pm index 8b12deb..b7a59a2 100644 --- a/lib/Maypole/View/TT.pm +++ b/lib/Maypole/View/TT.pm @@ -4,39 +4,76 @@ use Maypole::Constants; use Template; use File::Spec::Functions qw(catdir tmpdir); +our $error_template; +{ local $/; $error_template = ; } + use strict; -our $VERSION = 2.11; sub template { - my ( $self, $r ) = @_; - - unless ($self->{tt}) { - my $view_options = $r->config->view_options || {}; - $self->{provider} = Template::Provider->new($view_options); - $self->{tt} = Template->new({ - %$view_options, - LOAD_TEMPLATES => [ $self->{provider} ], - }); + my ( $self, $r ) = @_; + unless ($self->{tt}) { + my $view_options = $r->config->view_options || {}; + $self->{provider} = Template::Provider->new($view_options); + $self->{tt} = Template->new({ + %$view_options, + LOAD_TEMPLATES => [ $self->{provider} ], + }); + } + + $self->{provider}->include_path([ $self->paths($r) ]); + + my $template_file = $r->template; + + my $ext = $r->config->template_extension; + $template_file .= $ext if defined $ext; + + my $output; + my $processed_ok = eval{$self->{tt}->process($template_file, { $self->vars($r) }, \$output );}; + if ($processed_ok) { + $r->{output} = $output; + return OK; + } else { + if ($@) { + warn "fatal error in template '$template_file' : $@\n"; + $r->{error} = "fatal error in template '$template_file' : $@"; + } else { + warn "TT error for template '$template_file'\n" . $self->{tt}->error; + $r->{error} = "TT error for template '$template_file'\n" . $self->{tt}->error; } + return ERROR; + } +} - $self->{provider}->include_path([ $self->paths($r) ]); - - my $template_file = $r->template; - my $ext = $r->config->template_extension; - $template_file .= $ext if defined $ext; +sub report_error { + my ($self, $r, $error, $type) = @_; my $output; - if ($self->{tt}->process($template_file, { $self->vars($r) }, \$output )) { + + warn "self : $self, r : $r, error : $error, type : $type\n"; + + # Need to be very careful here. + my $tt = Template->new; + unless (ref $r->{config}) { + warn "no config for this request\n"; + $error .= '
There was a problem finding configuration for this request'; + $r->{config} ||= {}; + } + if ($tt->process(\$error_template, + { err_type => $type, error => $error, + config => $r->{config}, + request => $r, + paths => $self->paths($r), + 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; } - else { - $r->{error} = "TT error for template '$template_file'\n" . $self->{tt}->error; - return ERROR; - } + return ERROR; } -1; =head1 NAME @@ -80,6 +117,10 @@ options. Processes the template and sets the output. See L +=item report_error + +Reports the details of an error, current state and parameters + =back =head1 TEMPLATE TOOLKIT INTRODUCTION @@ -118,6 +159,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 %] @@ -242,6 +286,18 @@ truncate, format, escape or encode trivially. A useful selection is included with Template Toolkit and they can also be found on CPAN or can be written easily. See L. +TT provides stderr and stdout filters, which allow you to write handy macros +like this one to output debug information to your web server log, etc : + +=over 4 + +[% MACRO debug_msg(text) + FILTER stderr; "[TT debug_msg] $text\n"; END; +%] + +=back + + TT Macros allow you to reuse small blocks of content, directives, etc. The MACRO directive allows you to define a directive or directive block which is then evaluated each time the macro is called. Macros can be passed named parameters @@ -253,6 +309,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 +382,59 @@ 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 attribute = ["model_class", "table", "template", "path", + "content_type", "document_encoding", "action", "args", "objects"] %] + + [% END %] +
[% attribute %] [% + request.$attribute.list.join(" , ") %]
+ +

Website / Template Paths

+ + + +
Base URI [% request.config.uri_base %]
Paths [% paths %]
+ +

Application configuration

+ + + + + +
Model [% request.config.model %]
View [% request.config.view %]
Classes [% request.config.classes.list.join(" , ") %]
Tables [% request.config.display_tables.list.join(" , ") %]
+ + +