Template:Extension

  {{Documentation|content= {{intricate template}} {{lua|Module:Extension|Module:ExtensionJson|Module:String}} {{Uses TemplateStyles|Template:Infobox/styles.css|Template:Extension/styles.css|Template:Extension/status.css}} 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 {{ll|Category:All extensions}}, along with the appropriate {{ ll|Category:Extensions by status |status}} and {{ ll|Category:Extensions by implementation type |implementation type}} categories.

{{Clear}}

Content parameters
This section describes parameters that govern infobox content. For help with templatemode and other control parameters, please see Control parameters. Any other value for 'type' is invalid, and will cause the extension to be placed in Category:Extensions with invalid or missing type.
 *  - custom parameterized template markup, e.g.
 *  - custom XML tag markup, e.g. 
 *  - custom unparameterized template markup, e.g.
 *  - Extensions that add non-standard wiki syntax (i.e. not tags, parser functions, or variables).
 * - catchall for, 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:
 * - extensions that monitor user activity (logins, logouts, new user creation, etc.)
 * - extensions that create and delete users, and/or verify the identity of a user
 * - 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)
 * - catchall for uncategorized user interface extensions.
 *  - extensions that permit the embedding of multimedia content on wiki pages by registering a file extension with.
 *  - extensions that provide infrastructure so that users may personalize their MediaWiki experience and/or assist in the management of that infrastructure
 * - extensions that email users, broadcast messages and provide other forms of community notification
 *  - extensions that enhance or modify . 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 ).
 * - extensions that search through and select pages for users.
 * - extensions adding CSS or JavaScript, or implementing hook functions to change the look and feel of MediaWiki via the skins framework.
 * - extensions that use Ajax programming techniques.
 * - extensions that subclass the class, use one of its hooks, or patch one or more functions in  . See  for more information.
 * other
 * - extensions that add a new API module or extend a core API module.
 * - Hook extension - defines a new hook - see hook1, etc. below if you want to define hooks used by your extension
 * - adds tables and/or fields to the database backing a MediaWiki installation
 * - Data extraction
 * - extension that adds new file repository types as file backend
 * - Not a real extension, but an example of how to write one
 * - extensions that new.
 * - extensions to the underlying programming language.
 * - extensions associated with localization
 * - extensions associated with localization

Note: Many extensions have more than one type, if this applies to yours, replace with. You may define up to six types for an extension. hook1 hook2 hook3 hook4 ...  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 page 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 for values (but omit introductory '/').

For custom hooks defined by extensions:
 * use extensionName/hookName . For a partial list of custom hooks, see Extension hook registry.

For multiple hooks, assign the first hook to hook1, the second to hook2 and so on. newhook1 newhook2 newhook3 newhook4 ... newhook90 

name of each hook provided by the extension

You might also want to add the hooks to Extension hook registry. username  The author's username on MediaWiki.org (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.    The extension author's name, if different from their MediaWiki.org username. Free text. If omitted then the 'username' field will be used (if present). description   short description  screenshot or logo of extension. It should be provided without namespace and without s.    facultative, size of the image without adding px, e.g. 360 (default size is 300px) last version date of the last update preview version date of the last update to the preview version compatibility policy   (accepted values are master, main, rel , and ltsrel ). Required version of MediaWiki. Most extensions should not need to use this — it defaults to the value of the property of. See also Category:Extensions without MediaWiki version and Category:Extensions with manual MediaWiki version. required version of PHP

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. should be set as a value since this assures that the extension does not need update.php to be run and thus avoids uncertainty

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 and inserted  into "LocalSettings.php", run from the command line:

composer  The extension's Composer package name, in the [ https://getcomposer.org/doc/04-schema.md#name standard format]. It will be automatically included if set in an extension's " composer.json " file (i.e. this parameter is not required in that case). It will be linked to the extension's page on [ https://packagist.org/ Packagist]. table1 table2 table3 table4 ... table30 name of each non-core table used by the extension

Links to a subpage of your extension page. For instance, " table1 = cu_changes " at will link to. Don't list core tables such as or  ; only list tables that are added by extensions. license governing use of this extension, as one of the codes found in https://spdx.org/licenses/, e.g. ,  or  , etc. download  link to the download : Git, WikimediaDownload. repo  Name of the Gerrit repository the extension's code is stored in, if different from the page name. Setting this automatically sets download, and allows the template to automatically load data from the appropriate file. external link to the readme file, e.g. https://phabricator.wikimedia.org/r/browse/mediawiki/extensions/Flow;master;README external link to the changelog file, e.g. Extension:XGlossary/Changelog Link to user-help for the extension. If not provided, will look for. If provided, full wikitext link should be given (because you may want to link to e.g. an external page). example, website or screenshot of working extension namespace in which this extension is used available parameters for LocalSettings.php any tags your extension uses (e.g. &lt;tag1&gt;, &lt;tag2&gt; ). rights added by the extension. Not to be confused with the license! Rights are such as ' or ', not such as GFDL or LGPL or GPL - those are licenses! Additional compatibility information, for instance compatibility charts. It's encouraged to add any client-side compatibility information here too, especially when diverging from expectations of full support for a browser. Bugzilla MediaWiki extension component name Phabricator project name

Optional parameter to link the exact page where (message group id with which) the extension will be translatable on translatewiki.net if enabled. If the default link is incorrect, manually set it to: role
 * ext-LOWERCASE ( NOSPACES (Label as defined in )), aka
 * the parameter you get in the URL after
 * typing the name of the extension in the search/filter box at translatewiki:Special:Translate or
 * searching for its name in languagestats after clicking "expand all".

override the page name used for the check usage link.

Control parameters
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.

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

Create a new extension page
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.

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

The Create extension button
To improve the create extension button behavior:


 *  : The boilerplate extension that is preloaded into newly-created pages.
 *  : An input box that can be inserted wherever you want users to easily create extensions. For documentation on the  tag, please see.

Infobox parameters
In general:


 * 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:
 * Check the talk page - there have been some extensive discussions about this field.


 * The valid types and what they link to are defined at Module:Extension

To change the behavior of the hook parameters:


 *  Template:Extension/HookInUse : Adds links and categories for a hook in use. Multiple hooks in use are implemented by calling this template with Template:Foreach.
 * Template:Extension/HookInUseNoCats : Used instead of Template:Extension/HookInUse when this template is used in . Templates used with Template:Foreach can only take one parameter so we need to wrap the call to Template:Extension/HookInUse with another template that sets the mode.

Test case
See if the following pages are still ok, after edited this template.
 * Extension:Description2
 * Template:Extension

}} Maintenance: vulnerabilities, archived