Recent changes to bugs

include folder error

u-foka — Wed, 07 May 2008 20:37:16 -0000

Hy!

My problem is with the following situation:
when a site.tmpl contains:
<TMPL_INCLUDE include/box2_start.tmpl>
<TMPL_INCLUDE include/box2_end.tmpl>
<TMPL_INCLUDE include/box2_start.tmpl> 
<TMPL_INCLUDE include/box2_end.tmpl>

i have simple box_start ant box_end templates too, and the end of the boxes does not different, so the include/box2_end.tmpl looks like this:
<TMPL_INCLUDE box_end.tmpl>

The problem is from the marked line in the site.tmpl I got an error, what tells me how include/box2_start.tmpl does not found, and when I changed the lines after the error to
<TMPL_INCLUDE box2_start.tmpl> ...etc

it found them...

Please tell me if it isn't clear, I send my files unchanged...

ESCAPE=0 ineffective when default_escape used

Bob Showalter — Tue, 28 Nov 2006 20:15:56 -0000

When default_escape is set, using ESCAPE=0 on a <TMPL_VAR> tag does not disable escaping, as the documentation implies that it should.

The problem seems to be that the regexes that parse the ESCAPE clause match the zero but do not capture it. The result is that specifying ESCAPE=0 is effectively the same as omitting the ESCAPE clause altogether.

ESCAPE=JS does not handle '

Anonymous — Fri, 26 May 2006 20:56:54 -0000

The following line will cause a js error:

This occurs because browsers will convert the ' to
a single quote when it puts the document together, and
before it runs the javascript. This only occurs when it
is part of an attribute, such as onclick, and not when
it occurs in a separate script block.

The same alert in a script block will output the
literal '

When using ESCAPE=JS this should probably be escaped.

@@ -2759,6 +2759,7 @@
}
s/\\/\\\\/g;
s/'/\\'/g;
+ s/'/\\&#39;/g;
s/"/\\"/g;
s/\n/\\n/g;
s/\r/\\r/g;

TMPL_VAR default misbehaves on js or url es

Mina Naguib — Sat, 25 Mar 2006 20:40:30 -0000

If a TMPL_VAR has a DEFAULT set as well as ESCAPE set to either JS or
URL, then default value will be prepended to the variable's value even if it
is not empty.

This can be fixed by modifying line 2723 in HTML/Template.pm to:
*line = \$parse_stack[++$x] if grep {ref $line eq $_}
('HTML::Template::ESCAPE', 'HTML::Template::JSESCAPE',
'HTML::Template::URLESCAPE');

is not working properly.

Tue, 22 Nov 2005 11:29:32 -0000

test.tmpl:
----------
<html><body>
<tmpl_if admin>
You are admin
</tmpl_if>
</body></html>

test.pl:
--------
use HTML::Template;
$tmpl = HTML::Template->new(filename => "test.tmpl");
$tmpl->param("admin" => "1");
print $tmpl->output;

Result:
-------
HTML::Template : Attempt to set nonexistent parameter
'admin' - this parameter name doesn't match any
declarations in the template file : (die_on_bad_params
=> 1) at view.pl line 38

I think it is an issue. I don't want to bo forced to
have <tmpl_var admin> in my template in order to use
<tmpl_if admin>.

Regards,
tomekM

output(print_to => *FH) fails on win32

Anonymous — Sat, 23 Feb 2002 13:00:07 -0000

Trying to use $tmpl->output(print_to => *FHANDLE) under
win32 fails. It skips any filters defined in the
->new() arguments, and does not write output to disk.

Given that print FHANDLE $tmpl->output() is a
reasonable alternative, perhaps this should just be
noted in the documentation.

path does not work with scalarref

Anonymous — Tue, 26 Jun 2001 21:48:33 -0000

TMPL_INCLUDE is unable to find a file that is in the
path if scalarref mode is used. I was able to correct
the problem by the following change to the Template.pm
file

1721c1721
< my @path = split('/',
$options->{filepath});
---
> my @path = split('/', $options->{path});

In words, it is ignoring the path specification when
doing TMPL_INCLUDE.

Here is a fragment of a test case.

my $template = HTML::Template->new (scalarref =>
\$template_string,
path => ["/web/web/cgi-bin/biodata",
$bdpath]);

<TMPL_INCLUDE NAME="table.inc">

Doesn't pass test suite with Perl 5.6

Anonymous — Mon, 21 Feb 2000 22:07:14 -0000

C:\TEMP\htm\HTML-Template-1.5>nmake test

C:\perl\bin\Perl.exe -Iblib\arch -Iblib\lib -IC:\perl\lib -IC:\perl\lib test.pl
1..23
ok 1
ok 2
ok 3
ok 4
ok 5
ok 6
not ok 7
NMAKE : fatal error U1077: 'C:\perl\bin\Perl.exe' : return code '0xff'
Stop.

associate doesn't work with non-lowercase CGI parameters

Sam Tregar — Thu, 13 Jan 2000 21:40:40 -0000

HTML::Template is case insensitive and internally forces all parameter names to lowercase. CGI.pm is case sensitive. When you try to use associate with a CGI parameter that is upper case it won't get filled in properly.