From OpenWetWare
Jump to: navigation, search


A collection of parser functions such as branching instructions and expression handler and time calculation unit.


Other languages: Template:ParserFunctions
The Template:Wpd extension ParserFunctions is a collection of parser functions (note the difference between the name of the collection, and the general term). These parser functions have a hash character in front of the function name, so they typically have the syntax:



Tip: With Special:ExpandTemplates one can evaluate expressions with parser functions directly.

This module defines eight functions at present: expr, if, ifeq, ifexist, ifexpr, switch, time, and rel2abs.


The accuracy and format of numeric results varies with the operating system of the server.

The expr function computes mathematical expressions based on permutations of numbers (or variables/parameters that translate to numbers) and operators. It does not work with strings; use ifeq below instead. The syntax is:


A list of supported operators follows. For more details about the operator precedence see Help:Calculation, it's roughly (1) grouping (parentheses), (2) unary (+/- signs and NOT), (3) multiplicative (*, /, div, mod), (4) additive (+ and -), (5) round, (6) comparative (=, !=, <, >, etc.), (7) logical AND, (8) logical OR. Within the same precedence class operators are evaluated left to right. As always some redundant parentheses are better than erroneous terse code.

Operator Operation Example

Template:Ft = 1.2345678901234E+14

Template:Ft = 1.0E-6

( ) Grouping operators

Template:Ft = 259

+ Unary + sign

Template:Ft = 210

- Unary - sign (negation)

Template:Ft = 210

not Unary NOT, logical NOT

Template:Ft = 7
Template:Ft = 7

* Multiplication

Template:Ft = 210

/ Division, same as div

Template:Ft = 4.2857142857143

div Division, same as /, not integer division

Template:Ft = 4.2857142857143
Template:Ft = 6

mod "Modulo", remainder of division after truncating both operands to an integer.
Caveat, div and mod are different from all programming languages.

Template:Ft = 2
Template:Ft = -2
Template:Ft = -2
Template:Ft = 0
Template:Ft = 2
Template:Ft = 2

+ Addition

Template:Ft = 37

- Subtraction

Template:Ft = 23

round Rounds off the number on the left to the power of 1/10 given on the right

Template:Ft = 4.2857
Template:Ft = 4.3
Template:Ft = 1900
Template:Ft = -3

= Equality (numerical incl. logical)

Template:Ft = 0

<> Inequality, same as !=

Template:Ft = 1

 != Inequality, same as <>, logical xor

Template:Ft = 1

< Less than

Template:Ft = 0

> Greater than

Template:Ft = 1

<= Less than or equal to

Template:Ft = 0

>= Greater than or equal to

Template:Ft = 1

and Logical AND

Template:Ft = 0

or Logical OR

Template:Ft = 1

The boolean operators consider 0 to be "false" and any other number to be "true", on output "true" is shown as 1.

Numbers are given in decimal with "." for the decimal point. The formatnum: function can be used to change the decimal point to a comma for the appropriate locales. Scientific notation with E plus exponent is not yet supported on input for expressions, but used on output, for details see Help:Calculation.


The Template:Ft function is an if-then-else construct. The syntax is:


The applied condition is "The condition string is non-empty". Thus, if the condition string is empty or consists only of whitespace, then the condition is false, and the else text is returned. Otherwise, the then text is returned. The else text may be omitted, in which case the result will be blank if the condition is false.

An example:


Note that the condition string is not itself a condition such as "1 = 2"; for example, Template:Ft will return "yes", because the string "1 = 2" is not blank. Thus the Template:Ft function does not support "=" signs or mathematical expressions.


Template:Ft compares two strings or numbers, and returns another string depending on the result of that comparison. The syntax is:


If both strings can be interpreted as numbers the comparison is numerical. To force a string comparison add tokens that can't be interpreted as numbers:

Template:Ft gives 1
Template:Ft gives 0

Comparison of strings is case-sensitive:

Template:Ft gives 0
For compatibility with older templates #if: cannot directly distinguish defined and undefined parameter values, it's a shorthand for a comparison with the empty string. With #ifeq: it's directly possible to identify undefined parameters:
Template:Ft = blank,
Template:Ft = blank,
Template:Ft = undefined.
An undefined parameter without default counts in the comparison as a string consisting of the tag:
Template:Ft = 0.

Text between nowiki tags is during parsing temporarily replaced by a unique code. This affects comparisons:

{{#ifeq:<nowiki>abc</nowiki>|<nowiki>abc</nowiki>|y|n}} gives n.


Template:Ft returns one of two results based on whether or not a particular page exists.


The usual case-sensitivity applies: if a page exists then also a non-canonical name for that page gives a positive result. E.g. on Meta:

Template:Ft gives RFC 3092, because Bugs exists
Template:Ft gives RFC 3092, because bugs is in canonical form the existing Bugs
Template:Ft gives RFC 3092 because BUGS does not exist
Template:Ft gives Oops although m:Help:Calculation exists, because of the interwiki prefix.

The first parameter is the title to check for, the second is the positive result, and the third, the negative result. If the parameter passed does not produce a valid title object, then the result is negative.

Template:Tim gives the same result, except that the result is positive for an interwiki link. You can also handle an interwiki link differently with Template:Tim.

Template:Ft doesn't handle relative paths (like '../foo'), for that, use it in combination of Template:Ft.

The page where {{#ifexist:foo}} appears is listed on Special:Whatlinkshere/foo (as a page which links to foo), see below.


Template:Ft evaluates a mathematical expression (see #expr) and returns one of two strings depending on the result.


If the expression evaluates to zero, then the else text is returned, otherwise the then text is returned. Expression syntax is the same as for expr.


Template:Ft yes -- Because 10 is greater than 9.
At the moment the else text is also returned for an empty expression:
Template:Ft gives or else
Omitting both then text and else text gives no output except possibly an error message; this can be used to check the correctness of an expression, or to check the wording of the error message (emulated assertions, forced errors):
Template:Ft Division by zero. -- no result, hence "1/{{#ifeq: {{ns:4}}|Meta|1|0}}" is a correct expression
Template:Ft Division by zero.
Template:Ft correct -- "1=2" is a correct Boolean expression (not to be confused with one with the value 1, representing "true")
Template:Ft correct -- "1E2" not allowed in expressions
Template:Ft wrong -- "1/0" not allowed
Template:Ft wrong ("a=b" not allowed, to compare strings use #ifeq)

Example of an application: {{ #if: {{#ifexpr: {{PAGENAME}} }} || action if PAGENAME is a number (or correct numeric expression) }}

For another application, see also Template:Tim.


switch compares a single value against multiple others, returning a string if a match is found. The syntax is basically:

Template:Ft begin <comparison value>
 | <value1> = <result1>
 | <value2> = <result2>
 | ...
 | <valuen> = <resultn>
 | <default result>
Template:Ft end

switch will search through each value passed until a match is found with the comparison value. When found, the result for that value is returned (the text string after the equal sign). If no match is found, but the last item has no equal sign in it, it will be returned as the default result. If your default result must have an equal sign, you may use #default:

Template:Ft begin <comparison value>
 | <value> = <result>
 | #default = <default result>
Template:Ft end

Note that it's also possible to have "fall through" for values (reducing the need to duplicate results). For example:

Template:Ft begin <comparison value>
| <value1>
| <value2>
| <value3> = <result1, 2, 3>
| ...
| <valuen> = <resultn>
| <default result>
Template:Ft end

Note how value1 and value2 contain no equal sign. If they're matched, they are given the result for value3 (that is, whatever is in result3).

As for #ifeq: the comparison is numerical where possible:
Template:Ft gives Yes
Template:Ft gives No
The matched value can be empty, therefore the following constructs are equivalent:
Template:Ft gives empty
Template:Ft gives empty

Comparison of strings is case-sensitive:

Template:Ft gives UPPER
Template:Ft gives UPPER
Template:Ft gives lower

This is not to be confused with the fact that parser function names are case-insensitive:

Template:Ft gives UPPER

To have the #switch statement be case-insensitive, use the construct {{lc:}} or {{uc:}}

Template:Ft gives lower
Template:Ft gives lower
Template:Ft gives lower

This is usually used in templates, when you want to have case-insensitivity on in param values:

Template:Ft begin Template:Ft sub
| a
| b
| c = '''''abc''' or '''ABC'''''
| A
| B
| C = ''Memory corruption due to cosmic rays''
| #default = N/A
Template:Ft end

gives abc or ABC

#switch may be used instead of #ifeq:

Template:Ft gives true
Template:Ft gives true

Note that with respect to the Template:Peis the function #switch is basically "wasteful" (only a small part of the transcluded content is "used"), especially if it contains a long list of alternatives. A different method without this problem is using Template:Mlww.


Template:Ft is a time and date formatting function (for dates from 1 Jan 1970 only!). The syntax is:


If the time is not specified, the time at which the article is converted to HTML is used. Note that due to caching, this may be up to a week different to the time at which the article is viewed. Manual updates may be required, this can be achieved by saving the page without making any changes (a "null edit") or viewed with action=purge in search string of URL or viewed by a user whose option is "Disable page caching".

The format parameter is a format string similar to the one used by PHP's date.

The following format codes have the same meaning as in PHP. Significant differences from PHP's behaviour, apart from internationalisation (i.e. language and locale differences), should be considered an error of ParserFunctions and should be reported. All numeric format codes return numbers formatted according to the local language, use the xn code described below to override this.

Code Description Example output Current output
Y The 4-digit year. e.g. 2006 2017
y The 2-digit year. 00 to 99, e.g. 06 for year 2006. 17
n The month number, not zero-padded. 1 to 12 10
m The month number, zero-padded. 01 to 12 10
M An abbreviation of the month name. Often internationalised. Jan to Dec Oct
F The full month name. Often internationalised. January October
W ISO 8601 week number (ISO years have full weeks from monday to sunday, and ISO week number 1 always contains January 4 or the first thursday of the civil year), zero-padded. 01 to 52 or 53 (depends on year) 42
j The day of the month, not zero-padded. 1 to 31 19
d The day of the month, zero-padded. 01 to 31 19
z The day of the year (starting from 0) 0 to 364, or 365 on a leap year 291
D An abbreviation for the day of the week. Rarely internationalised. Mon to Sun Thu
l The full weekday name. Rarely internationalised. Monday to Sunday Thursday
N ISO 8601 day of the week (according to the ISO 8601 week). 1 (for Monday) through 7 (for Sunday) 4
w number of the day of the week (according to the American week). 0 (for Sunday) through 6 (for Saturday) 4
a am (between 01:00:00 and 12:59:59 on the same day) or pm, with lowercase (used with the 12-hour format). am or pm am
A Same as with code a above, but with uppercase. AM or PM AM
g 12-hour format of the hour without leading zeros (one or two digits, used with am/pm or AM/PM). 1 to 12 6
h 12-hour format of the hour, with leading padding zero (two digits, used with am/pm or AM/PM). 01 to 12 06
G 24-hour format of the hour, without leading padding zero (one or two digits). 0 to 23 6
H 24-hour format of the hour, with leading padding zero (two digits). 00 to 23 06
Minutes and seconds:
i The minute, with leading padding zero (two digits). 00 to 59 35
s The second, with leading padding zero (two digits). 00 to 59 21
U Seconds since January 1 1970 00:00:00 GMT. 0 to infinite 1508394921
L Whether it's a leap year. 1 if it is a leap year, 0 otherwise. 0
t Number of days in the month. 28 to 31 31
c ISO 8601 formatted date, same as {{#time:Y-m-dTH:i:s{{#time:+H:i|+0 hours}}}}. fixed length string 2017-10-19T06:35:21+00:00
r RFC 2822 formatted date, same as {{#time:D, j M Y H:i:s {{#time:+H:i|+0 hours}}}}. variable length string Thu, 19 Oct 2017 06:35:21 +0000

The following format codes are extensions to the PHP syntax:

Code Description
xn Format the next numeric code as a raw ASCII number. For example, in the Hindi language, Template:Ft produces ०६, 06.
xN Toggle a permanent raw number formatting flag. Like xn, except it lasts until the end of the string or until the same code appears again.
xr Format the next numeric code as a roman numeral. Only works for numbers up to 3000.
xg Output the genitive form of the month name, for languages which make such a distinction between genitive and nominative.
xx A literal "x"
xij The day of the month in Iranian calendar.
xiF The full month name in Iranian calendar
xin The month number in Iranian calendar
xiY The full year in Iranian calendar
xjj The day of the month in Hebrew calendar
xjF The full month name in Hebrew calendar
xjx Genitive form of the month name in Hebrew calendar
xjn The month number in Hebrew calendar
xjY The full year in Hebrew calendar

Any unrecognised character will be passed through to the output unmodified. There are also two quoting conventions which can be used to output literal characters.

  • Characters enclosed in double quotes will be considered literal (with the quotes themselves removed). Unmatched quotes will be considered literal quotes. Example:
  • Backslash escaping as in PHP's date() is supported. \H produces a literal H, \" produces a literal ".

More format codes may be added in the future, as demanded by the users of this extension. This may come in the form of either a more complete implementation of PHP's format codes, or additional "x" codes.

The format of the time parameter is identical to the one used by PHP's function strtotime(). It supports both absolute and relative dates, such as "December 11" and/or "+10 hours", which can be used for timezone translation. See also the GNU tar manual for more information.


In combination with user-specified date formatting:

Both give the user-specified format; the two are different if no preference has been specified.


The range of proper functioning is 01 January 1970 00:00:01 through 19 January 2038 03:14:07, or 1 through seconds after the start of 1970 (the Year 2038 problem). For arbitrary dates that may exceed this range, use date computing templates such as Template:Tim instead.

Dates before 1901 give an error message, dates between 1901 and 1970 even give (perhaps depending on the server) a wrong result (!):

Incomplete dates

  • Template:Evd (not a year but a time: today, 20:07)
  • Template:Evd (19:97 is not a valid time, therefore interpreted as year, giving the current date and time in that year)
  • Template:Evd (19:67 is not a valid time, therefore interpreted as year; this gives a date that is out of range which is changed to the start of the valid range)
  • Template:Evd (start of the month)
  • Template:Evd (specified date of the current year)

February 29

Caution should be taken with February 29, as {{#time:j|February 29}} will vary with the year. For example


Give UTC for a specified time, expressed in time zone UTC-3:

Give the UTC 3 hours ago:

Give the UTC 3 hours before a specified time expressed as UTC:

Give the UTC 3 hours before a specified time expressed in time zone UTC-3:

Thus "-0300" and "-3" add 3 hours, while "-3 hours" subtracts them.


Template:Ft converts a relative path to an absolute path.


A relative path is a path starting with '/', './', '../'. or is containing '/../' or '/.' or is simply the strings '..' or '.'. if a base path is given, is should be defined in an absolute syntax.


  • If standing in Help:Foo/bar and is calling Template:Ft, the result will be Help:Foo/baz
  • If standing in Help:Foo and is calling Template:Ft, the result will be baz
  • If standing in Help:Foo and is calling Template:Ft, the result will be Error: Invalid depth in path: "Help:Foo/../../baz" (tried to access a node above the root node).
  • If calling Template:Ft, the result will be Help:Bar/baz
  • If calling Template:Ft, the result will be Help:Foo/baz

There is no checks if the path do exist, for that you might use Template:Ft in combination:

Template:Ft gives '..' exist
Template:Ft gives '.' exist


{{#titleparts:pagename|nr_of_segments}} returns nr_of_segments slash-separated segments of pagename, starting from the beginning:

{{#titleparts:pagename|nr_of_segments|nr_of_starting_segment}} returns nr_of_segments slash-separated segments of pagename, starting from the specified starting segment:

This gives two parts of the title, starting at the second part. Likewise:

See also r22711 and bug 6067.


Like other parser functions the parser functions in this extension are affected by 5678 in a predictable way. Summary: undefined parameters can be overwritten by corresponding parameters, for details see 5678 and Substitution. Substitution is the only case where this is critical with respect to parameter defaults. It doesn't affect defined parameters.


Applying "subst:" to a parser function works, provided that there is no space between "subst:" and "#". For details see Help:Substitution. Note that unless a technique like optional substitution is used, substituting a template which uses a parser function does not replace that parser function with its result. This is often undesirable.

See also the previous section.


Currently wiki pipe table syntax doesn't work inside conditionals, but there are some workarounds.

  • Hide the pipe from parser functions by putting it in a template, e.g. Template:Tim.
  • Use html style table syntax instead of wiki style table syntax. NB: $wgUserHtml must be true (this has since been removed, and thus should not need to be set to 'true' - check if it is relevant for your version); it also may be essential to set $wgUseTidy=true;
  • See also Help:Table, completely empty rows or columns are not displayed. Empty cells could be also transformed into dummy &nbsp; cells on pages not affected by 5569.

Note that "|" and "=" were always tricky within templates, this is no new issue.

If all else fails, try setting $wgUseTidy=true; in your LocalSettings.php.


  • div is not integer division and is redundant, use / (slash) for real divisions.
  • mod uses PHP's % operator, which is different from modulo-operators in all other programming languages, see also Template:Tim and 6068.
  • mod sometimes returns wrong results for the same input values, see 6356 and /MOD10000. Update: values less than 1E+12 are apparently not affected.
  • Valid #expr: results like 1.0E-7 are not yet supported as #expr: input:
    {{#expr:1.0E-7}} yields 1.0E-7.
  • Under certain conditions round 0 results in -0 instead of 0. For an expression x using 0+(x) fixes this oddity.

Conditional whitespace

Because conditionals trim the leading and trailing whitespaces around pipe characters (like named, but unlike unnamed template parameters), inserting a conditional whitespace character is not always simple. If you only want to insert spaces, you can use the HTML entity &#32;, which inserts " ".

if you want to insert new lines or other whitespace, you can insert non-printing characters between the pipe and the whitespace:

first paragraph. {{#if:{{{paragraph}}}|<nowiki /> 

second paragraph.}}

first paragraph.

second paragraph.

See also Help:Newlines and spaces.

Code execution

In the case of conditional parser functions (if, ifeq, ifexist, ifexpr, switch), the wikitext for each case (then-part, else-part, etc.) is internally "executed"/"processed"/"evaluated" regardless of whether the condition is satisfied, although the resulting output depends on the condition. This concerns:

One may want to reduce processing to the actually applicable wikitext, to reduce the pre-expand include size, to avoid inapplicable items in the lists of links and inclusions and in the list of wanted pages, and to avoid unnecessary cascading of protection. This can be done by using #ifexpr etc. to select a template or link target, and put the whole parser function call inside the braces or brackets, e.g. {{ {{#ifexpr:..|a|b}} | parameters }} instead of {{ #ifexpr:.. | {{a|parameters}} | {{b |parameters}} }}. If there is no else-part a dummy template such as Template:Tim can be used:{{ {{#ifexpr:..|a|x0}} | parameters }} instead of {{ #ifexpr:.. | {{a|parameters}} }}. If the parameters of a and b are not the same the parser function can be split up into one for the then-part, and one with inverse condition with the else-part becoming then-part (or the same condition and only an else-part): {{ {{#ifexpr:..|a|x0}} | parameters of a }}{{ {{#ifexpr:..|x0|b}} | parameters of b }} instead of {{ #ifexpr:.. | {{a|parameters of a}} | {{b |parameters of b}} }}.

Similarly, in the case of links we can use [[ {{#ifexpr:..|a|b}} ]] instead of {{ #ifexpr:.. | [[a]] | [[b]] }}. If there is no else-part we can use {{#ifexpr:..|[[ {{#ifexpr:..|a}} ]] }} instead of {{ #ifexpr:.. | [[a]] }}. In this case we need to duplicate the condition: due to the inner copy of the condition either "[[a]]" or "[[]]" is produced; the former puts the link in the pagelinks table, the second does not give any entry in the pagelinks table; the outer copy of the condition avoids that "[[]]" is rendered if the condition is false.

In the case of nested conditional parser functions we have to copy for each link the whole nesting of conditional parser functions inside the link brackets. Similarly we can do that inside template braces. If "{{}}" is produced this does not give any entry in the templatelinks table, and it is not rendered due to the conditional parser functions around it.

See also Template:Ml.


Download all 3 of these files and put them in a new directory called ParserFunctions in your extensions directory.

If you don't have php5 use these files instead (older revision):

Then put the following at the end of your LocalSettings.php:

require_once( "$IP/extensions/ParserFunctions/ParserFunctions.php" );

If you get errors such as "Warning: require_once(/extensions/ParserFunctions/ParserFunctions.php) [function.require-once]: failed to open stream:", you should substitute the line for:

require_once( 'extensions/ParserFunctions/ParserFunctions.php' );

You can also browse the code tree here:


The Current version of ParserFunctions requires php5 to function.

INSTALLATION WARNING: MediaWiki: 1.9.1, PHP: 5.1.2-Debian-0.1~sarge1 (apache2handler) function ctype_alpha not available, had to add the following to Expr.php

if ( !function_exists('ctype_alpha') ) {
   function ctype_alpha($string) {
       //if ( !preg_match('|[^\pL]|', $string) )
       /* Warning: preg_match() [function.preg-match]: Compilation failed: PCRE does not support 
       \L, \l, \N, \P, \p, \U, \u, or \X at offset 3 in 
       /.../extensions/ParserFunctions/Expr.php on line 6
       /* alternative: */ // 
       if ( !preg_match('|[^A-Za-z]|', $string) )
           return true;
           return false;

If you are using Gentoo Linux's portage system to install php, be sure to have the "ctype" USE flag set for dev-lang/php to avoid the above error.

1.8 and up

All the ParserFunctions work under 1.8 and up, also in the localised forms.


All the ParserFunctions work under 1.7, but only in English. However, the extension may cause problems when used together with the Cite extension; cf. [1]. For the #time parser functions to work, you must also download SprintfDateCompat.php to the extensions/ParserFunctions directory.


When including the ParserFunctions in 1.6, some notices may be shown. Removing the following line (line 10) in ParserFunctions.php fixes the problem:

$wgHooks['LanguageGetMagic'][]       = 'wfParserFunctionsLanguageGetMagic';

For the #time parser functions to work, you must also download SprintfDateCompat.php to the extensions/ParserFunctions directory. But actually that won't fix the problem.

Most ParserFunctions (except #if, which does not work at all) work just as well on MediaWiki 1.6, but the syntax of ParserFunctions is without the '#' character. If you want to use the '#' character, find this section of ParserFunctions.php:

 $wgParser->setFunctionHook( 'expr', array( &$wgExtParserFunctions, 'expr' ) );
 $wgParser->setFunctionHook( 'if', array( &$wgExtParserFunctions, 'ifHook' ) );
 $wgParser->setFunctionHook( 'ifeq', array( &$wgExtParserFunctions, 'ifeq' ) );
 $wgParser->setFunctionHook( 'ifexpr', array( &$wgExtParserFunctions, 'ifexpr' ) );
 $wgParser->setFunctionHook( 'switch', array( &$wgExtParserFunctions, 'switchHook' ) );
 $wgParser->setFunctionHook( 'ifexist', array( &$wgExtParserFunctions, 'ifexist' ) );

Then, replace it with this:

 $wgParser->setFunctionHook( '#expr', array( &$wgExtParserFunctions, 'expr' ) );
 $wgParser->setFunctionHook( '#if', array( &$wgExtParserFunctions, 'ifHook' ) );
 $wgParser->setFunctionHook( '#ifeq', array( &$wgExtParserFunctions, 'ifeq' ) );
 $wgParser->setFunctionHook( '#ifexpr', array( &$wgExtParserFunctions, 'ifexpr' ) );
 $wgParser->setFunctionHook( '#switch', array( &$wgExtParserFunctions, 'switchHook' ) );
 $wgParser->setFunctionHook( '#ifexist', array( &$wgExtParserFunctions, 'ifexist' ) );

In some cases it just helps to add the default language to the header function on line 169

function wfParserFunctionsLanguageGetMagic( &$magicWords, $langCode='en' ) {

A simple fix for #if in this version -


 function ifHook( &$parser, $test = '', $then = '', $else = '' ) {
  if ($test !== '') {

on line 57 with:

 function ifHook( &$parser, $test = '', $then = '', $else = '' ) {
  if ( (string)$test !== '' ){

Although the above fix doesn't appear to work on PHP 4.3.9

Alteration and localization

The file ParserFunctions.i18n.php contains the localization for the parserfunctions. Adding more may be done by editing it according to the following guidelines.

In the latest MediaWiki versions, a new case for the language code should be added to function efParserFunctionsWords, for example:

        $words['fr'] = array(
	    'expr'       => array( 0, 'calcul',        'expr' ),
            'if'         => array( 0, 'si',            'if' ),
            'ifeq'       => array( 0, 'si-similaire',  'ifeq' ),
            'ifexpr'     => array( 0, 'si-calcul',     'ifexpr' ),
            'switch'     => array( 0, 'achemine',      'switch' ),
	    'default'    => array( 0, '#default' ); // same
            'ifexist'    => array( 0, 'si-existe',     'ifexist' ),
	    'time'       => array( 0, 'temps',         'time' ),
	    'rel2abs'    => array( 0, 'rel-a-abso',    'rel2abs' ),
	    'titleparts' => array( 0, 'part-titre',    'titleparts' ),
  • Please note that every hook established in function wfSetupParserFunctions must have an associated magic-words statement for it to work. Failure to associate a magic word may result in PHP warning messages (see bug #10166).

This method may not work on older version. Alternatively, hooks may be established in function wfSetupParserFunctions, as follows.

// fr
$wgParser->setFunctionHook( '#calcul', array( &$wgExtParserFunctions, 'expr' ) );
$wgParser->setFunctionHook( '#si', array( &$wgExtParserFunctions, 'ifHook' ) );
$wgParser->setFunctionHook( '#si-similaire', array( &$wgExtParserFunctions, 'ifeq' ) );
$wgParser->setFunctionHook( '#si-calcul', array( &$wgExtParserFunctions, 'ifexpr' ) );
$wgParser->setFunctionHook( '#achemine', array( &$wgExtParserFunctions, 'switchHook' ) );
$wgParser->setFunctionHook( '#si-existe', array( &$wgExtParserFunctions, 'ifexist' ) );	
$wgParser->setFunctionHook( '#temps', array( &$wgExtParserFunctions, 'time' ) );	
  • Tested on MediaWiki 1.6.10

See also

Other languages: de it nl ru vi

External links