Recent Changes - Search:



Nested page text variables

Note: The following examples in this section describe a behavior, which was not defined as a feature by design, but which is more like a side effect. Be advised not to rely on nested PTVs, as their processing may change in the future. --Petko June 19, 2010, at 07:54 PM

Oops! I hope it doesn't change too much. I make extensive use of the 2nd type of PTV nesting... —Peter Bowers February 23, 2011, at 01:39 AM

Page text variables can be nested

: MailingAddress : {$:Address}, {$:City}, {$:Country}
, ,

", , "

Another way you may nest PTVs is to make (part of) the variable name a variable in itself:

Contents of y on page {$:x}:

x:Test/Ptvb Contents of y on page Test/Ptvb: hello

Usage - other

Data relevant to a page (the "Base" page) may now also be found in other groups. If the Base page is Main/HomePage, the data page could be Data-Main/HomePage. A new variable called $BaseName, which automatically calculates the Base page name from the Data page name, and can be defined by including the following in config.php:

// The pattern for figuring out the basename of a page
$BaseNamePatterns['/^Data-/'] = '';

Your pattern may vary.

Use page text variables in conditional markup

Page text variables will be assigned/evaluated before any conditional markup is evaluated. This effectively means that you cannot declare a PTV within an if...else condition; and also that a PTV will have a value even if it is set within a (:if false:)....(:if:) condition.

Note: The following examples in this section describe a behavior, which was not defined as a feature by design, but which is more like a side effect. Be advised not to rely on conditionals when you set a PTV, as their processing may change in the future. --Petko June 19, 2010, at 07:54 PM

In the example below, the condition will output the text '1 is equal to 1'; however, the value of 'cond1' will be 23, since both PTV assignments are evaluated (before the conditional), but the cond1:23 is evaluated last, and overrides the initial cond1:19.

(:if equal 1 1:)1 is equal to 1 (:cond1:19:)
(:else:)1 is NOT equal to 1?! (:cond1:23:)

The value of 'cond1' is {$:cond1}

1 is equal to 1

The value of 'cond1' is 23

You can however embed a conditional in a PTV assignment. Notice the format of the declaration below uses the non-hidden assignment form.

cond2:(:if equal 1 1:)19(:else:)23(:if:)

The value of 'cond2' is {$:cond2}


The value of 'cond2' is 19

You cannot use the hidden form of PTV assignments, with an embedded condition. You basically get garbage output:

(:cond3:(:if equal 1 1:)19(:else:)23(:if:):)

The value of 'cond3' is {$:cond3}

The value of 'cond3' is (:if equal 1 1

But, you can take advantage of the fact that PTV assignments are made before conditions are evaluated, and hide the PTV assignment within a condition which evaluates to false, and thus is not displayed. In the example below we're using embedded conditions, and so we number the if statements:

(:if1 false:)
cond4:(:if2 equal 1 1:)19(:else2:)23(:if2:)

The value of 'cond4' is {$:cond4}

The value of 'cond4' is 19

Other information:

  • Pm's post about line breaks documents use of the directive and mentions customization of the markup.
  • Pm's post responding to a request for a summary in response to a request for documentation.
  • Pm's post announcing the release of 2.2.0 beta 2 and providing examples.
  • Pm's post planning for 2.2.0
  • Lots of older posts with references to "PData" including an some extensive threads with lots of brainstorming about markup including, specifically, the WikiPaths thread started by Martin. (wikipath recipe finally released)

Usage notes

List names can be separated with leading spaces (a la Site.Blocklist or Site.InterMap), but list values may only have one leading space.

Sea: Tasman
 Ocean:  Southern

-> @@"{$:Sea}"@@
-> @@"{$:Ocean}"@@

(:Continent: Antartica:)
-> @@"{$:Continent}"@@
 Sea: Tasman
  Ocean:  Southern
" Southern"

Lists can have leading or trailing spaces around the page variable name

Insect : Weta
:Bird  : Kiwi
: Tree: Kauri
:  Flower : Kowhai


Insect : Weta


"Weta" "Kiwi" "Kauri" "Kowhai"

What you can't do

Mismatch case in the page variable name

river: Whanganui
Range: Southern Alps

->[-(lowercase)-] "{$:river}"
->[-(uppercase)-] "{$:River}"
->[-(lowercase)-] "{$:range}"
->[-(uppercase)-] "{$:Range}"

river: Whanganui Range: Southern Alps

(lowercase) "Whanganui"
(uppercase) ""
(lowercase) ""
(uppercase) "Southern Alps"

Have embedded (you really didn't expect that did you) spaces in the page variable name

:Big bird:Moa

"@@{$:Big bird}@@" "@@{$:Bigbird}@@"
Big bird

"{$:Big bird}" ""

Note that leading and trailing spaces in the page variable text are retained

:Island:       Rakiura
:Volcano:               Ngauruhoe                                  


" Rakiura" " Ngauruhoe " "Rotorua "

Use natural page names, ie normal page name preprocessing does not occur

-<[[PmWiki.Page text variables]] "{PmWiki.Page text variables$:Summary}"
-<[[PmWiki.PageTextVariables]] "{PmWiki.PageTextVariables$:Summary}"
PmWiki.Page text variables "{PmWiki.Page text variables$:Summary}"
PmWiki.PageTextVariables "Page variables automatically made available through natural or explicit page markup"

To use with conditional markup put the conditional markup in the variable

LinkUrl: (:if TRUE:)[[Cookbook:Quotes]](:ifend:)




this won't work as page text variables are calculated prior to expressions.

(:if TRUE:)
 LinkUrl: [[Cookbook:Quotes]]



See more examples at Test.Ptv

Usage in code

Defining new patterns for PTV (examples : bulleted lists, anchors, triple angle brackets)

PageTextVar relies on the $PageTextVarPatterns variable (which can be used to extend the recognized formats for page text variables in a page). In the older 2.2.0 Beta versions of PmWiki, this variable wasn't initialized until stdmarkup.php was run, after config.php was executed. Thus, if you needed to use page text variables inside config.php, you had to initialize it yourself. This is no longer necessary, but for those who are still running earlier versions of the beta series, here's the value to use:

SDVA($PageTextVarPatterns, array(
  'var:' => '/^:*\\s*(\\w[-\\w]*)\\s*:[ \\t]?(.*)$/m',
  '(:var:...:)' => '/\\(: *(\\w[-\\w]*) *:(?!\\))\\s?(.*?):\\)/s'));

Bulleted lists. For enabling PTV definition in bulleted lists, use this line in config.php (EemeliAro in Mailing list)

$PageTextVarPatterns['* var:'] = '/^(\\**\\s*(\\w[-\\w]*)\\s*:[ \\t]?)(.*)($)/m';

Anchors. For enabling multiline PTV definition delimited with anchors, use these lines in config.php (HansB in Mailing list). « The advantage of using anchors as PTVs is that you could reference those sections as PTVs and also as anchor sections, use them in urls for instance. The markers are also invisible. »

# make it possible to treat [[#section]] .... [[#sectionend]] as a PTV of name 'section'
$PageTextVarPatterns['[[#anchor]]'] =   "/(\\[\\[#(\\w[-\\w]*)\\]\\](?: *\n)?)(.*?)(\\[\\[#\\2end\\]\\])/s";

<<< (myvar) angle brackets >>>. For enabling multiline PTV definition delimited with triple angle brackets, use these lines in config.php (HansB in Mailing list).

Markup('<<<var', '<split', '/<<<\\s*?\\((\\w[-\\w]*) *\\)(.*?)>>>/s', '$2' );
$PageTextVarPatterns['<<<var...>>>'] = '/(<<<\\s*?\\(*(\\w[-\\w]*) *\\)(?!\\))\\s?)(.*?)(>>>)/s';

Page Text Variable calls & Markup Expressions

You can use a PTV call in a markup expression, but due to order of processing, you cannot use a markup expression inside of a PTV variable name. The following will fail:

(:if exists Profile-Data.{Members/Hosts$:{(ftime "%Y%m")}} :)

Instead create a Page Variable in config.php, and use it in the PTV:

$FmtPV['$YYYYMM'] = 'strftime("%Y%m")';

Then this will work:

(:if exists Profile-Data.{Members/Hosts$:{$YYYYMM}} :)


How can I get the page text variable to be evaluated only when it is declared, rather than each time it is used? For example I want to do the following, where the link refers back to the page with the included text

(:include {$:Abstract} lines=4:)
->[[{$:Abstract} | more ...]]

Is there a way to overwrite Page text variables, for including the same Template twice? E.g.:

(:include TemplateThatUsesParameter:)
(:include TemplateThatUsesParameter:)

See Include with PTV, IncludeWithPTV2

Is it possible to use complex searches for PTV through pagelist?

For example using regexp like this: (pagelist $MyVar="<regexp match pattern>")? Maybe a cookbook recipe can be provided for this? Also is there a possibility to achieve complex pagelist searches based on PTV-match conditions? For example to search for all pages where PTV1=<xxx> | PTV2!=<yyy>, or some other boolean expression... I wonder if this is something that can be cookbooked?

Is there any possibillity to include PageTextVariables in some other MarkUp? Something like that:

(:div id={{=$Name}$:project}}_small :)
Yes. Inspect the source to see that the following works. —Eemeli Aro July 28, 2009, at 06:29 AM
(:div id='{$:project}_small':)


Can someone give me an example of using page text variables in a skin template? I read it can be done - but how?


This is a talk page for improving PmWiki.PageTextVariables.

Edit - History - Print - Recent Changes - Search
Page last modified on April 02, 2015, at 02:59 PM