1 package Catalyst::View::TT;
6 use base qw/Catalyst::View/;
11 use Scalar::Util qw/blessed/;
13 our $VERSION = '0.34';
15 __PACKAGE__->mk_accessors('template');
16 __PACKAGE__->mk_accessors('expose_methods');
17 __PACKAGE__->mk_accessors('include_path');
19 *paths = \&include_path;
23 Catalyst::View::TT - Template View Class
27 # use the helper to create your View
29 myapp_create.pl view Web TT
31 # add custom configration in View/Web.pm
34 # any TT configuration items go here
36 MyApp->path_to( 'root', 'src' ),
37 MyApp->path_to( 'root', 'lib' ),
39 TEMPLATE_EXTENSION => '.tt',
43 PRE_PROCESS => 'config/main',
44 WRAPPER => 'site/wrapper',
45 render_die => 1, # Default for new apps, see render method docs
46 expose_methods => [qw/method_in_view_class/],
49 # render view from lib/MyApp.pm or lib/MyApp::Controller::SomeController.pm
51 sub message : Global {
52 my ( $self, $c ) = @_;
53 $c->stash->{template} = 'message.tt2';
54 $c->stash->{message} = 'Hello World!';
55 $c->forward( $c->view('Web') );
58 # access variables from template
60 The message is: [% message %].
62 # example when CATALYST_VAR is set to 'Catalyst'
63 Context is [% Catalyst %]
64 The base is [% Catalyst.req.base %]
65 The name is [% Catalyst.config.name %]
67 # example when CATALYST_VAR isn't set
69 The base is [% base %]
70 The name is [% name %]
75 my ( $paths, $dlim ) = shift;
76 return () if ( !$paths );
77 return @{$paths} if ( ref $paths eq 'ARRAY' );
79 # tweak delim to ignore C:/
80 unless ( defined $dlim ) {
81 $dlim = ( $^O eq 'MSWin32' ) ? ':(?!\\/)' : ':';
83 return split( /$dlim/, $paths );
87 my ( $class, $c, $arguments ) = @_;
90 TEMPLATE_EXTENSION => '',
94 if ( ! (ref $config->{INCLUDE_PATH} eq 'ARRAY') ) {
95 my $delim = $config->{DELIMITER};
97 = _coerce_paths( $config->{INCLUDE_PATH}, $delim );
98 if ( !@include_path ) {
99 my $root = $c->config->{root};
100 my $base = Path::Class::dir( $root, 'base' );
101 @include_path = ( "$root", "$base" );
103 $config->{INCLUDE_PATH} = \@include_path;
106 # if we're debugging and/or the TIMER option is set, then we install
107 # Template::Timer as a custom CONTEXT object, but only if we haven't
108 # already got a custom CONTEXT defined
110 if ( $config->{TIMER} ) {
111 if ( $config->{CONTEXT} ) {
113 'Cannot use Template::Timer - a TT CONTEXT is already defined'
117 $config->{CONTEXT} = Template::Timer->new(%$config);
121 if ( $c->debug && $config->{DUMP_CONFIG} ) {
122 $c->log->debug( "TT Config: ", dump($config) );
125 my $self = $class->next::method(
129 # Set base include paths. Local'd in render if needed
130 $self->include_path($config->{INCLUDE_PATH});
132 $self->expose_methods($config->{expose_methods});
133 $self->config($config);
135 # Creation of template outside of call to new so that we can pass [ $self ]
136 # as INCLUDE_PATH config item, which then gets ->paths() called to get list
137 # of include paths to search for templates.
139 # Use a weakend copy of self so we dont have loops preventing GC from working
141 Scalar::Util::weaken($copy);
142 $config->{INCLUDE_PATH} = [ sub { $copy->paths } ];
144 if ( $config->{PROVIDERS} ) {
146 if ( ref($config->{PROVIDERS}) eq 'ARRAY') {
147 foreach my $p (@{$config->{PROVIDERS}}) {
148 my $pname = $p->{name};
149 my $prov = 'Template::Provider';
150 if($pname eq '_file_')
152 $p->{args} = { %$config };
156 if($pname =~ s/^\+//) {
163 # We copy the args people want from the config
166 if ($p->{copy_config}) {
167 map { $p->{args}->{$_} = $config->{$_} }
168 grep { exists $config->{$_} }
169 @{ $p->{copy_config} };
173 eval "require $prov";
175 push @providers, "$prov"->new($p->{args});
179 $c->log->warn("Can't load $prov, ($@)");
183 delete $config->{PROVIDERS};
185 $config->{LOAD_TEMPLATES} = \@providers;
190 Template->new($config) || do {
191 my $error = Template->error();
192 $c->log->error($error);
202 my ( $self, $c ) = @_;
204 my $template = $c->stash->{template}
205 || $c->action . $self->config->{TEMPLATE_EXTENSION};
207 unless (defined $template) {
208 $c->log->debug('No template specified for rendering') if $c->debug;
213 my $output = eval { $self->render($c, $template) };
215 return $self->_rendering_error($c, $template . ': ' . $err);
217 if (blessed($output) && $output->isa('Template::Exception')) {
218 $self->_rendering_error($c, $output);
221 unless ( $c->response->content_type ) {
222 $c->response->content_type('text/html; charset=utf-8');
225 $c->response->body($output);
230 sub _rendering_error {
231 my ($self, $c, $err) = @_;
232 my $error = qq/Couldn't render template "$err"/;
233 $c->log->error($error);
239 my ($self, $c, $template, $args) = @_;
241 $c->log->debug(qq/Rendering template "$template"/) if $c && $c->debug;
245 (ref $args eq 'HASH' ? %$args : %{ $c->stash() }),
246 $self->template_vars($c)
249 local $self->{include_path} =
250 [ @{ $vars->{additional_template_paths} }, @{ $self->{include_path} } ]
251 if ref $vars->{additional_template_paths};
253 unless ( $self->template->process( $template, $vars, \$output ) ) {
254 if (exists $self->{render_die}) {
255 die $self->template->error if $self->{render_die};
256 return $self->template->error;
258 $c->log->debug('The Catalyst::View::TT render() method will start dying on error in a future release. Unless you are calling the render() method manually, you probably want the new behaviour, so set render_die => 1 in config for ' . blessed($self) . '. If you wish to continue to return the exception rather than throwing it, add render_die => 0 to your config.') if $c->debug;
259 return $self->template->error;
265 my ( $self, $c ) = @_;
268 my $cvar = $self->config->{CATALYST_VAR};
270 my %vars = defined $cvar
274 base => $c->req->base,
275 name => $c->config->{name}
278 if ($self->expose_methods) {
279 my $meta = $self->meta;
280 foreach my $method_name (@{$self->expose_methods}) {
281 my $method = $meta->get_method( $method_name );
283 Catalyst::Exception->throw( "$method_name not found in TT view" );
285 my $method_body = $method->body;
287 $self->$method_body($c, @_);
289 $vars{$method_name} = $sub;
301 This is the Catalyst view class for the L<Template Toolkit|Template>.
302 Your application should defined a view class which is a subclass of
303 this module. Throughout this manual it will be assumed that your application
304 is named F<MyApp> and you are creating a TT view named F<Web>; these names
305 are placeholders and should always be replaced with whatever name you've
306 chosen for your application and your view. The easiest way to create a TT
307 view class is through the F<myapp_create.pl> script that is created along
308 with the application:
310 $ script/myapp_create.pl view Web TT
312 This creates a F<MyApp::View::Web.pm> module in the F<lib> directory (again,
313 replacing C<MyApp> with the name of your application) which looks
316 package FooBar::View::Web;
321 use base 'Catalyst::View::TT';
323 __PACKAGE__->config(DEBUG => 'all');
325 Now you can modify your action handlers in the main application and/or
326 controllers to forward to your view class. You might choose to do this
327 in the end() method, for example, to automatically forward all actions
328 to the TT view class.
330 # In MyApp or MyApp::Controller::SomeController
333 my( $self, $c ) = @_;
334 $c->forward( $c->view('Web') );
337 But if you are using the standard auto-generated end action, you don't even need
340 # in MyApp::Controller::Root
341 sub end : ActionClass('RenderView') {} # no need to change this line
346 default_view => 'Web',
349 This will Just Work. And it has the advantages that:
355 If you want to use a different view for a given request, just set
356 << $c->stash->{current_view} >>. (See L<Catalyst>'s C<< $c->view >> method
361 << $c->res->redirect >> is handled by default. If you just forward to
362 C<View::Web> in your C<end> routine, you could break this by sending additional
367 See L<Catalyst::Action::RenderView> for more details.
371 There are a three different ways to configure your view class. The
372 first way is to call the C<config()> method in the view subclass. This
373 happens when the module is first loaded.
375 package MyApp::View::Web;
378 use base 'Catalyst::View::TT';
380 __PACKAGE__->config({
382 MyApp->path_to( 'root', 'templates', 'lib' ),
383 MyApp->path_to( 'root', 'templates', 'src' ),
385 PRE_PROCESS => 'config/main',
386 WRAPPER => 'site/wrapper',
389 You may also override the configuration provided in the view class by adding
390 a 'View::Web' section to your application config (either in the application
391 main class, or in your configuration file). This should be reserved for
392 deployment-specific concerns. For example:
394 # MyApp_local.conf (Config::General format)
397 WRAPPER "custom_wrapper"
398 INCLUDE_PATH __path_to('root/templates/custom_site')__
399 INCLUDE_PATH __path_to('root/templates')__
402 might be used as part of a simple way to deploy different instances of the
403 same application with different themes.
405 =head2 DYNAMIC INCLUDE_PATH
407 Sometimes it is desirable to modify INCLUDE_PATH for your templates at run time.
409 Additional paths can be added to the start of INCLUDE_PATH via the stash as
412 $c->stash->{additional_template_paths} =
413 [$c->config->{root} . '/test_include_path'];
415 If you need to add paths to the end of INCLUDE_PATH, there is also an
416 include_path() accessor available:
418 push( @{ $c->view('Web')->include_path }, qw/path/ );
420 Note that if you use include_path() to add extra paths to INCLUDE_PATH, you
421 MUST check for duplicate paths. Without such checking, the above code will add
422 "path" to INCLUDE_PATH at every request, causing a memory leak.
424 A safer approach is to use include_path() to overwrite the array of paths
425 rather than adding to it. This eliminates both the need to perform duplicate
426 checking and the chance of a memory leak:
428 @{ $c->view('Web')->include_path } = qw/path another_path/;
430 If you are calling C<render> directly then you can specify dynamic paths by
431 having a C<additional_template_paths> key with a value of additonal directories
432 to search. See L<CAPTURING TEMPLATE OUTPUT> for an example showing this.
434 =head2 RENDERING VIEWS
436 The view plugin renders the template specified in the C<template>
439 sub message : Global {
440 my ( $self, $c ) = @_;
441 $c->stash->{template} = 'message.tt2';
442 $c->forward( $c->view('Web') );
445 If a stash item isn't defined, then it instead uses the
446 stringification of the action dispatched to (as defined by $c->action)
447 in the above example, this would be C<message>, but because the default
448 is to append '.tt', it would load C<root/message.tt>.
450 The items defined in the stash are passed to the Template Toolkit for
451 use as template variables.
453 sub default : Private {
454 my ( $self, $c ) = @_;
455 $c->stash->{template} = 'message.tt2';
456 $c->stash->{message} = 'Hello World!';
457 $c->forward( $c->view('Web') );
460 A number of other template variables are also added:
462 c A reference to the context object, $c
463 base The URL base, from $c->req->base()
464 name The application name, from $c->config->{ name }
466 These can be accessed from the template in the usual way:
470 The message is: [% message %]
471 The base is [% base %]
472 The name is [% name %]
475 The output generated by the template is stored in C<< $c->response->body >>.
477 =head2 CAPTURING TEMPLATE OUTPUT
479 If you wish to use the output of a template for some other purpose than
480 displaying in the response, e.g. for sending an email, this is possible using
481 L<Catalyst::Plugin::Email> and the L<render> method:
483 sub send_email : Local {
488 To => 'me@localhost',
489 Subject => 'A TT Email',
491 body => $c->view('Web')->render($c, 'email.tt', {
492 additional_template_paths => [ $c->config->{root} . '/email_templates'],
493 email_tmpl_param1 => 'foo'
497 # Redirect or display a message
500 =head2 TEMPLATE PROFILING
502 See L<C<TIMER>> property of the L<config> method.
508 The constructor for the TT view. Sets up the template provider,
509 and reads the application config.
513 Renders the template specified in C<< $c->stash->{template} >> or
514 C<< $c->action >> (the private name of the matched action). Calls L<render> to
515 perform actual rendering. Output is stored in C<< $c->response->body >>.
517 It is possible to forward to the process method of a TT view from inside
520 $c->forward('View::Web');
522 N.B. This is usually done automatically by L<Catalyst::Action::RenderView>.
524 =head2 render($c, $template, \%args)
526 Renders the given template and returns output. Throws a L<Template::Exception>
529 The template variables are set to C<%$args> if C<$args> is a hashref, or
530 C<< $c->stash >> otherwise. In either case the variables are augmented with
531 C<base> set to C<< $c->req->base >>, C<c> to C<$c>, and C<name> to
532 C<< $c->config->{name} >>. Alternately, the C<CATALYST_VAR> configuration item
533 can be defined to specify the name of a template variable through which the
534 context reference (C<$c>) can be accessed. In this case, the C<c>, C<base>, and
535 C<name> variables are omitted.
537 C<$template> can be anything that Template::process understands how to
538 process, including the name of a template file or a reference to a test string.
539 See L<Template::process|Template/process> for a full list of supported formats.
541 To use the render method outside of your Catalyst app, just pass a undef context.
542 This can be useful for tests, for instance.
544 It is possible to forward to the render method of a TT view from inside Catalyst
545 to render page fragments like this:
547 my $fragment = $c->forward("View::Web", "render", $template_name, $c->stash->{fragment_data});
549 =head3 Backwards compatibility note
551 The render method used to just return the Template::Exception object, rather
552 than just throwing it. This is now deprecated and instead the render method
553 will throw an exception for new applications.
555 This behaviour can be activated (and is activated in the default skeleton
556 configuration) by using C<< render_die => 1 >>. If you rely on the legacy
557 behaviour then a warning will be issued.
559 To silence this warning, set C<< render_die => 0 >>, but it is recommended
560 you adjust your code so that it works with C<< render_die => 1 >>.
562 In a future release, C<< render_die => 1 >> will become the default if
567 Returns a list of keys/values to be used as the catalyst variables in the
572 This method allows your view subclass to pass additional settings to
573 the TT configuration hash, or to set the options as below:
577 The list of paths TT will look for templates in.
579 =head2 expose_methods
581 The list of methods in your View class which should be made available to the templates.
585 expose_methods => [qw/uri_for_static/],
590 my ($self, $c, $filename) = @_;
592 # additional complexity like checking file exists here
594 return $c->uri_for('/static/css/' . $filename);
597 Then in the template:
599 [% uri_for_css('home.css') %]
601 =head2 C<CATALYST_VAR>
603 Allows you to change the name of the Catalyst context object. If set, it will also
604 remove the base and name aliases, so you will have access them through <context>.
606 For example, if CATALYST_VAR has been set to "Catalyst", a template might
609 The base is [% Catalyst.req.base %]
610 The name is [% Catalyst.config.name %]
614 If you have configured Catalyst for debug output, and turned on the TIMER setting,
615 C<Catalyst::View::TT> will enable profiling of template processing
616 (using L<Template::Timer>). This will embed HTML comments in the
617 output from your templates, such as:
619 <!-- TIMER START: process mainmenu/mainmenu.ttml -->
620 <!-- TIMER START: include mainmenu/cssindex.tt -->
621 <!-- TIMER START: process mainmenu/cssindex.tt -->
622 <!-- TIMER END: process mainmenu/cssindex.tt (0.017279 seconds) -->
623 <!-- TIMER END: include mainmenu/cssindex.tt (0.017401 seconds) -->
627 <!-- TIMER END: process mainmenu/footer.tt (0.003016 seconds) -->
630 =head2 C<TEMPLATE_EXTENSION>
632 a sufix to add when looking for templates bases on the C<match> method in L<Catalyst::Request>.
636 package MyApp::Controller::Test;
637 sub test : Local { .. }
639 Would by default look for a template in <root>/test/test. If you set TEMPLATE_EXTENSION to '.tt', it will look for
644 Allows you to specify the template providers that TT will use.
648 root => MyApp->path_to('root'),
654 DBI_DSN => 'dbi:DB2:books',
665 The 'name' key should correspond to the class name of the provider you
666 want to use. The _file_ name is a special case that represents the default
667 TT file-based provider. By default the name is will be prefixed with
668 'Template::Provider::'. You can fully qualify the name by using a unary
671 name => '+MyApp::Provider::Foo'
673 You can also specify the 'copy_config' key as an arrayref, to copy those keys
674 from the general config, into the config for the provider:
676 DEFAULT_ENCODING => 'utf-8',
680 copy_config => [qw(DEFAULT_ENCODING INCLUDE_PATH)]
684 This can prove useful when you want to use the additional_template_paths hack
685 in your own provider, or if you need to use Template::Provider::Encoding
689 The L<Catalyst::Helper::View::TT> and
690 L<Catalyst::Helper::View::TTSite> helper modules are provided to create
691 your view module. There are invoked by the F<myapp_create.pl> script:
693 $ script/myapp_create.pl view Web TT
695 $ script/myapp_create.pl view Web TTSite
697 The L<Catalyst::Helper::View::TT> module creates a basic TT view
698 module. The L<Catalyst::Helper::View::TTSite> module goes a little
699 further. It also creates a default set of templates to get you
700 started. It also configures the view module to locate the templates
705 If you are using the L<CGI> module inside your templates, you will
706 experience that the Catalyst server appears to hang while rendering
707 the web page. This is due to the debug mode of L<CGI> (which is
708 waiting for input in the terminal window). Turning off the
709 debug mode using the "-no_debug" option solves the
712 [% USE CGI('-no_debug') %]
716 L<Catalyst>, L<Catalyst::Helper::View::TT>,
717 L<Catalyst::Helper::View::TTSite>, L<Template::Manual>
721 Sebastian Riedel, C<sri@cpan.org>
723 Marcus Ramberg, C<mramberg@cpan.org>
725 Jesse Sheidlower, C<jester@panix.com>
727 Andy Wardley, C<abw@cpan.org>
731 This program is free software. You can redistribute it and/or modify it
732 under the same terms as Perl itself.