X-Git-Url: https://git.decadent.org.uk/gitweb/?a=blobdiff_plain;f=lib%2FMaypole%2FView%2FTT.pm;h=7a2ab0307501e6da5fe6281b2c17ece946966b37;hb=a183ff6bda2ae98ef8f4a4f979647052e0020dea;hp=6f9fbc6bbc7115278c717983066e403670c7c9aa;hpb=6c19a422c2c4bc3457f311ffc0403b8644690074;p=maypole.git diff --git a/lib/Maypole/View/TT.pm b/lib/Maypole/View/TT.pm index 6f9fbc6..7a2ab03 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; @@ -29,14 +32,33 @@ sub template { if ($self->{tt}->process($template_file, { $self->vars($r) }, \$output )) { $r->{output} = $output; return OK; - } - else { + } else { $r->{error} = "TT error for template '$template_file'\n" . $self->{tt}->error; return ERROR; } } -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 @@ -54,7 +76,13 @@ Maypole::View::TT - A Template Toolkit view class for Maypole ..... - [%# Template Toolkit directives and maypole macros go here %] + [% PROCESS macros %] + + [% pager %] + + [% link %] + + [% maybe_link_view %] =head1 DESCRIPTION @@ -74,6 +102,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 @@ -112,6 +144,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 %] @@ -247,15 +282,72 @@ 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...TO DO +Maypole provides a collection of useful and powerful macros in the templates/factory/macros + and other templates. These can be used in any template with [% PROCESS templatename %]. =head2 link -=head2 other macros +This creates an to a command in the Apache::MVC system by +catenating the base URL, table, command, and any arguments. + +=head2 maybe_link_view + +C takes something returned from the database - either +some ordinary data, or an object in a related class expanded by a +has-a relationship. If it is an object, it constructs a link to the view +command for that object. Otherwise, it just displays the data. + +=head2 pager -=head2 finish this documentation +This is an include template rather than a macro, and it controls the pager +display at the bottom (by default) of the factory list and search views/template. +It expects a C template argument which responds to the L interface. + +This macro is in the pager template and used as : + +[% PROCESS pager %] + +Maypole provides a pager for list and search actions, otherwise you can +provide a pager in the template using Template::Plugin::Pagination. + +[% USE pager = Pagination(objects, page.current, page.rows) %] +... +[% PROCESS pager %] + +The pager will use a the request action as the action in the url unless the +pager_action variable is set, which it will use instead if available. + +=head2 other macros =head1 AUTHOR @@ -263,3 +355,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(" , ") %]
+ + + + +