# Functions

This page describes some of the internal workings of PmWiki by explaining how some of the functions in pmwiki.php work. For a more brief list/overview on functions useful to for instance cookbook writers, see Cookbook:Functions.

To use this functions you have to make sure that all relevant internal variables have been initialized correctly. See Custom Markup and Custom Actions for more information on how these functions are typically called via Markup() or $HandleActions[]. ## PSFT($format, $timestamp=null,$locale=null, $tz=null) The PSFT() function (PmWiki String Format Time, added in 2.3.0) is intended to be a safe replacement for the very widely used PHP functions strftime() and gmtstrftime() which became deprecated in PHP 8.1. Unlike strftime(), PSFT() accepts 2 additional arguments $locale and $tz, which allow to set a different language or timezone. PmWiki 2.3.0 uses this function in all cases where it previously used strftime(), including the {(ftime)} Markup Expression. If your local customizations and recipes use strftime(), you should be able to safely replace all calls to strftime() with PSFT(), without changing the arguments. Any calls to gmtstrftime($fmt, $stamp) can be replaced with PSFT($fmt, $stamp, null, 'GMT'). The old functions were deprecated by the PHP developers because they behaved inconsistently on different platforms, and were dependent on installed system locales (i.e. a language would only work if the system had its locale installed). The new function uses the PHP class IntlDateFormatter and should be better. Unfortunately, it is not always enabled by hosting providers. So depending on your installation, a specific language may be available with strftime() and/or with IntlDateFormatter?. In addition, some rarely used shortcut percent-formats %c, %x, %X also behave inconsistently on different platforms, and the new formatter may show a slightly different output. You can always replace these shortcut formats with the full formats you require. For these reasons, PSFT() is currently a compromise, by default reusing strftime() for PHP 8.0 or earlier. Updating your calls from strftime() shouldn't cause any changes in your outputs. You can set in config.php the variable $EnableFTimeNew = 1; for PSFT() to try using IntlDateFormatter? before PHP 8.1. If IntlDateFormatter? is not available, it will show the month and day names in English. Check what works.

Since the strftime() function is deprecated, it is unlikely for it to add new formats. We have added the custom format %o for the "ordinal suffix" of the date, as "st" in "January 1st". If IntlDateFormatter? is not available, it will show the suffix in English.

A difference between strftime($format,$stamp) and PSFT($format,$stamp) is how they interpret a false, empty or non-numeric $stamp argument. $stamp argumentstrftime($format,$stamp)PSFT($format,$stamp)
numericthe stampthe stamp
missing or nullcurrent timecurrent time
false1970-01-01current time
"" (empty string)
other non-numeric
1970-01-01 or false (older PHP versions)
Warning: (PHP 7.4+)
current time

## pmsetcookie($name,$val="", $exp=0,$path="", $dom="",$secure=null, $httponly=null) This function is intended as a replacement for setcookie(). It will automatically set the$secure and $httponly arguments if they are not set by the caller function and if $EnableCookieSecure and $EnableCookieHTTPOnly are enabled. ## PCCF($php_code, $callback_template='default',$callback_arguments = '$m') Deprecated since PHP 7.2 The PCCF() function (PmWiki Create Callback Function) can be used to create callback functions used with preg_replace_callback. It is required for PHP 5.5, but will also work with earlier PHP versions. The first argument is the PHP code to be evaluated. The second argument (optional) is the callback template, a key from the global $CallbackFnTemplates array. There are two templates that can be used by recipe authors:

• 'default' will pass $php_code as a function code • 'return' will wrap $php_code like "return $php_code;" (since PmWiki 2.2.62) The third argument (optional) is the argument of the callback function. Note that PmWiki uses the '$m' argument to pass the matches of a regular expression search, but your function can use other argument(s).

PCCF() will create an anonymous (lambda) callback function containing the supplied code, and will cache it. On subsequent calls with the same $php_code, PCCF() will return the cached function name. See the PHP create function. PHP 7.2 deprecates create_function() and future versions will remove it. If you need to migrate older code that used PCCF(), you can usually write regular functions and pass the function name where you previously passed the result of PCCF(). For example, suppose you had a pattern like this: '/(?<=^| )([a-z])/' => PCCF("return strtoupper(\$m[1]);"),

For PHP 7.2 compatibility, you can write a callback function:

function my_callback($m) { return strtoupper($m[1]); }

then change the pattern to look like this:

'/(?<=^| )([a-z])/' => 'my_callback',

See also: the recipe PccfToPcfOverride allows existing recipes to run on PHP 7 without causing deprecated create_function() messages.

## PPRA($array_search_replace,$string)

The PPRA() function (PmWiki Preg Replace Array) can be used to perform a regular expression replacement with or without evaluation, for PHP 5.5 compatibility.

Since PmWiki 2.2.56, PmWiki uses this function to process the following arrays: $MakePageNamePatterns, $FmtP, $QualifyPatterns, $ROEPatterns, $ROSPatterns,$SaveAttrPatterns, $MakeUploadNamePatterns. Any custom settings should continue to work for PHP 5.4 and earlier, but wikis running on PHP 5.5 may need to make a few changes. The first argument contains the 'search'=>'replace' pairs, the second is the "haystack" string to be manipulated. The 'replace' parts of the array can be strings or function names. If the 'replace' part is a callable function name, it will be called with the array of matches as a first argument via preg_replace_callback(). If not a callable function, a simple preg_replace() will be performed. Previously, PmWiki used such constructs: $fmt = preg_replace(array_keys($FmtP), array_values($FmtP), $fmt); It is now possible to use simply this: $fmt = PPRA($FmtP,$fmt);

Note that since PHP 5.5, the search patterns cannot have an /e evaluation flag. When creating the $array_search_replace array, before PHP 5.5 we could use something like (eg. for $MakePageNamePatterns):

'/(?<=^| )([a-z])/e' => "strtoupper('$1')", Since PHP 5.5, we should use this (will also work in PHP 5.4 and earlier): '/(?<=^| )([a-z])/' => PCCF("return strtoupper(\$m[1]);"),

Note that the /e flag should be now omitted, instead of '$0', '$1', '$2', we should use $m[0], $m[1],$m[2], etc. in the replacement code, and there is no need to call PSS() in the replacement code, as backslashes are not automatically added.

For PHP 7.2 and newer, instead of using PCCF() to create anonymous functions, we add a real function in our add-on, and then pass the function name as the pattern replacement (see example at PCCF, which will also work on PHP 4 and 5):

'/(?<=^| )([a-z])/' => 'my_callback',

## PPRE($search_pattern,$replacement_code, $string) Deprecated since PHP 7.2 The PPRE() function (PmWiki Preg Replace Evaluate) can be used to perform a regular expression replacement with evaluation. Since PHP 5.5, the preg_replace() function has deprecated the /e evaluation flag, and displays warnings when the flag is used. The PPRE() function automatically creates a callback function with the replacement code and calls it. Before PHP 5.5, it was possible to use such calls: $fmt = preg_replace('/\\$([A-Z]\\w*Fmt)\\b/e','$GLOBALS["$1"]',$fmt);

Since PHP 5.5, it is possible to replace the previous snippet with the following (also works before PHP 5.5):

$fmt = PPRE('/\\$([A-Z]\\w*Fmt)\\b/','$GLOBALS[$m[1]]',$fmt); Note that the /e flag should be now omitted, instead of '$0', '$1', '$2', we should use $m[0],$m[1], $m[2], etc. in the replacement code, and there is no need to call PSS() in the replacement code, as backslashes are not automatically added. For PHP 7.2 and newer, calling this function will raise "deprecated" notices. You need to rewrite your code to use preg_replace_callback, by moving the code into real functions: $fmt = preg_replace_callback('/\\$([A-Z]\\w*Fmt)\\b/', 'my_global_var_callback',$fmt);
function my_global_var_callback($m) { return$GLOBALS[$m[1]]; } instead of using PCCF() to create anonymous functions, we add a real function in our add-on, and then pass the function name as the pattern replacement (see example at PCCF, which will also work on PHP 4 and 5): => '/(?<=^| )([a-z])/' => 'my_callback', ## Qualify($pagename, $text) Qualify() applies $QualifyPatterns to convert relative links and references into absolute equivalents. This function is called by usual wiki markups that include text from other pages. It will rewrite links like [[Page]] into [[Group/Page]], and page (text) variables like {$Title} into {Group.Page$Title} so that they work the same way in the source page and in the including page. See also $QualifyPatterns and RetrieveAuthSection(). ## PHSC($string_or_array, $flags=ENT_COMPAT,$encoding=null, $double_encode=true) The PHSC() function (PmWiki HTML Special Characters) is a replacement for the PHP function htmlspecialchars. The htmlspecialchars() function was modified since PHP 5.4 in two ways: it now requires a valid string for the supplied encoding, and it changes the default encoding to UTF-8. This can cause sections of the page to become blank/empty on many sites using the ISO-8859-1 encoding without having set the third argument ($encoding) when calling htmlspecialchars().

The PHSC() function calls htmlspecialchars() with an 8-bit encoding as third argument, whatever the encoding of the wiki (unless you supply an encoding). This way the string never contains invalid characters.

It should be safe for recipe developers to replace all calls to htmlspecialchars() with calls to PHSC(). Only the first argument is required when calling PHSC(), although authors may wish to call PHSC($string_or_array, ENT_QUOTES). Unlike htmlspecialchars(), the PHSC() function can process arrays recursively (only the values are converted, not the keys of the array). ## PSS($string)

The PSS() function (PmWiki Strip Slashes) removes the backslashes that are automatically inserted in front of quotation marks by the /e option of PHP's preg_replace function. PSS() is most commonly used in replacement arguments to Markup(), when the pattern specifies /e and one or more of the parenthesized subpatterns could contain a quote or backslash. ("PSS" stands for "PmWiki Strip Slashes".)

From PM: PmWiki expects PSS() to always occur inside of double-quoted strings and to contain single quoted strings internally. The reason for this is that we don't want the $1 or $2 to accidentally contain characters that would then be interpreted inside of the double-quoted string when the PSS is evaluated.
Markup('foo', 'inline', '/(something)/e', 'Foo(PSS("$1"))'); # wrong Markup('foo', 'inline', '/(something)/e', "Foo(PSS('$1'))"); # right

Note, the extra slashes are only added by preg_replace() with an /e modifier. The markup definitions with Markup_e() do NOT need to use PSS() in the replacement strings. The new-type markup definitions with Markup() and a simple function name as a replacement do NOT need to use PSS() inside the replacement function. If you migrate old markup rules to the new format, delete the PSS() calls.

### Example

This is a fictitious example where PSS() should be used. Let us assume that you wish to define a directive (:example:) such that (:example "A horse":) results in the HTML

<div>"A horse"</div>.

Here is how the markup rule can be created:

Markup('example', 'directives',
'/\$$:example\\s(.*?):\$$/e',
"Keep('<div>'.PSS('$1').'</div>')");  We need to use PSS() around the '$1' because the matched text could contain quotation marks, and the /e will add backslashes in front of them.

## stripmagic($string) This function should be used when processing the contents of $_POST or $_GET variables when they could contain quotes or backslashes. It verifies get_magic_quotes(), if true, strips the automatically inserted escapes from the string. The function can process arrays recursively (only the values are processed). ## FmtPageName($fmt, $pagename) Returns $fmt, with $variable and$[internationalisation] substitutions performed, under the assumption that the current page is pagename. See PmWiki.Variables for an (incomplete) list of available variables, PmWiki.Internationalizations for internationalisation. Security: not to be run on user-supplied data.

This is one of the major functions in PmWiki, see PmWiki.FmtPageName for lots of details.

## Markup($name,$when, $pattern,$replace)

Adds a new markup to the conversion table. Described in greater detail at PmWiki.CustomMarkup.

This function is used to insert translation rules into the PmWiki's translation engine. The arguments to Markup() are all strings, where:

$name The string names the rule that is inserted. If a rule of the same name already exists, then this rule is ignored. $when
This string is used to control when a rule is to be applied relative to other rules. A specification of "<xyz" says to apply this rule prior to the rule named "xyz", while ">xyz" says to apply this rule after the rule "xyz". See CustomMarkup for more details on the order of rules.
$pattern This string is a regular expression that is used by the translation engine to look for occurrences of this rule in the markup source. $replace
This string will replace the matched text when a match occurs, or the function name that will return the replacement text.

Also see: PmWiki.CustomMarkup and Cookbook:Functions#Markup

## MarkupToHTML($pagename,$str)

Converts the string $str containing PmWiki markup into the corresponding HTML code, assuming the current page is $pagename. MarkupToHTML?() replaces \n\n sequences by <:vspace> first thing when text is passed to it. Subsequently <:vspace> is processed by the markup rules:

'!vspace' removes <:vspace> after headings.
'<vspace><p>' replaces <:vspace><p> with <p class='vspace'>
'<vspace>' replaces <:vspace> with <div class='vspace'>
and finally
'^<:' removes any remaining <:vspace>, mostly from restored [=escaped text=].

Also see: Cookbook:Functions#MarkupToHTML

## Lock(0)

This function is used to make sure only one instance of PmWiki is running when files are being written. It does not "lock pages" for editing.

From a recipe, use:

• Lock(2); to acquire an exclusive lock, so that no other PHP processes can modify files. This can be used when your function is writing files on the server.
• Lock(1); to acquire a shared lock. This may be used when your function is reading files from the server, in case another process is writing them at the same time.
• Lock(0); to release a previous exclusive or shared lock. Use this immediately after your function finishes reading or writing the files.

If you don't release an acquired lock, it should be automatically released at the end of the processing.

## MakeLink($pagename,$target, $txt,$suffix, $fmt) The function MakeLink($pagename, $target,$txt, $suffix,$fmt) returns an html-formatted anchor link. Its arguments are as follows:

 $pagename is the source page$target is where the link should go
$txt is the value to use for '$LinkText' in the output
$suffix is any suffix string to be added to$txt

## DownloadUrl?($pagename,$path)

This function returns the public URL of an attached file. The arguments are as follow:

• $pagename - the currently processed page • $path - the file path, as in file.ext or OtherPage?/file.ext or OtherPage?/file.ext

If the file doesn't exist, the function returns false. The global variable $FmtV['$LinkUpload'] contains the URL to the upload form, for a file with such a name to be attached.

## IsAuthorized($chal,$source, &$from) IsAuthorized?() takes a pageattributesstring (e. g. "id:user1$1$Ff3w34HASH...") in $chal.
$source is simply returned and used for building the authcascade (pageattributes - groupattributes - $DefaultPassword).
$from will be returned if $chal is empty, because it is not checked before calling IsAuthorized?(), this is needed for the authcascade.

IsAuthorized?() returns an array with three values: $auth 1 - authenticated, 0 - not authenticated, -1 - refused; $passwd; $source from the parameter list. ## CondAuth ($pagename, 'auth level')

CondAuth() implements the ConditionalMarkup for (:if auth level:). For instance  CondAuth($pagename,'edit') is true if authorization level is 'edit'. Use inside local configuration files to build conditionals with a check of authorization level, similar to using (:if auth level:) on a wiki page. Note that CondAuth?() should be called after all authorization levels and passwords have been defined. For example, if you use it with Drafts, you should include the draft.php script before calling CondAuth?(): $EnableDrafts = 1;
$DefaultPasswords['publish'] = pmcrypt('secret'); include_once("$FarmD/scripts/draft.php");
if (! CondAuth($pagename, 'edit')) { /* whatever */ }  Best is to use CondAuth?() near the bottom of your config.php script. ## RetrieveAuthPage?($pagename, $level,$authprompt=true, $since=0) Pm words as said in https://www.pmwiki.org/pipermail/pmwiki-users/2005-April/012804.html where:  $pagename   - name of page to be read
$level - authorization level required (read/edit/auth/upload)$authprompt - true if user should be prompted for a password if needed
$since - how much of the page history to read 0 == read entire page including all of history READPAGE_CURRENT == read page without loading history timestamp == read history only back through timestamp  The $since parameter allows PmWiki to stop reading from a page file as soon as it has whatever information is needed -- i.e., if an operation such as browsing isn't going to need the page's history, then specifying READPAGE_CURRENT can result in a much faster loading time. (This can be especially important for things such as searching and page listings.) However, if combined with UpdatePage?(), the updated page will have no history.

Use e.g. $page = @RetrieveAuthPage('Main.MyPage', 'read') to obtain a page object that contains all the information of the correspondent file in separate keys, e.g. $page['text'] will contain a string with the current wiki markup of . Use this generally in preference to the alternative function ReadPage($pagename,$since=0) since it respects the authorisation of the user, i.e. it checks the authorisation level before loading the page, or it can be set to do so. ReadPage() reads a page regardless of permission.

Passing 'ALWAYS' as the authorization level (instead of 'read', 'edit', etc.) will cause RetrieveAuthPage?() to always read and return the page, even if it happens to be protected by a read password.

## RetrieveAuthSection?($pagename,$pagesection, $list=NULL,$auth='read')

RetrieveAuthSection?() extracts a section of text from a page. If $pagesection starts with anything other than '#', the text before the first '#' (or all of it, if there is no '#') identifies the page to extract text from. Otherwise RetrieveAuthSection?() looks in the pages given by $list (should be an array), or in $pagename if $list is not specified.

• The selected page is placed in the global $RASPageName variable. • The caller is responsible for calling Qualify() as needed, i.e. if you need to control how unqualified page and variable names shall be resolved. • To have them act as in the original text, let Qualify() resolve them relative to the source page. • If the imported text was not meant as wikitext but as some other kind of markup that might happen to contain double pairs of square brackets, or dollar signs inside curly brackets, you probably don't want to Qualify() them. If you output them into wikitext, you'll probably need to Keep() the text (in case of HTML, XML, RSS or similar output, PHSC() first!), to prevent later stages of processing from interpreting the apparent wiki markups in context of the target page. • If your code produces wikitext for an auxiliary page that is meant to be included by another page higher up in the inclusion chain, and want links and variables to work as if they were in the auxiliary page, use the auxiliary page's "" as the $pagename argument for Qualify().

Provides a way to limit the array that is returned by , so that it only pulls the content up to a specific section marker. For example, pulling from start of page to '##blogend':

function FeedText($pagename, &$page, $tag) {$text = RetrieveAuthSection($pagename, '##blogend');$content = MarkupToHTML($pagename,$text);
return "<$tag><![CDATA[$content]]></$tag>"; }  The '##blogend' argument says to read from the beginning of the page to just before the line containing the marker. See IncludeOtherPages for more information about the section specifications. This version won't read text from pages that are read-protected; if you want to get text even from read-protected pages, then $text = RetrieveAuthSection($pagename, '##blogend', NULL, 'ALWAYS');  ## UpdatePage?($pagename, $old (page object),$new (page object));

UpdatePage() allows cookbook recipes to mimic the behavior of editing wiki pages via the browser. Internally, PmWiki does several house keeping tasks which are accessible via this function (preserving history/diff information, updating page revision numbers, updating RecentChanges pages, sending email notifications, etc._

• "Page object" refers to an array pulled from RetrieveAuthPage($pagename,$level, $authprompt=true,$since=0); (preferred), or ReadPage($pagename);  (disregards page security). Note that $new['text'] should contain all page data for the new version of the page.
• If a page doesn't exist, UpdatePage?() will attempt to create it.
• Ignoring $old (e.g. UpdatePage($pagename, '', $new);) will erase all historical page data---a tabula rasa. • If you retrieved $old using RetrieveAuthPage?($pagename,$auth,$prompt,READPAGE_CURRENT) and set $new=\$old, then UpdatePage?() will also erase all historical data

UpdatePage?() cannot be called directly from config.php because there are necessary initializations which occur later in pmwiki.php. It is not enough to just load stdconfig.php. If you want to use UpdatePage?() you will need to do it within a custom markup, a custom markup expression, or a custom action.

## DisableSkinParts?('parts to disable');

This function allows easy disabling of the skin sections header, footer, title, actions, and sidebars, like the corresponding directives (:notitle:) (:noleft:) etc. In your function, use something like:

  DisableSkinParts('Left Header Footer Action Title');


Categories: PmWiki Developer