Šablona:Extension

Template documentation

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 Kategorie: Všechna rozšíření , along with the appropriate status and implementation type categories.

Použití

Zkopíruj a vlož: {{Extension |templatemode = |name = |status = |type1 = |type2 = |hook1 = |hook2 = |newhook1 = |newhook2 = |username = |author = |description = |image = |imagesize = |version = |update = |version preview = |update preview = |compatibility policy = |mediawiki = |php = |needs-updatephp = |composer = |table1 = |table2 = |license = |download = |readme = |changelog = |example = |namespace = |parameters = |tags = |rights = |compatibility = |bugzilla = |phabricator = |vagrant-role = }} Jaký má být obsah parametrů, viz níže

Základní informace k tomuto rozšíření MediaWiki {{{name}}} Stav rozšíření: unknown Zavádí {{{type1}}}, {{{type2}}} Popis {{{description}}} Napsal(i) SomeAuthor (SomeUsertalk) Aktuální verze {{{version}}} ({{{update}}}) Latest preview version {{{version preview}}} ({{{update preview}}}) Compatibility policy MediaWiki {{{mediawiki}}} PHP {{{php}}} Změny v databázi {{{needs-updatephp}}} Composer {{{composer}}} Tabulky [[Special:MyLanguage/Template:Extension/{{{table1}}} table|{{{table1}}}]][[:Template:Extension/{{{table1}}} table| ]] [[Special:MyLanguage/Template:Extension/{{{table2}}} table|{{{table2}}}]][[:Template:Extension/{{{table2}}} table| ]] Licence {{{license}}} Zdrojový kód {{{download}}} {{{readme}}} {{{changelog}}} Příklad {{{example}}} Jmenný prostor {{{namespace}}} Parametry {{{parameters}}} Přidané tagy {{{tags}}} Přidaná práva {{{rights}}} Použité háčky (hooks) hook1 hook2 Poskytované háčky (hooks) newhook1 newhook2 {{{compatibility}}} Přeložte rozšíření Extension, jsou-li dostupné jeho lokalizační zprávy na webu translatewiki.net Vagrant role {{{vagrant-role}}} Issues [[phab:tag/{{{phabricator}}}|Open tasks]] · Report a bug

Obsah parametrů

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

Content parameters

Parametr	Popis
name	název rozšíření
status	current release status 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 archive - archived - deprecated or merged with another extension 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. release status colour scheme
type1 type2 type3 type4 type5 type6	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. Allowed 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: contenthandler - Extensions using ContentHandler . link - customized link markup, e.g. [[...]] parser function - custom parameterized template markup, e.g. {{#name: ... }} tag - custom XML tag markup, e.g. <tagname>...</tagname> variable - custom unparameterized template markup, e.g. {{NAME}} extended syntax - Extensions that add non-standard wiki syntax (i.e. not tags, parser functions, or variables). 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 action s. 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 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 database - adds tables and/or fields to the database backing a MediaWiki installation data extraction - Data extraction filerepo - extension that adds new file repository types as file backend 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/cs. 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.
hook1 hook2 hook3 hook4 ... hook90	použité háčky 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: 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.
author	The extension author's name, if different from their MediaWiki.org username. Libovolný text. If omitted then the 'username' field will be used (if present).
description	stručný popis
image	snímek obrazovky, nebo logo rozšíření It should be provided without namespace and without [[]]s.
imagesize	facultative, size of the image (default size is 220px)
version	poslední verze
update	datum poslední aktualizace
compatibility policy	compatibility policy (accepted values are master, rel, and ltsrel). (backlog )
mediawiki	vyžaduje MediaWiki verze
php	vyžaduje PHP verze
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. no 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 $IP/extensions/ExtensionName and inserted wfLoadExtension( "ExtensionName"); into "LocalSettings.php", run from the command line: cd path/to/wiki_install_directory cd maintenance php update.php $IP stands for the Installation Path (or "directory") of your MediaWiki installation, the same directory that holds LocalSettings.php , index.php etc..
composer	If applicable the name of the "vendor" as well as the "package" should be entered in the format vendor/package, e.g. mediawiki/semantic-media-wiki to point people directly to packagist.org, which serves as the package archive.
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 Extension:CheckUser will link to Extension:CheckUser/cu_changes table . Don't list core tables such as page or revision ; only list tables that are added by extensions.
license	license governing use of this extension, as one of the codes found in https://spdx.org/licenses/, e.g. GPL-2.0-or-later, GPL-2.0-only or GPL-3.0-or-later, etc.
download	link to the download : Git, {{WikimediaDownload/cs}} with server=svn in case it was not migrated from Subversion . 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. https://phabricator.wikimedia.org/r/browse/mediawiki/extensions/Flow;master;README
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	Additional compatibility information, for instance compatibility charts (formerly using Template:Extension Testing). It's encouraged to add any client-side compatibility information here too, especially when diverging from expectations of full support for a browser.
translate	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: ext-LOWERCASE(NOSPACES(Label as defined in config)), 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".
bugzilla	Bugzilla MediaWiki extension component name
phabricator	Phabricator project name
CheckUsageNameOverride	override the page name used for the check usage link.

Control parameters

Control parameters

Parametr

Popis

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/cs and to one or more additional categories, depending on the values assigned to the Content parameters.

Použití infoboxu

Na existující stránce k rozšíření

Pokud chcete přidat infobox na stránku, která již existuje, zkopírujte do ní výše uvedený kód.

Založení nové stránky k rozšíření

Pokud chcete přidat stránku k rozšíření, které zde dosud svoji stránku nemá, napište do níže uvedeného vstupního pole formuláře jeho název a klikněte na tlačítko. Tím dojde k založení nové stránky, která již bude tuto informační šablonu obsahovat.

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

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.

Doplnění této šablony o další položky

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:

• Template:Extension/Sample : The boilerplate extension that is preloaded into newly-created pages.
• Template:Extension/CreateExtensionInputBox : An input box that can be inserted wherever you want users to easily create extensions. For documentation on the <inputbox> tag, please see Extension:InputBox .

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.
• Template:Extension/TypeSwitch : Stores the possible values for the type field. Multiple values are implemented by calling this template with Template:Foreach.
• Template:Extension/TypeSwitchNoCats : Does not need to be modified when adding a new type. Used instead of Template:Extension/TypeSwitch when this template is used in templatemode=nocats. Templates used with Template:Foreach can only take one parameter so we need to wrap the call to Template:Extension/TypeSwitch with another template that sets the mode.

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 templatemode=nocats. 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

TemplateData

Editors can experiment in this template’s sandbox (create | mirror) and testcases (create) pages.
Subpages of this template.

Maintenance: vulnerabilities, archived