Francesco,
Perhaps a different method would work better for you. Us a <tmpl_var> to
insert your <tmpl_var>'s.
TEMPLATE BEFORE PARSING
bla bla bla
<tmpl_var message1>
bla bla bla
<tmpl_var name="PLACE MY TEMPLATE VARS HERE">
bla bla bla
TEMPLATE AFTER PARSING
bla bla bla
parse this
bla bla bla
<tmpl_var message2>
<tmpl_loop results>
<tmpl_var site> - <tmpl_var url>
</tmpl_loop>
bla bla bla
That will help you to remove as much logic as possible from the
template. It will also offer you the flexibility of changing what
you place in the template dynamically.
Francesco Martelli - HalNet wrote:
>yes, you've misunderstood me (maybe cause my english).
>
>i add an example of what i want <tmpl_skip> tag to do:
>
>TEMPLATE BEFORE PARSING:
>
>bla bla bla
><tmpl_var message1>
>bla bla bla
><tmpl_skip>
> <tmpl_var message2>
> <tmpl_loop results>
> <tmpl_var site> - <tmpl_var url>
> </tmpl_loop>
></tmpl_skip>
>bla bla bla
>
>METHOD CALL:
>
>$tmpl->param(
> message1 =>'parse this',
> message2 =>'dont parse this', # useless
>);
>
>TEMPLATE AFTER PARSING:
>
>bla bla bla
>parse this
>bla bla bla
><tmpl_var message2>
><tmpl_loop results>
> <tmpl_var site> - <tmpl_var url>
></tmpl_loop>
>bla bla bla
>
>END
>
>Now i can use it as a template (in previous message i explain why i need
>this).
>
>bye
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
