[pmwiki-devel] FmtTemplateVars function

Hans design5 at softflow.co.uk
Tue Feb 10 10:44:49 CST 2009

Tuesday, February 10, 2009, 4:19:58 PM, Patrick wrote:

> The intent of the extra $ is not to introduce a new class of variables,
> but instead to say "perform the substitution as soon as the template
> is read" as opposed to "when it is rendered".  Beyond that it's
> the same set of available substitutions, and intentionally includes
> page variables.

>> I suggest to use either {$PageVar} (like it is used on normal pages)
>> or perhaps {$$$PageVar}.

> No.  The whole reason {$$PageVar} exists is so that {$PageVar}
> _won't_ perform a substitution in a template, and thus someone 
> viewing/editing the template sees the page variable and not 
> its substituted value.

Does this means that we are stuck with this naming conflict?
The list of page variables is quite long and includes simple words
like Name, Title, Version, Action, Group,
all of which someone could easily use as a PTV name in normal text.

I am not suggesting to create a new class of variables, only a
different syntax for PVs and for standard template replacement


More information about the pmwiki-devel mailing list