Air Data Probes and Sensors for Small- and Mid-Sized Aircraft
Print  |  PDF
Search:  

Air Data Products

3D Displacement Sensors

Special Offers

Contact Us

Air Data Newsletter

Support

Business Information

PmWiki is a wiki-based system for collaborative creation and maintenance of websites.

PmWiki pages look and act like normal web pages, except they have an "Edit" link that makes it easy to modify existing pages and add new pages into the website, using basic editing rules. You do not need to know or use any HTML or CSS. Page editing can be left open to the public or restricted to small groups of authors.

Key PmWiki Features

Custom look-and-feel: A site administrator can quickly change the appearance and functions of a PmWiki site by using different skins and HTML templates. If you can't find an appropriate skin already made, you can easily modify one or create your own.
Access control: PmWiki password protection can be applied to an entire site, to groups of pages, or to individual pages. Password protection controls who can read pages, edit pages, and upload attachments. PmWiki's access control system is completely self-contained, but it can also work in conjunction with existing password databases, such as .htaccess, LDAP servers, and MySQL databases.
Customization and plugin architecture: One principle of the PmWikiPhilosophy is to only include essential features in the core engine, but make it easy for administrators to customize and add new markup. Hundreds of features are already available by using extensions (called "recipes") that are available from the PmWiki Cookbook.

PmWiki is written in PHP and distributed under the General Public License. It is designed to be simple to install, customize, and maintain for a variety of applications. This site is running pmwiki-2.2.11.

PmWiki is a registered trademark of Patrick R. Michaud.

PmWiki's home on the web is at pmwiki.org.

This page describes the "variables" that are associated with pages. Page variables have the form {$variable}, and can be used in page markup or in certain formatting strings in PmWiki. For example, the markup "{$Group}" renders in this page as "PmWiki".

Note: Do not confuse these variables (set and used only in PmWiki pages) with PHP variables. Page variables can be read in PHP with the PageVar() function.

Note that these variables do not necessarily exist in the PHP code, because they have to be determined for a specific page. (However, they are usable in FmtPageName strings.)

There is also the form {pagename$variable}, which returns the value of the variable for another page. For example, "{MarkupMasterIndex$Title}" displays as "Markup Master Index".

Special references

Special referenced variables are used to retain the context of the target page or main page for a variable when:

  • the variable is included into a destination (target) page)
  • the variable is part of a sidebar, header, or footer for a main page

Prefixing the variable name with an asterisk (*) means the variable reflects the value related to the target page or main page.

  • *$PageVariablename - prefixed by an asterisk (*) - value reflects target page context

Without the asterisk it reflects the value of the page in which it originates.

  • $PageVariablename - retains value in source page context

See also $EnableRelativePageVars.

Special references are also used in page list templates.

For example you can test to see if the page is part of another page

(:if ! name {$FullName}:) 
%comment% name of this page is not the same as the page this text was
sourced from
->[[{$FullName}#anchor | more ...]]
(:ifend:)

or refer to the main page in a sidebar, footer, or header

This page is [[{*$FullName}]]

This page is PmWiki.PageVariables

Default page variables

The page variables defined for PmWiki are:

{$Action} - page's url action argument, as in "browse"
{$BaseName} - page's "base" form (stripping any prefixes or suffixes defined via $BaseNamePatterns) as in "PmWiki.PageVariables"
{$DefaultGroup} - default group name, as in "Main"
{$DefaultName} - name of default page, as in "`Home"
{$Description} - page's description from the (:description:) markup, as in "Documentation for "variables" that are associated with pages."
{$FullName} - page's full name, as in "PmWiki.PageVariables"
{$Group} - page's group name, as in "PmWiki"
{$Groupspaced} - spaced group name, as in "Pm Wiki"
{$LastModified} - date page was edited, as in "2010-02-11 09:47"
{$LastModifiedBy} - page's last editor, as in "Petko"
{$LastModifiedHost} - IP of page's last editor, as in "86.69.109.228"
{$LastModifiedSummary} - Summary from last edit, as in "See also $EnableRelativePageVars"
{$LastModifiedTime} - time page was edited in unix-style timestamp, as in "1265899656" added version 2.2 beta 67
This can be used (preceded by '@') in {(ftime)} and other date/time markups.
{$Name} - page name, as in "PageVariables"
{$Namespaced} - spaced page name, as in "Page Variables"
{$PasswdRead} - "read" permissions for the page e.g. "(protected)"
{$PasswdEdit} - "edit" permissions for the page e.g. "(protected)"
{$PasswdAttr} - "attr" permissions for the page e.g. "(protected)"
{$RequestedPage} - page requested in URL, used on Site.PageNotFound. e.g. "PmWiki/PageVariables"
{$SiteGroup} - default group name for e.g. RecentChanges, as in "Site"
{$Title} - page title (may differ from Name), as in "Page specific variables"
{$Titlespaced} - either the page title (if defined), or the spaced page name, as in "Page specific variables"

In addition to the above, there are some page-invariant variables available through this markup:

{$Author} - the name of the person currently interacting with the site, as in ""
{$AuthId} - current authenticated id, as in "" Please note the lower case 'd'. {$AuthID} returns nothing
{$Version} - PmWiki version, as in "pmwiki-2.2.11"
{$VersionNum} - The internal version number, as in "2002011"
{$ScriptUrl} - The url to the pmwiki script, as in "https://spaceagecontrol.com/Main"

Custom page variables

You may add custom page variables as a local customization. In a local configuration file or a recipe script, use the variable $FmtPV:

$FmtPV['$VarName'] = "'variable definition'";
$FmtPV['$CurrentSkin'] = '$GLOBALS["Skin"]';
$FmtPV['$WikiTitle'] = '$GLOBALS["WikiTitle"]';

Defines new Page Variable of name $CurrentSkin, which can be used in the page with {$CurrentSkin} (also for Conditional markup). It's necessary to use the single quotes nested inside double-quotes as shown above (preferred) or a double-quoted string nested inside single-quotes like '"this"'.

If you want to have a Page Variable that returns the currently used password (more precisely, the last password entered), you can use

$FmtPV['$AuthPw'] = 'reset(array_keys((array)@$_SESSION["authpw"]))';

See also

Is there a variable like $LastModified, but which shows me the creation time?

No, but you can create one in config.php. For instance:

# add page variable {$PageCreationDate} in format yyyy-mm-dd
$FmtPV['$PageCreationDate'] = 'strftime("%Y-%m-%d", $page["ctime"])';

If you like the same format that you define in config.php with $TimeFmt use

 $FmtPV['$Created'] = "strftime(\$GLOBALS['TimeFmt'], \$page['ctime'])";

PmWiki is a wiki-based system for collaborative creation and maintenance of websites.

PmWiki pages look and act like normal web pages, except they have an "Edit" link that makes it easy to modify existing pages and add new pages into the website, using basic editing rules. You do not need to know or use any HTML or CSS. Page editing can be left open to the public or restricted to small groups of authors.

Key PmWiki Features

Custom look-and-feel: A site administrator can quickly change the appearance and functions of a PmWiki site by using different skins and HTML templates. If you can't find an appropriate skin already made, you can easily modify one or create your own.
Access control: PmWiki password protection can be applied to an entire site, to groups of pages, or to individual pages. Password protection controls who can read pages, edit pages, and upload attachments. PmWiki's access control system is completely self-contained, but it can also work in conjunction with existing password databases, such as .htaccess, LDAP servers, and MySQL databases.
Customization and plugin architecture: One principle of the PmWikiPhilosophy is to only include essential features in the core engine, but make it easy for administrators to customize and add new markup. Hundreds of features are already available by using extensions (called "recipes") that are available from the PmWiki Cookbook.

PmWiki is written in PHP and distributed under the General Public License. It is designed to be simple to install, customize, and maintain for a variety of applications. This site is running pmwiki-2.2.11.

PmWiki is a registered trademark of Patrick R. Michaud.

PmWiki's home on the web is at pmwiki.org.

Page last modified on 2010-02-11 09:47
Print
SpaceAge Control, Inc.
An ISO9001:2000/AS9100B-Compliant Company
38850 20th Street East • Palmdale, CA 93550 USA
661-273-3000 • Fax: 661-273-4240 • email@spaceagecontrol.com
Business hours: Mon-Thu, 06:30 to 17:00 (Pacific time)
PrivacyConditions of UseComments and Questions
All specifications subject to change without notice.
© 1996-2025 SpaceAge Control, Inc. All rights reserved.
After Hours Help: 661-273-3000 Ext. 100 (for hours outside of Mon-Thu, 06:30 to 17:00 (Pacific time))

top Newsletter   •   News   •   Representatives   •   Request Literature   •   CAD Models   •   Calculators   •   Print   •   PDF top