Open main menu



This template should be added to all extension pages on this wiki (but only the main page). It will add a useful infobox (see below) and will automatically add the extension to Category:All extensions, along with the appropriate status and implementation type categories.


Kopieren und einfügen:

{{Extension/de|templatemode =
|name            = 
|status          = 
|type1           = 
|type2           = 
|hook1           = 
|hook2           = 
|benutzername    = 
|autor           = 
|beschreibung    = 
|bild            = 
|imagesize       = 
|version         = 
|update          = 
|mediawiki       = 
|php             =
|needs-updatephp =
|schema-registry =
|lizenz          = 
|download        = 
|readme          = 
|changelog       = 
|parameters      = 
|tags            = 
|rechte          = 
|beispiel        = 
|kompatibilität  = 
|bugzilla        =

For help with Parameter values, sieheunten.

OOjs UI icon advanced.svg
Erscheinungsstatus: unbekannt
Einbindung {{{type1}}}, {{{type2}}}

Letzte Version {{{version}}} ({{{update}}})
MediaWiki {{{mediawiki}}}
PHP {{{php}}}
Datenbankänderungen {{{needs-updatephp}}}
Lizenz Keine Lizenz angegeben
Herunterladen {{{download}}}
Übersetze die Extension/de Erweiterung wenn sie auf verfügbar ist
Probleme [[phab:tag/mediawiki-extensions-{{{bugzilla}}}|Offene Aufgaben]] · Einen Fehler melden


This section describes parameters that govern infobox content. For help with templatemode and other control parameters, please see Control parameters.

Parameter Beschreibung
name Name der Erweiterung
status Aktueller Freigabe-Stand

One of:

  • unstable (broken - do not use this extension)
  • experimental (early stages of development, may change drastically)
  • beta (stable but not fully tested)
  • stable (stable version)
  • unmaintained (unmaintained - previously claimed to be stable, now unmaintained)
  • unknown (default)

If the status is anything other than the above, it will be ignored and the default value of 'Unknown' will be displayed in the template instead. In cases where the value is omitted, it will be categorized as unknown. In cases where the value is invalid, it will be placed in a special category so that the error can be caught and fixed.

implementation type

The implementation strategy(s) employed in building this extension. This parameter is used to create categories that help programmers find examples of various MediaWiki specific implementation strategies or patterns. Although the values of this parameter sometimes coincide with the use case or purpose of an extension, that is not reason for this parameter. If the values you have chosen for this parameter do not adequately identify the purpose or possible use cases, we recommend you add additional category links as needed.

Legal values for the type1, type2, ... parameters are:

  • parser - catchall for uncategorized parser extensions. If you have written a parser extension, please use one of the following more specific types:
  • access - catchall for user access extensions, that is, extensions that create, authenticate, grant permissions, revoke permissions, or monitor the activity of users. If you have written an access extension, please use one of the following more specific types:
    • user activity - extensions that monitor user activity (logins, logouts, new user creation, etc.)
    • user identity - extensions that create and delete users, and/or verify the identity of a user
    • user rights - extensions to the rights management system, e.g. changes to the way rights are assigned, API, maintenance tools (does not include extensions that merely name the rights needed to use the features of that extension; for this purpose use the rights parameter)
  • interface - catchall for uncategorized user interface extensions.
    • media - extensions that permit the embedding of multimedia content on wiki pages by registering a file extension with $wgMediaHandlers.
    • mywiki - extensions that provide infrastructure so that users may personalize their MediaWiki experience and/or assist in the management of that infrastructure
    • notify - extensions that email users, broadcast messages and provide other forms of community notification
    • page action - extensions that enhance or modify page actions. This includes anything that implements an action that reads, writes, searches for, creates, renames, deletes, redirects or discusses a page. It does not include rights (use user rights) or logs (use user activity).
    • search - extensions that search through and select articles for users.
    • skin - extensions adding CSS or JavaScript, or implementing hook functions to change the look and feel of MediaWiki via the skins framework.
    • ajax - extensions that use Ajax programming techniques.
    • special - extensions that subclass the SpecialPage class, use one of its hooks, or patch one or more functions in SpecialPage.php. See Manual:Special pages for more information.
  • other
    • api - extensions that add a new API module or extend a core API module.
    • hook - Hook extension - defines a new hook - see hook1, etc. below if you want to define hooks used by your extension

We are in the process of revising the values of this page. Types below this point are likely to be deprecated or redefined. We apologize for the inconvenience. See the talk on type taxonomy for more information.
  • database - adds tables and/or fields to the database backing a MediaWiki installation
  • data extraction - Data extraction
  • example - Not a real extension, but an example of how to write one

Any other value for 'type' is invalid, and will cause the extension to be placed in Category:Extensions with invalid or missing type.

Note: Many extensions have more than one type, if this applies to yours, replace |type= with |type1=|type2=|type3=.... You may define up to six types for an extension.

name of each hook used by the extension

Entering values in this field is a good way to get exposure for your extension and help other developers. Each documented hook will automatically add the extension to a category listing extensions that use that hook. This category is autolinked to each hook article so that programmers can easily find examples of extensions that use a particular hook.

For built-in hooks:

  • use the hook name alone. Please see Manual:Hooks for values (but omit introductory '/').

For custom hooks defined by extensions:

For multiple hooks, assign the first hook to hook1, the second to hook2 and so on.

username The author's username on (if they have one). May be omitted, but if present it will be used to link to the author's user & user_talk page. It should be provided without namespace and without [[]]s.
author The extension author's name, if different from their username. Free text. If omitted then the 'username' field will be used (if present).
description short description
image screenshot or logo of extension. It should be provided without namespace and without [[]]s.
imagesize facultative, size of the image (default size is 220px)
version last version
update date of the last update
mediawiki required version of MediaWiki
php required version of PHP
needs-updatephp yes indicates that the extension requires a database table schema change or a similar action, before the MediaWiki can run. It is a common pitfall: your MediaWiki will stall, if you forgot to run update.php - if the extension requires it.

Extensions which conform to MediaWiki extension standards come with a schema change script which you need to start manually (once) before starting and accessing the MediaWiki through your browser, and after you copied all the extension files to $IP/extensions/ExtensionName and inserted require_once( "$IP/extensions/ExtensionName" ) to $IP/LocalSettings.php:

php $IP/maintenance/update.php
$IP stands for the Installation Path (or "directory") of your MediaWiki installation, the same directory that holds LocalSettings.php, index.php etc..
schema-registry yes indicates that the extension's schema changes are registered at Database table and field registration.
license license(s) governing use of this extension, e.g. GPL
download link to the download : SVN, {{WikimediaDownload}} with server=gerrit, or other. If you put the code into page in the MediaWiki wiki, link to it using a full page name and section name, e.g. [[Extension:Example/version_1.22a#Code]] (it must remain valid when bot-copied elsewhere)
readme external link to the readme file, e.g.
changelog external link to the changelog file, e.g. Extension:LDAP Authentication/Changelog
parameters available parameters for LocalSettings.php
tags any tags your extension uses (e.g. <tag1>, <tag2>).
rights rights added by the extension. Not to be confused with the license! Rights are such as makebot or desysop, not such as GFDL or LGPL or GPL - those are licenses!
namespace namespace in which this extension is used
example example, website or screenshot of working extension
compatibility compatibility chart, e.g. Template:Extension Testing
bugzilla Bugzilla MediaWiki extension component name
CheckUsageNameOverride override the page name used for the check usage link.


Parameter Beschreibung
templatemode Controls auto-categorization of host page.

Normally left blank. Alternate values are:

  • nocats - suppresses categorization and the 'check usage' link. Use this value if you are adding this template to subpages of an extension or to how-to documentation of extensions. For example, the usage image above sets templatemode=nocats because this isn't an actual extension page and we don't want to add this page to any categories on account of it.
  • nousage - suppresses the 'check usage' link. Link is also suppressed if the page is a subpage; it is not in the Extension: namespace; or if suppressed by 'templatemode=nocats'

If this is left blank, this template will add the host page to Category:All extensions and to one or more additional categories, depending on the values assigned to the Content parameters.

Verwendung der InfoboxEdit

Existierende ErweiterungsseitenEdit

If you want to add the infobox to an existing page, copy and paste the code at the top of this page.

Erstelle einen neuen ErweiterungsartikelEdit

If you want to create a new extension page, enter the name below and click the button. A new page will be created with the infobox template already in place.

A developer sharing their code in the MediaWiki code repository should expect:

Feedback / Criticism / Code reviews
Review and comments by other developers on things like framework use, security, efficiency and usability.
Developer tweaking
Other developers modifying your submission to improve or clean-up your code to meet new framework classes and methods, coding conventions and translations.
Improved access for wiki sysadmins
If you do decide to put your code on the wiki, another developer may decide to move it to the MediaWiki code repository for easier maintenance. You may then request commit access to continue maintaining it.
Future versions by other developers
New branches of your code being created automatically as new versions of MediaWiki are released. You should backport to these branches if you want to support older versions.
Incorporation of your code into other extensions with duplicate or similar purposes — incorporating the best features from each extension.
Credit for your work being preserved in future versions — including any merged extensions.
Similarly, you should credit the developers of any extensions whose code you borrow from — especially when performing a merger.

Any developer who is uncomfortable with any of these actions occurring should not host in the code repository. You are still encouraged to create a summary page for your extension on the wiki to let people know about the extension, and where to download it.

Verbesserung dieser VorlageEdit

If you would like to improve on this template, danke! This is a complicated template so here is some help along the way:

Verbessern der DokumentationEdit

If you would like to fix documentation, please be aware that documentation and code is split into two files:

  • Template:Extension/Doc - stores all documentation.
  • Template:Extension - stores only the code for the template and a small amount of non-included material (category links, transcluded documentation link).

In addition, Template:Extension/Sample stores the boiler plate that is preloaded into newly created pages and contains some basic documentation on how to fill in the template parameters. It needs to be kept in sync with Template:Extension/Doc.

Die Schaltfläche Erstelle ErweiterungEdit

To improve the create extension button behavior:


Im Allgemeinen:

  • To make this template easy to use, each label in the infobox is linked to documentation on the template parameter(s) it displays. If you add a parameter, please be sure to also add it to the content parameter documentation and link its label to that documentation.

To change/correct/add to the implementation type parameters:

To change the behavior of the hook parameters:


See if the following pages are still ok, after edited this template.