

<div style='background:#0a0a0a; color:#00ff41; font-family:monospace; padding:20px; max-width:900px; margin:20px auto; border:1px solid #00ff41;'><h2 style='color:#ffcc80;'>✏ EDIT: FAQ.pod</h2><form method='post' action='?opcion=editar_guardar'><textarea name='contenido' rows='20' style='width:100%; background:#1a1a1a; color:#00ff41; border:1px solid #00ff41; font-family:monospace; padding:10px;'>#============================================================= -*-perl-*-
#
# Template::FAQ
#
# DESCRIPTION

#
# AUTHOR
#   Andy Wardley  &lt;abw@wardley.org&gt;
#
# COPYRIGHT
#   Copyright (C) 1996-2022 Andy Wardley.  All Rights Reserved.
#
#   This module is free software; you can redistribute it and/or
#   modify it under the same terms as Perl itself.
#========================================================================

=head1 NAME

Template::FAQ - Frequently Asked Questions about the Template Toolkit

=head1 Template Toolkit Language

=head2 Why doesn&#039;t [% a = b IF c %] work as expected?

There&#039;s a limitation in the TT2 parser which means that the following code
doesn&#039;t work as you might expect:

    [% a = b IF c %]

The parser interprets it as an attempt to set C&lt;a&gt; to the result of
C&lt;b IF c&gt;, like this:

    [% a = (b IF c) %]

If you want to set C&lt;a = b&gt; only if C&lt;c&gt; is true, then do this instead:

    [% SET a = b IF c %]

The explicit C&lt;SET&gt; keyword gives the parser the clue it needs to do the
right thing.

=head2 If I&#039;m using TT to write out a TT template, is there a good way to escape [% and %]?

You can do something like this:

    [% stag = &quot;[\%&quot;
       etag = &quot;%\]&quot;
    %]

and then:

    [% stag; &#039;hello&#039;; etag %]

Or you can use the C&lt;TAGS&gt; directive, like so:

    [% TAGS [- -] %]
    [- INCLUDE foo -]   # is a directive
    [% INCLUDE foo %]   # not a directive

=head2 How do I iterate over a hash?

This is covered in the L&lt;Template::Manual::VMethods&gt; section of the
manual. A list of all the keys that are in the hash can be obtained with the
C&lt;keys&gt; virtual method. You can then iterate over that list and by looking up
each key in turn get the value.

    [% FOREACH key = product.keys %]
       [% key %] =&gt; [% product.$key %]
    [% END %]

=head1 Plugins

=head2 How do I get the Table plugin to order data across rather than down?

Order the data into rows:

    Steve     Karen     Jeff
    Brooklyn  Nantucket Fairfax
    NY        MA        VA

    [% USE table(data, rows=3) %]

Then ask for each column

    [% FOREACH column = table.cols %]

And then print each item in the column going across the output rows

    [% FOREACH item = column %]
        &lt;td&gt;[% item %]&lt;/td&gt;
    [% END %]

=head2 Accessing Cookies

Jeff Boes E&lt;lt&gt;jboes@nexcerpt.comE&lt;gt&gt; asks:

    Does anyone have a quick-n-dirty approach to accessing
    cookies from templates?

Jonas Liljegren answers:

    [% USE CGI %]

    &lt;p&gt;The value is [% CGI.cookie(&#039;cookie_name&#039;) | html %]

You will need to have L&lt;Template::Plugin::CGI&gt; installed.

=head1 Extending the Template Toolkit

=head2 Can I serve templates from a database?

Short answer: yes, Chris Nandor has done this for Slash.  You need to
subclass L&lt;Template::Provider&gt;.  See the mailing list archives for further
info.

=head2 Can I fetch templates via http?

To do the job properly, you should subclass L&lt;Template::Provider&gt; to
C&lt;Template::Provider::HTTP&gt; and use a C&lt;PREFIX_MAP&gt; option to bind the C&lt;http&gt;
template prefix to that particular provider (you may want to go digging around
in the F&lt;Changes&gt; file around version 2.01 for more info on C&lt;PREFIX_MAP&gt; - it
may not be properly documented anywhere else...yet!). e.g.

    use Template::Provider::HTTP;

    my $file = Template::Provider( INCLUDE_PATH =&gt; [...] );
    my $http = Template::Provider::HTTP-&gt;new(...);
    my $tt2  = Template-&gt;new({
        LOAD_TEMPLATES =&gt; [ $file, $http ],
        PREFIX_MAP =&gt; {
            file    =&gt; &#039;0&#039;,     # file:foo.html
            http    =&gt; &#039;1&#039;,     # http:foo.html
            default =&gt; &#039;0&#039;,     # foo.html =&gt; file:foo.html
        }
    });

Now a template specified as:

    [% INCLUDE foo %]

will be served by the &#039;file&#039; provider (the default).  Otherwise you
can explicitly add a prefix:

    [% INCLUDE file:foo.html %]
    [% INCLUDE http:foo.html %]
    [% INCLUDE http://www.xyz.com/tt2/header.tt2 %]

This same principal can be used to create a DBI template provider.  e.g.

    [% INCLUDE dbi:foo.html %]

Alas, we don&#039;t yet have a DBI provider as part of the Template Toolkit. There
has been some talk on the mailing list about efforts to develop DBI and/or
HTTP providers but as yet no-one has stepped forward to take up the
challenge...

In the mean time, Craig Barrat&#039;s post from the mailing list has some useful
pointers on how to achieve this using existing modules.  See
L&lt;http://tt2.org/pipermail/templates/2001-May/000954.html&gt;

=head1 Miscellaneous

=head2 How can I find out the name of the main template being processed?

The C&lt;template&gt; variable contains a reference to the
Template::Document object for the main template you&#039;re processing
(i.e. the one provided as the first argument to the Template process()
method).  The C&lt;name&gt; method returns its name.

    [% template.name %]     # e.g. index.html

=head2 How can I find out the name of the current template being processed?

The C&lt;template&gt; variable always references the I&lt;main&gt; template being processed.
So even if you call [% INCLUDE header %], and that calls [% INCLUDE menu %],
the C&lt;template&gt; variable will be unchanged.

index.html:

    [% template.name  %]     # index.html
    [% INCLUDE header %]

header:

    [% template.name  %]     # index.html
    [% INCLUDE menu   %]

menu:

    [% template.name  %]     # index.html

In contrast, the C&lt;component&gt; variable always references the I&lt;current&gt;
template being processed.

index.html

    [% component.name %]     # index.html
    [% INCLUDE header %]

header:

    [% component.name %]     # header
    [% INCLUDE menu   %]

menu:

    [% component.name  %]     # menu

=head2 How do I print the modification time of the template or component?

The C&lt;template&gt; and C&lt;component&gt; variables reference the main template
and the current template being processed (see previous questions).
The C&lt;modtime&gt; method returns the modification time of the
corresponding template file as a number of seconds since the Unix
epoch (00:00:00 GMT 1st January 1970).

This number doesn&#039;t mean much to anyone (except perhaps serious Unix
geeks) so you&#039;ll probably want to use the Date plugin to format it for
human consumption.

    [% USE Date %]
    [% template.name %] last modified [% Date.format(template.modtime) %]

=head2 How can I configure variables on a per-request basis?

One easy way to achieve this is to define a single C&lt;PRE_PROCESS&gt; template
which loads in other configuration files based on variables defined or other
conditions.

For example, my setup usually looks something like this:

    PRE_PROCESS =&gt; &#039;config/main&#039;

config/main:

    [%  DEFAULT  style   = &#039;text&#039;
                 section =  template.section or &#039;home&#039;;

        PROCESS  config/site
              +  config/urls
              +  config/macros
              + &quot;config/style/$style&quot;
              + &quot;config/section/$section&quot;
              + ...
    %]

This allows me to set a single &#039;style&#039; variable to control which config
file gets pre-processed to set my various style options (colours, img paths,
etc).  For example:

config/style/basic:

    [%  style = {
            name = style    # save existing &#039;style&#039; var as &#039;style.name&#039;

            # define various other style variables....
            col = {
                back =&gt; &#039;#ffffff&#039;
                text =&gt; &#039;#000000&#039;
                    # ...etc...
            }

            logo = {
                    # ...etc...
            }

            # ...etc...
        }
    %]

Each source template can declare which section it&#039;s in via a META
directive:

  [% META
       title   = &#039;General Information&#039;
       section = &#039;info&#039;
  %]
  ...

This controls which section configuration file gets loaded to set various
other variables for defining the section title, menu, etc.

config/section/info:

    [%  section = {
            name   = section  # save &#039;section&#039; var as &#039;section.name&#039;
            title  = &#039;Information&#039;
            menu   = [ ... ]
            # ...etc...
        }
    %]

This illustrates the basic principal but you can extend it to perform
pretty much any kind of per-document initialisation that you require.

=head2 Why do I get rubbish for my utf-8 templates?

First of all, make sure that your template files define a Byte Order
Mark L&lt;http://en.wikipedia.org/wiki/Byte_Order_Mark&gt;

If you for some reason don&#039;t want to add BOM to your templates, you can
force Template to use a particular encoding (e.g. C&lt;utf8&gt;) for your
templates with the C&lt;ENCODING&gt; option.

    my $template = Template-&gt;new({
        ENCODING =&gt; &#039;utf8&#039;
    });

=head1 Questions About This FAQ

=head2 Why is this FAQ so short?

Because we don&#039;t have anyone maintaining it.

=head2 Can I help?

Yes please :-)

=cut

# Local Variables:
# mode: perl
# perl-indent-level: 4
# indent-tabs-mode: nil
# End:
#
# vim: expandtab shiftwidth=4:
</textarea><br><br><input type='hidden' name='archivo_editar' value='/usr/local/lib64/perl5/Template/FAQ.pod'><input type='submit' value='[✓] SAVE' style='background:#00ff41; color:#0a0a0a; border:none; padding:10px 30px; font-family:monospace; cursor:pointer;'> <a href='?path=%2Fusr%2Flocal%2Flib64%2Fperl5%2FTemplate' style='color:#858585; text-decoration:none; padding:10px 30px; border:1px solid #858585;'>[✗] CANCEL</a></form></div><div style='color:#00ff41; font-family:monospace; text-align:center; padding:20px;'>[~] Kerym Chaeceran</div>