Help:Extension:ParserFunctions

The extension provides ten additional parser functions to supplement the "magic words", which are already present in MediaWiki. All the parser functions provided by this extension take the form:
 *  

#if:

 *  

This function tests whether the first parameter is 'non-empty'. It evaluates to false if the test string is empty or contains only whitespace characters (space, newline, etc).


 *   &rarr; 
 *   &rarr; 
 *   &rarr; 
 *   &rarr; 

The test string is always interpreted as pure text, so mathematical expressions are not evaluated:


 *   &rarr; 

Either or both the return values may be omitted:


 *   &rarr;  
 *  </tt> &rarr;  
 *  </tt> &rarr;  

When dealing with parameters, a pipe symbol ("|") may be used to indicate which way to handle things if a parameter is or is not passed in.


 *  </tt>


 * Sample:  </tt>


 * Result: </tt>


 *  </tt>


 * Sample:  </tt>


 * Result: </tt>

The second usage is more common, and correctly handles situations where a parameter exists, but is comprised only of empty space.

#ifeq:
This parser function compares two strings and determines whether they are identical.


 *  </tt>

If both strings are valid numerical values, the strings are compared numerically:


 *  </tt> &rarr; 
 *  </tt> &rarr; 

Otherwise the comparison is made as text; this comparison is case sensitive:


 *  </tt> &rarr; 
 *  </tt> &rarr; 
 *  </tt> &rarr; 

#expr:
This function evaluates a mathematical expression and returns the calculated value.


 *  </tt>

The available operators are listed to the right, in order of precedence. See m:Help:Calculation for more details of the function of each operator. The accuracy and format of the result returned will vary depending on the operating system of the server running the wiki, and the number format of the site language.

When evaluating using boolean algebra, zero evaluates to false</tt> and any nonzero value, positive or negative, evaluates to <tt>true</tt>:


 * <tt> </tt> &rarr; 

An empty input expression returns an empty string. Invalid expressions return one of several error messages, which can be caught using the <tt>#iferror:</tt> function:


 * <tt> </tt> &rarr;  
 * <tt> </tt> &rarr; 
 * <tt> </tt> &rarr; 

#ifexpr:
This function evaluates a mathematical expression and returns one of two strings depending on the boolean value of the result:


 * <tt> </tt>

The <tt>expression</tt> input is evaluated exactly as for <tt>#expr:</tt> above, with the same operators being available. The output is then evaluated as a boolean expression. This function is equivalent to one using <tt>#ifeq:</tt> and <tt>#expr:</tt> only:


 * <tt> </tt>

An empty input expression evaluates to false:


 * <tt> </tt> &rarr; 

Either or both the return values may be omitted:


 * <tt> </tt> &rarr; 
 * <tt> </tt> &rarr;  
 * <tt> </tt> &rarr;  

#switch:
This function compares one input value against several test cases, returning an associated string if a match is found.

The <tt>default result</tt> is returned if no <tt>case</tt> string matches the <tt>comparison string</tt>. In this syntax, the default result must be the last parameter and must not contain a raw equals sign. Alternatively, the default result may be explicitly declared with a case string of "<tt>#default</tt>"; default results declared in this way may be placed anywhere within the function:


 * <tt> </tt> &rarr; 

It is possible to have 'fall through' values, where several <tt>case</tt> strings return the same <tt>result</tt> string. This minimises duplication.

Here cases 2, 3 and 4 all return <tt>result2</tt>; cases 6 and 7 both return <tt>result4</tt>

As with <tt>#ifeq:</tt>, the comparison is made numerically if both the comparison string and the case string being tested are numeric; or as case-sensitive string otherwise.

#ifexist:
This function takes an input string, interprets it as a page title, and returns one of two values depending on whether or not the page exists on the local wiki.


 * <tt> </tt>

The function evaluates to <tt>true</tt> if the page exists, whether it contains content, is visibly blank (contains meta-data such as category links or magic words, but no visible content), is blank, or is a redirect. Only pages that are redlinked evaluate to false, including if the page used to exist but has been deleted.


 * <tt> </tt> &rarr; 
 * <tt> </tt> &rarr; 

The function evaluates to true for system messages that have been customised, and for special pages that are defined by the software.


 * <tt> </tt> &rarr; 
 * <tt> </tt> &rarr;
 * <tt> </tt> &rarr;

<tt>#ifexist:</tt> is considered an "expensive parser function", only a limited number of which can be included on any one page (including functions inside transcluded templates). When this limit is exceeded, the page is categorised into Category:, and any further <tt>#ifexist:</tt> functions automatically return false, whether the target page exists or not.

If a page checks a target using <tt>#ifexist:</tt>, then that page will appear in the list for the target page. So if the code <tt> </tt> were included live on this page, /Foo will list.

On wikis using a shared media repository, <tt>#ifexist:</tt> can be used to check if a file has been uploaded to the repository, but not to the wiki itself:
 * <tt> </tt>  &rarr; 
 * <tt> </tt> &rarr; 
 * <tt> </tt> &rarr; 

If a local description page has been created for the file, the result is exists for all of the above.

#iferror:
This function takes an input string and returns one of two results; the function evaluates to <tt>true</tt> if the input string contains an HTML object with <tt>class="error"</tt>, as generated by other parser functions such as <tt>#expr:</tt>, <tt>#time:</tt> and <tt>#rel2abs:</tt>, template errors such as loops and recursions, and other 'failsoft' parser errors.


 * <tt> </tt>

One or both of the return strings can be omitted. If the <tt>correct</tt> string is omitted, the <tt>test string</tt> is returned if it is not erroneous. If the <tt>error</tt> string is also omitted, an empty string is returned on an error:


 * <tt> </tt> &rarr; 
 * <tt> </tt> &rarr; 
 * <tt> </tt> &rarr; 
 * <tt> </tt> &rarr; 
 * <tt> </tt> &rarr;  
 * <tt> </tt> &rarr;  

#time:
This parser function takes a date and/or time construct and formats it according to the syntax given. A date/time object can be specified; the default is the value of the magic word <tt> </tt> – that is, the time the page was last rendered into HTML.


 * <tt> </tt>
 * <tt> </tt>

The list of accepted formatting codes is given in the table to the right. Any character in the formatting string that is not recognised is passed through unaltered. There are also two ways to escape characters within the formatting string: In addition, the digraph <tt>xx</tt> is interpreted as a single literal "x".
 * 1) A backslash followed by a formatting character is interpreted as a single literal character
 * 2) characters enclosed in double quotes are considered literal characters, and the quotes are removed


 * <tt> </tt> &rarr; 
 * <tt> </tt> &rarr; 
 * <tt> </tt> &rarr; 
 * <tt> </tt> &rarr; 
 * <tt> </tt> &rarr; 

The <tt>date/time object</tt> can be in any format accepted by PHP's strtotime function. Both absolute (eg <tt>20 December 2000</tt>) and relative (eg <tt>+20 hours</tt>) times are accepted.

Full or partial absolute dates can be specified; the function will 'fill in' parts of the date that are not specified using the current values:


 * <tt> </tt> &rarr; '''

A four-digit number is interpreted as hours and minutes if possible, and otherwise as year: <tt> </tt> &rarr; ''' Input is treated as a time rather than a year. <tt> </tt> &rarr; ''' Since 19:60 is no valid time, 1960 is treated as a year.

The function performs a certain amount of date mathematics:


 * <tt> </tt> &rarr; '''
 * <tt> </tt> &rarr; '''
 * <tt> </tt> &rarr; '''
 * <tt> </tt> &rarr; '''

The function recognizes a large number of placenames and time zones (full list):


 * <tt> </tt> &rarr; '''
 * <tt> </tt> &rarr; '''

#rel2abs:
This function converts a relative file path into an absolute filepath.


 * <tt> </tt>
 * <tt> </tt>

Within the <tt>path</tt> input, the following syntax is valid:
 * &rarr; the current level
 * &rarr; "go up one level"
 * &rarr; "go down one level into the subdirectory /foo"

If the <tt>base path</tt> is not specified, the full page name of the page will be used instead:


 * <tt> </tt> &rarr; '''
 * <tt> </tt> &rarr; '''
 * <tt> </tt> &rarr; '''

Invalid syntax, such as <tt>/.</tt> or <tt>/./</tt>, is ignored. Since no more than two consecutive full stops are permitted, sequences such as these can be used to separate successive statements:


 * <tt> </tt> &rarr; '''
 * <tt> </tt> &rarr; '''
 * <tt> </tt> &rarr; '''
 * <tt> </tt> &rarr; '''

#titleparts:
This function separates a pagetitle into segments based on slashes, then returns some of those segments as output.


 * <tt> </tt>

If the <tt>first segment</tt> parameter is not specified, it defaults to "1". If the <tt>number of segments</tt> parameter is not speficied, it defaults to "0", which returns all the segments:


 * <tt> </tt> &rarr; 
 * <tt> </tt> &rarr; 
 * <tt> </tt> &rarr; 
 * <tt> </tt> &rarr; 

Negative values are accepted for <tt>number of segments</tt>, they translate to "add this value to the total number of segments", loosely equivalent to "count from the right":


 * <tt> </tt> &rarr; 
 * <tt> </tt> &rarr;  

General points
Parser functions can be substituted by prefixing the hash character with <tt>subst:</tt>:


 * <tt> </tt> &rarr; the code <tt>    </tt> will be inserted in the wikitext since the page  exists.

Parser functions will mangle wikitable syntax, treating all the raw pipe characters as parameter divisors. To avoid this, most wikis create the template    :! with its contents only a raw pipe character. This 'hides' the pipe from the MediaWiki parser, ensuring that it is not considered until after all the templates and variables on a page have been expanded. Alternatively, raw HTML table syntax can be used, although this is less intuitive and more error-prone.

Whitespace, including newlines, tabs, and spaces, is stripped from the beginning and end of all the parameters of these parser functions. If this is not desirable, adding any non-whitespace characters (including the HTML encoding for a whitespace character) will prevent further stripping:


 * &rarr; 
 * &rarr; 
 * &rarr; 
 * &rarr;