MediaWiki code snippets

From Organic Design
Revision as of 04:39, 22 July 2009 by Rob (talk | contribs) (add snippet to remove links to the image page on images)
To be a good MediaWiki coder requires a few key things (see also MW:How to debug and MW:Developer hub).
  • Full browser and shell access to a running instance of every major version
  • Local access to the source code for all those versions
  • Use wfDebugDieBacktrace() to stop code and report the call stack
  • A good text editor with regular expression support file search capability (we use Geany which runs on most platforms)
  • A wikia setup so that extension code changes can be quickly tested in all versions and different extension versions can be quickly swapped
  • Tools or code for being able to stop the php code and output the necessary items in the scope
  • Tools for debugging the JS and CSS environment (eg. firebug)
  • Bookmarks for all the documentation you've found useful
  • Bookmarks to code snippets and examples (within your own wiki,, other sites and in the mediawiki code)
  • Your own repository of snippets for achieving common objectives in the mediawiki runtime environment


Get article content


Edit or create an article

Editing or creating an article are both achieved using the Article::doEdit method which takes three parameters (the third is optional). The first two are the text content and edit summary. The third optional parameter is for flags which adjust the operation. The available flags and their meaning are listed below followed by example usage.

  • EDIT_NEW: Article is known or assumed to be non-existent, create a new one
  • EDIT_UPDATE: Article is known or assumed to be pre-existing, update it
  • EDIT_MINOR: Mark this edit minor, if the user is allowed to do so
  • EDIT_SUPPRESS_RC: Do not log the change in recentchanges
  • EDIT_FORCE_BOT: Mark the edit a "bot" edit regardless of user rights
  • EDIT_DEFER_UPDATES: Defer some of the updates until the end of index.php
  • EDIT_AUTOSUMMARY: Fill in blank summaries with generated text where possible


  • Note: $wgUser must be set before calling this function.

Image URLs

Given the name of an image page, obtain the full URL of the image.


Image links

Sometimes you might want to prevent images from linking to the image page. This extension function removes the link.



Here's an example which was created in response to a support-desk question. It prevents users from editing other users user-pages:


Here is a similar example which restricts all namespaces except MAIN from anonymous users:


The following snippet causes all requests to be redirected to HTTPS if the user is a sysop:


Returning content to the client

Raw wikitext content

This function returns the raw content specified in $text, it can be called any time from extension-setup or after. If the $save parameter is supplied it will bring up a download dialog with the default name set to $save, otherwise it will download and open unprompted. If $expand is set to true, then any templates, parser-functions or variables in the content will be expanded.


Return an HTTP error page


Domain-based default redirect

If no page title is specified, redirect to a default depending on the domain name in the requested URL. In this example requests to or any of it's subdomains with no title specified will redirect to the Welcome to ABC article, and any requests to the exact domain of without a title end up at the XYZ Home article. Titleless requests to any other domain which resolves to this example wiki will be unaffected and left to the rest of the configuration to deal with. This code should be executed early in the LocalSettings before any extensions are included, but after $wgServer is defined.

Add a meta tags to the page


Using the parser

Parse wikitext


Expand templates only


Replace triple-brace arguments in wikitext content


$parser->replaceVariables($wikitext, $args, true); </php>

If $wikitext is set to "hello {{{you}}} this is {{{me}}}", then the "you" and "me" keys of the $args array will replace the corresponding triple-brace arguments in the wikitext content. This is a useful method to know because there are actually a number of difficulties involved in implementing it since it must account for both named and ordered parameters and default values (which can also contain brace-expressions).

Using named parameters from a parser-function callback

You can use named parameters in your parser functions, eg {{#drops:for=Rikkukin the Defender|zone=The Ascent|h=3}}, but you will need to manually split the args into key/value pairs in your callback function, such as in the following example code:


This snippet will create a hash from the arguments passed to your callback function (ignoring any which are objects such as the first one which is $parser). The resulting hash will contain numeric keys for all the normal non-named parameters in your parser-function, and non-numeric keys matching all the name=value parameters.

Return codes for parser functions

Typical example.


See also:

Protecting raw HTML output from modification by MediaWiki

See: How can I avoid modification of my extension's HTML output on Thanks to Duesentrieb for digging out this info.

Post processing to remove unwanted breaks and entities from output


MediaWiki Environment

Article title

This should be called at an appropriate time such as from the OutputPageBeforeHTML hook.


$wgOut->setPageTitle('foo'); </php>

Article queries

Info.svg See MW:Manual:Database access for additional information about database access in MediaWiki.

List article titles from a category


Adjust the $list addition to your own needs. This example creates a title object for each and then calls the getPrefixedText method which returns the title as a string including namespace.

List categories an article belongs to


Check if a title is in a category


Article queries using DPL

This DPL query example provides a standard list of page links in wikitext bullet list format.




This function returns an array of the brace structure found in the passed wikitext parameter.


') {

$brace =& $braces[$depths[$depth-1]]; $brace[LENGTH] = $match[0][1]-$brace[OFFSET]+2; $brace[DEPTH] = $depth--; } else { $depths[$depth++] = count($braces); $braces[] = array( NAME => $match[1][0], OFFSET => $match[0][1] ); } } return $braces; } </php>}}

The following input,


Gives the following array:

    [0] => Array(
        [NAME]   => #bar
        [OFFSET] => 3
        [LENGTH] => 29
        [DEPTH]  => 1

    [1] => Array(
        [NAME]   => foo
        [OFFSET] => 17
        [LENGTH] => 13
        [DEPTH]  => 2

    [2] => Array(
        [NAME]   => moo
        [OFFSET] => 32
        [LENGTH] => 7
        [DEPTH]  => 1

The array output is designed to integrate with the substr_replace function arguments subject, replace, offset, length. The index 0, 1, 2 order referes to the order functions are found (from left to right).

Google Analytics


Force all headings to use outline numbering

There is a user-preference to make all headings use outline numbering, but no way to make that a default for all users. Here's a few lines of code which can be added to your LocalSettings.php file which do that.


Integrating with the Skin

Adding a new action tab

The following code adds a new action tab with a corresponding link. To process the new action, add a processing function to the UnknownAction hook.


Wikitext in Sidebar

Replace a section such as toolbox or navlinks in the skins/MonoBook.php file with the following:


Development server identification

The idea is to have a picture or text that allows a developer to quickly see that they are on the development instance and not the production instance of MediaWiki. By adding to the content of $wgSiteNotice in a conditional every article will have the change for that domain map.


This approach was based on W:User:East718/include, and the image source is Image:Gnome-devel.svg

See also