Manual:Tag extensions

Individual projects will often find it useful to extend the built-in wiki markup with additional capabilities, whether simple string processing, or full-blown information retrieval. Tag Extensions allow users to create new custom tags that do just that. For example, one might use a tag extension to introduce a simple &lt;donation /&gt; tag, which injects a donation form into the page. Extensions, along with Parser Functions and Hooks are the most effective way to change or enhance the functionality of MediaWiki. To see existing extensions built by other MediaWiki users see: Extension Matrix. You should always check the matrix before you start work on an extension to make sure someone else hasn't done exactly what you are trying to do.

A simple tag extension consists of a callback function, which is hooked to the parser so that, when the parser runs, it will find and replace all instances of a specific tag, calling the corresponding callback function to render the actual HTML.

Example
This example registers a callback function for the &lt;sample&gt; tag. When a user adds this tag to a page like this:, the parser will call the efSampleRender function, passing in three arguments:


 * $input : Input between the &lt;sample&gt; and &lt;/sample&gt; tags, or null if the tag is "closed", i.e. &lt;sample /&gt;
 * $args : Tag arguments, which are entered like HTML tag attributes; this is an associative array indexed by attribute name.
 * $parser : The parent parser (a Parser object); more advanced extensions use this to obtain the contextual Title, parse wiki text, expand braces, register link relationships and dependencies, etc.
 * $frame : The parent frame (a PPFrame object). This is used together with $parser to provide the parser with more complete information on the context in which the extension was called.

Attributes
Let's look at another example:

This example dumps the attributes passed to the tag, along with their values. It's quite evident that this allows for flexible specification of new, custom tags. You might, for example, define a tag extension that allows a user to inject a contact form on their user page, using something like &lt;emailform to="User" email="user@foo.com" /&gt;.

There is a veritable plethora of tag extensions available for MediaWiki, some of which are listed on this site; others can be found via a quick web search. While a number of these are quite specialised for their use case, there are a great deal of well-loved and well-used extensions providing varying degrees of functionality.

Conventions
While an extension can be a single file, it is recommended that, for each extension, a separate subdirectory  of the extensions directory is created, containing three files:


 * a small setup file,
 * an internationalisation file,
 * a  file with the bulk of the code.

The setup file adds an element to the  array, which specifies which files are to be loaded:

Publishing your extensions

 * 1) Create a new page on this wiki named Extension: with information on your extension, how to install it, and screenshots of it in use. A convenient template has been created to hold this information called Template:Extension.  See the template page for more information.  You should also add as much detail as possible to the body of the page, and it is wise to check back fairly regularly to respond to user questions on the associated talk page.  Also, make sure the page belongs to Category:Extensions. NOTE: If you already have a page for your extension on meta.wikimedia.org then please do not start a new page here. Your page will be moved by an admin, with complete revision history - in the meantime, continue to edit at meta.
 * 2) Extensions that create new hooks within the extension code should register them on extension hook registry.
 * 3) Notify the mediawiki-l mailing list.

Security Concerns
You'll notice above that the input in the examples above is escaped using htmlspecialchars</tt> before being returned. It is vital that all user input is treated in this manner before echoing it back to the clients, to avoid introducing vectors for arbitrary HTML injection, which can lead to cross-site scripting vulnerabilities.

Timing and extensions
If you change the code for an extension, all pages that use the extension will, theoretically, immediately reflect the results of new code. Technically speaking, this means your code is executed each and every time a page containing the extension is rendered.

In practice, this is often not the case, due to page caching - either by the MediaWiki software, the browser or by an intermediary proxy or firewall.

To bypass MediaWiki's parser cache and ensure a new version of the page is generated, click on edit, replace "action=edit" in the URL shown in the address bar of your browser by "action=purge" and submit the new URL. The page and all templates it references will be regenerated, ignoring all cached data. The purge action is needed if the main page itself is not modified, but the way it must be rendered has changed (the extension was modified, or only a referenced template was modified).

If this is not sufficient to get you a fresh copy of the page, you can normally bypass intermediary caches by adding '&rand=somerandomtext' to the end of the above URL. Make sure 'somerandomtext' is different every time.

How do I disable caching for pages using my extension?
Since MediaWiki 1.5, the parser is passed as the third parameter to an extension. This parser can be used to invalidate the cache like this:

To disable all server side caching on the site, put the following code in LocalSettings.php:

Regenerating the page when another page is edited
Maybe you don't want to disable caching entirely, you just want the page to be regenerated whenever another page is edited, similar to the way that template transclusions are handled. This can be done using the parser object that is passed to your hook function. The following method was lifted from CoreParserFunctions.php and appears to work for this purpose.

Since version 1.16alpha
Parser hook functions are passed a reference to the parser object and a frame object; these should be used to parse wikitext.

Parser::recursiveTagParse</tt> has been around since version 1.8. Its advantages include simplicity (it takes just one argument and returns a string) and the fact that it parses extension tags in $text</tt>, so you can nest extension tags.

The second parameter to recursiveTagParse, $frame</tt>, is an optional argument introduced in MW 1.16 alpha (r55682).
 * If $frame</tt> is provided (using the value of $frame</tt> passed to your extension), then any template parameters in $text</tt> will be expanded. In other words, content such as   </tt> will be recognized and converted into the appropriate value.
 * If $frame</tt> is not provided (e.g., $parser->recursiveTagParse( $text )</tt>), or if $frame</tt> is set to false, then template parameters will not be expanded;  </tt> will not be altered.  Although this unlikely to be the desired behavior, this was the only option available before MW 1.16alpha.

However, one step of parsing that is still skipped for tags, even when using recursiveTagParse, is Parser::preSaveTransform. preSaveTransform is the first step of parsing, responsible for making permanent changes to the about-to-be saved wikitext, such as: The original call to preSaveTransform intentionally skips such conversions within all extension tags.
 * Converting signatures (, ~ ,  )
 * Expanding link labels (e.g., changing Help:Contents into Contents ). Without this step, shorthand links such as Help:Contents are considered to be invalid, and are left in their wikitext form when parsed.
 * Expanding templates.

Version 1.8 to version 1.15
The only difference before 1.16alpha is that the $frame argument was not available for Parser::recursiveTagParse</tt>.

If the resulting inability to recognize template variables is a problem, see Extensions and Templates and bug 2257 for more information and workarounds.

Before version 1.8
Before version 1.8, the following, less pretty, approach must be used:

The fourth and fifth parameters to Parser::parse are $lineStart</tt> and $clearState</tt>; these dictate how the parser behaves. $lineStart</tt>, when true, indicates that the wikitext is to be treated as starting on a new line (use this when dealing with blocks, or handling lists, etc.). $clearState</tt>, when true, indicates that the parser should clear internal state information; in most cases, this should be false.

Note that <tt>Parser::parse</tt> returns a ParserOutput object, not raw HTML, as in the example above.

In cases where this does not work (often due to order of operations, nesting or other hook confusion), use a cloned copy of the parser object:

Extensions and Templates
Before MW 1.16alpha (r55682), if template parameters were used inside extension tags (e.g., " was passed directly to the extension and not transformed into the correct value specified when the template was called.  This is because in previous versions of the parser, extensions are parsed before templates.

Since version 1.16alpha
As of r55682, extensions can make use of a new option for how to process the text within the extension tag, fully fixing this problem. Namely, using the <tt>$frame</tt> parameter for the recursiveTagParse function tells the parser to expand any template parameters (the <tt>$frame</tt> parameter provides the parser with the necessary context to use when looking up the values of the parameters). For example: For this extension, any template parameters in <tt>$text</tt> would be expanded when converted to <tt>$output</tt>.

Before version 1.16alpha
In prior MW versions, one possible workaround is to use #tag: to invoke a tag as if it were a parser function; see Extension:TagParser for details. As of MediaWiki 1.12 (Jan 2008), the #tag: function is not an extension but part of the core MediaWiki code; see Help:Magic_words.

For instance:



could be rewritten as:



or


 * " " as

This would permit the template variable(s) to be substituted correctly.

See bug 2257 for more info and possible patches.

Another workaround for this issue is to create a new parser function that expands template variables and then creates the extension code. For example, to call the  extension with template parameters, you would create a new parser function like this:

Then you would call the function on a page like this:

Since version 1.5
Since MediaWiki 1.5, XML-style parameters (tag attributes) are supported. The parameters are passed as the second parameter to the hook function, as an associative array. The value strings have already had HTML character entities decoded for you, so if you emit them back to HTML, don't forget to use, to avoid the risk of HTML injection.

Before version 1.5
Before MediaWiki 1.5, you have to pass any parameters in between the extension tags. That is, you have to invent a special syntax for "options", and then analyse the hook's input text for them. One possible syntax would be: @option1=foo @option2=bar

...content to be processed by the extension....

In the extension function, you would then look for lines looking like <tt>@option1=foo</tt> before performing the normal processing. You are of course free to choose some other syntax.

How can I avoid modification of my extension's HTML output?
The current extension code assumes parser hook extensions will produce inline material and they are inserted before the final block-level rendering stages (see 8997).

One way to work around this is to make your extension's parser hook function output a marker, instead of the actual result, and then replace that marker with the actual result in a handler function registered for the ParserAfterTidy hook.

Alternatively, instead of outputting a marker, it would also be possible to output the result in an armored form (e.g. Base64-Encoded), and unarmor (decode) it in the ParserAfterTidy handler.

How do I get my extension to show up on Special:Version?
In order for your extension to be displayed on the MediaWiki Special:Version page, you must assign extension credits within the PHP code.

To do this, add a <tt>$wgExtensionCredits</tt> variable as the first executable line of code before the hook line or function definition.

An example extension credit is:

Replace <tt>validextensionclass</tt> with one of the following (unless your extension falls under multiple classes&mdash;then create a credit for each class):
 * 'specialpage'&mdash;reserved for additions to MediaWiki Special Pages;
 * 'parserhook'&mdash;used if your extension modifies, complements, or replaces the parser functions in MediaWiki;
 * 'variable'&mdash;extension that add multiple functionality to MediaWiki;
 * 'other'&mdash;all other extensions.