View source for Manual:Developing extensions/pl

<languages/>
{{ExtensionTypes}}
{{mbox| text = Jeżeli chcesz, by twoje rozszerzenie było umieszczone na stronach WikiMedia, przeczytaj {{ll|Writing an extension for deployment}}}}
[[File:MediaWiki-extensions-icon.svg|125px|alt=Rozszerzenia MediaWiki|{{dir|{{pagelang}}|left|right}}]]

Każde [[Special:MyLanguage/Manual:Extensions|rozszerzenie]] posiada 3 części:

# [[#Setup|Ustawienie]]
# [[#Execution|Wykonanie]]
# [[#Localisation|Lokalizacja]]

<div class="mw-translate-fuzzy">
Minimalistyczne rozszerzenie zawiera 3 pliki, po jednym na każdą część:
</div>

; ''MyExtension''/extension.json
: Zawiera instrukcje [[#Setup|do ustawienia]]. Plik musi się nazywać ''extension.json''. (Przed MediaWiki 1.25 instrukcje ustawiania byly w pliku <code>''MyExtension''/''MyExtension''.php</code> nazwanym po nazwie rozszerzenia Wiele rozszerzeń wciąż ma podkładki kompatybilności z wcześniejszymi wersjami w tym pliku PHP.
; ''MyExtension''/includes/ (or ''MyExtension''/src/)
: <span class="mw-translate-fuzzy">Przechowuje kod [[#Execution|wykonywania]] dla rozszerzenia.</span>
; ''MyExtension''/resources/ (or ''MyExtension''/modules/)
: <span lang="en" dir="ltr" class="mw-content-ltr">Stores the client-side resources such as JavaScript, CSS and LESS for the extension.</span>
; ''MyExtension''/i18n/*.json
: Przechowuje informacje o [[#Localisation|lokalizacje]] dla rozszerzenie.

<span class="mw-translate-fuzzy">Kiedy tworzysz rozszerzenie, zastąp "MyExstension" nazwą swojego rozszerzenia.</span>
Używaj nazw ''UpperCamelCase'' dla nazwy jego folderu  i pliku/ów PHP; to jest konwencja [[Special:MyLanguage/Manual:Coding conventions#File naming|nazywania plików]].<ref>[[mailarchive:wikitech-l/2011-August/054839.html]]</ref>
<span lang="en" dir="ltr" class="mw-content-ltr">(The {{git repo|project=mediawiki/extensions/BoilerPlate|text=BoilerPlate extension}} is a good starting point for your extension.)</span>

{{Note|1=Póki tworzysz, możesz chcieć wyłączyć cachowanie przez ustawianie <code>{{ll|Manual:$wgMainCacheType|$wgMainCacheType}} = CACHE_NONE</code> i <code class=mw-highlight>{{ll|Manual:$wgCacheDirectory|$wgCacheDirectory}} = {{#tag:span|false|class=k}}</code>, w przeciwnym wypadku, wiadomości systemowe i inne zmiany mogą się nie pokazać.}}

__TOC__

<span id="Setup"></span>
== Ustawianie ==

<div lang="en" dir="ltr" class="mw-content-ltr">
Your goal in writing the setup portion is to make installing the extension as easy as possible, so users only have to add this line to LocalSettings.php:
</div>

<syntaxhighlight lang="php">
wfLoadExtension( 'MyExtension' );
</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
If you want to make your extension user configurable, you need to define and document some configuration parameters and your users' setup should look something like this:
</div>

<syntaxhighlight lang="php">
wfLoadExtension( 'MyExtension' );
$wgMyExtensionConfigThis = 1;
$wgMyExtensionConfigThat = false;
</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
To reach this simplicity, your setup file needs to accomplish a number of tasks (described in detail in the following sections):
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* register any media handler, [[Special:MyLanguage/Manual:Parser functions|parser function]], [[Special:MyLanguage/Manual:Special pages|special page]], [[Special:MyLanguage/Manual:Tag extensions|custom XML tag]], and [[Special:MyLanguage/Manual:Variable|variable]] used by your extension.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* define and/or validate any configuration variables you have defined for your extension.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* prepare the classes used by your extension for autoloading
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* determine what parts of your setup should be done immediately and what needs to be deferred until the MediaWiki core has been initialized and configured
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* define any additional [[Special:MyLanguage/Manual:Hooks|hooks]] needed by your extension
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* create or check any new database tables required by your extension.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* set up localisation for your extension
</div>

{{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Good practice is to add a README file with basic info about how to install and configure the extension.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can use either plain text or [https://secure.phabricator.com/book/phabricator/article/remarkup/ Phabricator markup syntax].</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, see the [https://phabricator.wikimedia.org/diffusion/EPFM Phabricator Diffusion page] for the {{ll|Extension:Page Forms}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If markdown is used, add the file extension <code>.md</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, see the <code>README.md</code> file for {{ll|Parsoid}} on [https://phabricator.wikimedia.org/diffusion/GPAR Phabricator Diffusion].</span>}}

<span id="Registering_features_with_MediaWiki"></span>
===Rejestrowanie cech z MediaWiki===
<span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki lists all the extensions that have been installed on its <code>Special:Version</code> page.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">For example, you can see all the extensions installed on this wiki at [[Special:Version]].</span>

{{MW 1.25|and after}}
<span lang="en" dir="ltr" class="mw-content-ltr">To do this, add the extension details to ''{{ll|extension.json|extension.json}}''.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">The entry will look something like this:</span>

<syntaxhighlight lang="json">
{
	"name": "Example",
	"author": "John Doe",
	"url": "https://www.mediawiki.org/wiki/Extension:Example",
	"description": "This extension is an example and performs no discernible function",
	"version": "1.5",
	"license-name": "GPL-2.0-or-later",
	"type": "validextensionclass",
	"manifest_version": 1
}
</syntaxhighlight>


<span lang="en" dir="ltr" class="mw-content-ltr">Many of the fields are optional, but it's still good practice to fill them out.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">The <code>manifest_version</code> refers to the version of the schema the {{ll|extension.json|extension.json}} file is written against.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">The available versions are 1 and 2. See [[Special:MyLanguage/Manual:Extension.json/Schema#manifest version|here for the documentation on this feature]].</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Unless you need to support an older version of MediaWiki, pick the latest version.</span>

<span lang="en" dir="ltr" class="mw-content-ltr">In addition to the above registration, you must also "hook" your feature into MediaWiki.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">The above only sets up the Special:Version page.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">The way you do this depends on [[#Extension types|the type of your extension]].</span>
<span lang="en" dir="ltr" class="mw-content-ltr">For details, please see the documentation for each type of extension:</span>
{{ExtensionTypes}}

<span id="Making_your_extension_user_configurable"></span>
===Robienie twojego rozszerzenia możliwego do konfiguracji przez użytkownika===
<span lang="en" dir="ltr" class="mw-content-ltr">If you want your user to be able to configure your extension, you'll need to provide one or more configuration variables.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">It is a good idea to give those variables a unique name.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">They should also follow MediaWiki [[Special:MyLanguage/Manual:Coding conventions/PHP#Naming|naming conventions]] (e.g. global variables should begin with $wg).</span>

<span lang="en" dir="ltr" class="mw-content-ltr">For example, if your extension is named "MyExtension", you might want to name all your configuration variables to begin with <code>$wgMyExtension</code>.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">It is important that '''none''' of the MediaWiki core begins its variables this way and you have done a reasonable job of checking to see that none of the published extensions begin their variables this way.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Users won't take kindly to having to choose between your extension and some other extensions because you chose overlapping variable names.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
It is also a good idea to include extensive documentation of any configuration variables in your installation notes.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Here is an example boiler plate that can be used to get started:
</div>

<syntaxhighlight lang="json">
{
	"name": "BoilerPlate",
	"version": "0.0.0",
	"author": [
		"Your Name"
	],
	"url": "https://www.mediawiki.org/wiki/Extension:BoilerPlate",
	"descriptionmsg": "boilerplate-desc",
	"license-name": "GPL-2.0-or-later",
	"type": "other",
	"AutoloadClasses": {
		"BoilerPlateHooks": "includes/BoilerPlateHooks.php",
		"SpecialHelloWorld": "includes/SpecialHelloWorld.php"
	},
	"config": {
		"BoilerPlateEnableFoo": {
			"value": true,
			"description": "Enables the foo functionality"
		}
	},
	"callback": "BoilerPlateHooks::onExtensionLoad",
	"ExtensionMessagesFiles": {
		"BoilerPlateAlias": "BoilerPlate.i18n.alias.php"
	},
	"Hooks": {
		"NameOfHook": "BoilerPlateHooks::onNameOfHook"
	},
	"MessagesDirs": {
		"BoilerPlate": [
			"i18n"
		]
	},
	"ResourceModules": {
		"ext.boilerPlate.foo": {
			"scripts": [
				"resources/ext.boilerPlate.js",
				"resources/ext.boilerPlate.foo.js"
			],
			"styles": [
				"resources/ext.boilerPlate.foo.css"
			]
		}
	},
	"ResourceFileModulePaths": {
		"localBasePath": "",
		"remoteExtPath": "BoilerPlate"
	},
	"SpecialPages": {
		"HelloWorld": "SpecialHelloWorld"
	},
	"manifest_version": 2
}
</syntaxhighlight>

<span lang="en" dir="ltr" class="mw-content-ltr">Note that after calling {{phpi|wfLoadExtension( 'BoilerPlate' );}} the global variable <code>$wgBoilerPlateEnableFoo</code> does not exist.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">If you set the variable, e.g. in <code>LocalSettings.php</code> then the default value given in extension.json will not be used.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
For more details on how to use global variable inside custom extensions, please refer to {{ll|Manual:Configuration for developers}}.
</div>

<span id="Preparing_classes_for_autoloading"></span>
===Przygotowanie klas do autokonfiguracji===
<span lang="en" dir="ltr" class="mw-content-ltr">If you choose to use classes to implement your extension, MediaWiki provides a simplified mechanism for helping PHP find the source file where your class is located.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">In most cases this should eliminate the need to write your own <code>__autoload($classname)</code> method.</span>

<span lang="en" dir="ltr" class="mw-content-ltr">To use MediaWiki's autoloading mechanism, you add entries to the {{ll|Manual:$wgAutoloadClasses|AutoloadClasses}} field.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">The key of each entry is the class name; the value is the file that stores the definition of the class.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">For a simple one class extension, the class is usually given the same name as the extension, so your autoloading section might look like this (extension is named ''MyExtension''):</span>

<syntaxhighlight lang="json">
{
	"AutoloadClasses": {
		"MyExtension": "includes/MyExtension.php"
	}
}
</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
The filename is relative to the directory the extension.json file is in.
</div>

<span lang="en" dir="ltr" class="mw-content-ltr">For more complex extensions, [https://php.net/language.namespaces namespaces] should be considered.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">See [[Special:MyLanguage/Manual:Extension.json/Schema#AutoloadNamespaces|Manual:Extension.json/Schema#AutoloadNamespaces]] for details.</span>

<span id="Defining_additional_hooks"></span>
===Definiowanie dodatkowych haczyków===

Zobacz {{ll|Manual:Hooks}}.

<span id="Adding_database_tables"></span>
===Dodawanie tablic baz danych===
<span lang="en" dir="ltr" class="mw-content-ltr">Make sure the extension doesn't modify the core database tables.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Instead, extension should create new tables with foreign keys to the relevant MW tables.</span>  
{{Warning|1=<span lang="en" dir="ltr" class="mw-content-ltr">If your extension is used on any production WMF-hosted wiki please follow the [https://wikitech.wikimedia.org/wiki/Schema_changes Schema change guide].</span>}}

<span lang="en" dir="ltr" class="mw-content-ltr">If your extension needs to add its own database tables, use the {{ll|Manual:Hooks/LoadExtensionSchemaUpdates|LoadExtensionSchemaUpdates}} hook.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">See the manual page for more information on usage.</span>

<span id="Set_up_localisation"></span>
===Ustawianie lokalizacji===

Zobacz:
* [[#Localisation|<span lang="en" dir="ltr" class="mw-content-ltr">Localisation (summary)</span>]]
* {{ll|Localisation|2=<span lang="en" dir="ltr" class="mw-content-ltr">Localisation (detailed)</span>}}
* {{ll|Manual:Language#Namespaces|2=<span lang="en" dir="ltr" class="mw-content-ltr">Namespaces</span>}}

<span id="Add_logs"></span>
===Dodaj rejestry===
<span lang="en" dir="ltr" class="mw-content-ltr">On MediaWiki, all actions by users on wiki are tracked for transparency and collaboration.</span>
Zobacz {{ll|Manual:Logging to Special:Log}} by wiedzieć jak to zrobić.

<div lang="en" dir="ltr" class="mw-content-ltr">
== Handling dependencies ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Assume that an extension requires the presence of another extension, for example because functionalities or database tables are to be used and error messages are to be avoided in case of non-existence.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
For example the extension {{ll|Extension:CountingMarker|CountingMarker}} requires the presence of the extension {{ll|Extension:HitCounters|HitCounters}} for certain functions.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
One way to specify this would be by using the <code>[[Special:MyLanguage/Manual:Extension.json/Schema#requires|requires]]</code> key in [[Special:MyLanguage/Manual:Extension.json|extension.json]].
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Another option is using ExtensionRegistry (available since MW 1.25):
</div>

<syntaxhighlight lang="php">
	if ( ExtensionRegistry::getInstance()->isLoaded( 'HitCounters', '>=1.1' ) {
		/* do some extra stuff, if extension HitCounters is present in version 1.1 and above */
	}
</syntaxhighlight>

Currently (as of February 2024, MediaWiki 1.41.0) the name of the extension-to-be-checked needs to exactly match the name in their extension.json.<ref>https://www.mediawiki.org/wiki/Topic:Xyjw7nhfzaas5r5z</ref><ref>https://phabricator.wikimedia.org/T356596</ref>

Example: if you want to check the load status of extension "OpenIDConnect", you have to use it with a ''space''

<syntaxhighlight lang="php">
	if ( ExtensionRegistry::getInstance()->isLoaded( 'OpenID Connect' ) {
    ...
	}
</syntaxhighlight>

<span id="Localisation"></span>
== Lokalizacja ==
{{mbox
| type = notice
| text =  <nowiki/>
* {{ll|Localisation|Localisation}} – <span lang="en" dir="ltr" class="mw-content-ltr">discusses the MediaWiki localisation engine, in particular, there is a list of features that can be localized and some review of the MediaWiki source code classes involved in localization.</span>
* {{ll|Help:System message#Adding new messages|2=Tworzenie nowych komunikatów}}
* {{ll|Localization checks}} – <span lang="en" dir="ltr" class="mw-content-ltr">discusses common problems with localized messages</span>
}}

{{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">While developing, you may want to disable both cache by setting {{phpi|$wgMainCacheType {{=}} CACHE_NONE}} and {{phpi|$wgCacheDirectory {{=}} false}}, otherwise your system message changes may not show up.</span>}}

<div lang="en" dir="ltr" class="mw-content-ltr">
If you want your extension to be used on wikis that have a multi-lingual readership, you will need to add localisation support to your extension.
</div>

<span id="Store_messages_in_&lt;language-key&gt;.json"></span>
=== Przechowywanie komunikatu w ''<language-key>''.json ===
<span lang="en" dir="ltr" class="mw-content-ltr">Store message definitions in a localisation JSON file, one for each language key your extension is translated in.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">The messages are saved with a message key and the message itself using standard JSON format.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Each message id should be lowercase and may '''not''' contain spaces.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Each key should begin with the lowercased extension name.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">An example you can find in the [https://github.com/wikimedia/mediawiki-extensions-MobileFrontend/blob/master/i18n/de.json MobileFrontend extension].</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Here is an example of a minimal JSON file (in this case ''en.json''):</span>

''en.json''

<syntaxhighlight lang="json">{
	"myextension-desc": "Adds the MyExtension great functionality.",
	"myextension-action-message": "This is a test message"
}</syntaxhighlight>

<span id="Store_message_documentation_in_qqq.json"></span>
=== Przechowywanie dokumentacji komunikatu w  ''qqq''.json ===
<span lang="en" dir="ltr" class="mw-content-ltr">The documentation for message keys can be stored in the JSON file for the pseudo language with code '''qqq'''.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">A documentation of the example above can be:</span>

''qqq.json'':

<syntaxhighlight lang="json">{
	"myextension-desc": "The description of MyExtension used in Extension credits.",
	"myextension-action-message": "Adds 'message' after 'action' triggered by user."
}
</syntaxhighlight>

<span id="Load_the_localisation_file"></span>
=== Ładowanie pliku lokalizacyjnego ===

<div lang="en" dir="ltr" class="mw-content-ltr">
In your extension.json, define the location of your messages files (e.g. in directory '''i18n/'''):
</div>

<syntaxhighlight lang="json">
{
	"MessagesDirs": {
		"MyExtension": [
			"i18n"
		]
	}
}
</syntaxhighlight>

<span id="Use_wfMessage_in_PHP"></span>
=== Używanie wfMessage w PHP ===
<span lang="en" dir="ltr" class="mw-content-ltr">In your setup and implementation code, replace each literal use of the message with a call to <code>wfMessage( $msgID, $param1, $param2, ... )</code>.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">In classes that implement {{ll|Manual:RequestContext#IContextSource|IContextSource}} (as well as some others such as subclasses of SpecialPage), you can use {{phpi|$this->msg( $msgID, $param1, $param2, ... )}} instead.</span>
Przykład:

<syntaxhighlight lang="php">
wfMessage( 'myextension-addition', '1', '2', '3' )->parse()
</syntaxhighlight>

<span id="Use_mw.message_in_JavaScript"></span>
=== Używanie mw.message w JavaScript ===
<span lang="en" dir="ltr" class="mw-content-ltr">It's possible to use i18n functions in JavaScript too.</span>
Zobacz {{ll|Manual:Messages API}} po szczegóły.

{{anchor|Execution}}
<span id="Extension_types"></span>
== Rodzaje rozszerzeń ==

{{ExtensionTypes}}
<span lang="en" dir="ltr" class="mw-content-ltr">Extensions can be categorized based on the programming techniques used to achieve their effect.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Most complex extensions will use more than one of these techniques:</span>

* '''<span lang="en" dir="ltr" class="mw-content-ltr">Subclassing:</span>''' <span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki expects certain kinds of extensions to be implemented as subclasses of a MediaWiki-provided base class:</span>
** '''{{ll|Manual:Special pages|nsp=0}}''' – <span lang="en" dir="ltr" class="mw-content-ltr">Subclasses of the {{ll|Manual:SpecialPage.php|SpecialPage}} class are used to build pages whose content is dynamically generated using a combination of the current system state, user input parameters, and database queries.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Both reports and data entry forms can be generated.</span> <span lang="en" dir="ltr" class="mw-content-ltr">They are used for both reporting and administration purposes.</span>
** '''{{ll|Manual:Skins|nsp=0}}''' – <span lang="en" dir="ltr" class="mw-content-ltr">Skins change the look and feel of MediaWiki by altering the code that outputs pages by subclassing the MediaWiki class {{ll|Manual:SkinTemplate.php|SkinTemplate}}.</span>
* '''{{ll|Manual:Hooks|nsp=0}}''' – <span lang="en" dir="ltr" class="mw-content-ltr">A technique for injecting custom PHP code at key points within MediaWiki processing.</span> <span lang="en" dir="ltr" class="mw-content-ltr">They are widely used by MediaWiki's parser, its localization engine, its extension management system, and its page maintenance system.</span>
** '''{{ll|Manual:Tag extensions|2=<span lang="en" dir="ltr" class="mw-content-ltr">Tag-function associations</span>}}''' – <span lang="en" dir="ltr" class="mw-content-ltr">[[w:XML|XML]] style tags that are associated with a php function that outputs HTML code.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You do not need to limit yourself to formatting the text inside the tags.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You don't even need to display it.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Many tag extensions use the text as parameters that guide the generation of [[w:HTML|HTML]] that embeds Google objects, data entry forms, RSS feeds, excerpts from selected wiki articles.</span>
* '''{{ll|Manual:Magic words|nsp=0}}''' – <span lang="en" dir="ltr" class="mw-content-ltr">A technique for mapping a variety of wiki text string to a single id that is associated with a function.  Both [[Special:MyLanguage/Manual:Variable|variables]] and [[Special:MyLanguage/Manual:Parser functions|parser functions]] use this technique.</span> <span lang="en" dir="ltr" class="mw-content-ltr">All text mapped to that id will be replaced with the return value of the function.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The mapping between the text strings and the id is stored in the array $magicWords.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The interpretation of the id is a somewhat complex process – see {{ll|Manual:Magic words}} for more information.</span>
** '''{{ll|Manual:Variable|nsp=0}}''' – <span lang="en" dir="ltr" class="mw-content-ltr">Variables are something of a misnomer.</span> <span lang="en" dir="ltr" class="mw-content-ltr">They are bits of wikitext that look like templates but have no parameters and have been assigned hard-coded values.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Standard wiki markup such as <code>{{ll|Help:Variables|<nowiki>{{PAGENAME}}</nowiki>}}</code> or <code>{{ll|Help:Variables|<nowiki>{{SITENAME}}</nowiki>}}</code> are examples of variables.</span> <span lang="en" dir="ltr" class="mw-content-ltr">They get their name from the source of their value: a php variable or something that could be assigned to a variable, e.g. a string, a number, an expression, or a function return value.</span>
** '''{{ll|Manual:Parser functions|nsp=0}}''' – <code><nowiki>{{</nowiki>''functionname'': ''argument 1'' | ''argument 2'' | ''argument 3''...}}</code>.  <span lang="en" dir="ltr" class="mw-content-ltr">Similar to tag extensions, parser functions process arguments and returns a value.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Unlike tag extensions, the result of parser functions is [[w:wikitext|wikitext]].</span>
* '''{{ll|API:Extensions|2=Moduły API}}''' – <span lang="en" dir="ltr" class="mw-content-ltr">you can add custom modules to MediaWiki's [[Special:MyLanguage/API:Main page|action API]], that can be invoked by JavaScript, bots or third-party clients.</span>
* '''{{ll|Manual:Page content models|nsp=0}}''' – <span lang="en" dir="ltr" class="mw-content-ltr">If you need to store data in formats other than wikitext, JSON, etc. then you can create a new {{ll|Manual:ContentHandler|ContentHandler}}.</span>

<span id="Support_other_core_versions"></span>
==Wspieranie innych wersji jądra==
<!-- keep this in sync with [[Compatibility#MediaWiki_extensions]] -->

<div lang="en" dir="ltr" class="mw-content-ltr">
There are two widespread conventions for supporting older versions of MediaWiki core:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* Master: the master branch of the extension is compatible with as many old versions of core as possible. This results in a maintenance burden (backwards-compatibility hacks need to be kept around for a long time, and changes to the extension need to be tested with several versions of MediaWiki), but sites running old MediaWiki versions benefit from functionality recently added to the extension.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* Release branches: release branches of the extension are compatible with matching branches of core, e.g. sites using MediaWiki {{MW stable branch number}} need to use the {{MW stable branch git}} branch of the extension.
</div> <span lang="en" dir="ltr" class="mw-content-ltr">(For extensions hosted on [[Special:MyLanguage/gerrit|gerrit]], these branches are automatically created when new versions of MediaWiki are released.)</span> <span lang="en" dir="ltr" class="mw-content-ltr">This results in cleaner code and faster development but users on old core versions do not benefit from bugfixes and new features unless they are [[Backporting fixes|backported]] manually.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
Extension maintainers should declare with the <code>[[Special:MyLanguage/Template:Extension#compatibility policy|compatibility policy]]</code> parameter of the {{tl|Extension}} template which convention they follow.
</div>

{{anchor|Licensing}}
<span id="License"></span>
== Licencja ==

{{Extension/License}}

<span id="Publishing"></span>
== Publikacja ==
<span lang="en" dir="ltr" class="mw-content-ltr">To autocategorize and standardize the documentation of your existing extension, please see {{ll|Template:Extension}}.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">To add your new extension to this Wiki:</span>
{{Extension/CreateExtensionInputBox}}

<div lang="en" dir="ltr" class="mw-content-ltr">
=== Deploying and registering ===
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">If you intend to have your extension deployed on Wikimedia sites (including possibly Wikipedia), additional scrutiny is warranted in terms of performance and security.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Consult {{ll|Writing an extension for deployment}}.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
If your extension adds namespaces, you may wish to register its [[Special:MyLanguage/Extension default namespaces|default namespaces]]; likewise, if it adds database tables or fields, you may want to register those at {{ll|database field prefixes}}.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Please be aware that review and deployment of new extensions on Wikimedia sites can be extremely slow, and in some cases has taken more than two years.<ref>[[phabricator:T148848]]</ref>
</div>

<span id="Help_documentation"></span>
=== Dokumentacja pomocy ===
<span lang="en" dir="ltr" class="mw-content-ltr">You should provide [[Special:MyLanguage/Project:PD help|public domain help documentation]] for features provided by your extension.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Help:CirrusSearch}} is a good example.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">You should give users a link to the documentation via the {{ll|Manual:Special pages#Help page|addHelpLink()}} function.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
== Providing support / collaboration ==
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">Extension developers should open an account on Wikimedia's {{ll|Phabricator}}, and [[Special:MyLanguage/Phabricator/Creating and renaming projects|request a new project for the extension]].</span>
<span lang="en" dir="ltr" class="mw-content-ltr">This provides a public venue where users can submit issues and suggestions, and you can collaborate with users and other developers to triage bugs and plan features of your extension.</span>

<span id="See_also"></span>
== Zobacz też ==

* {{ll|Manual:Extension registration}} - provides further developer documentation on how to register extensions and skins.
* {{ll|API:Extensions}} &ndash; <span lang="en" dir="ltr" class="mw-content-ltr">explains how your extension can provide an API to clients</span>
* {{ll|Manual:Extending wiki markup}}
* {{ll|Manual:Coding conventions}}
* <span lang="en" dir="ltr" class="mw-content-ltr">[[Best practices for extensions|Best practices for extensions]]</span>
* {{ll|ResourceLoader}}

===Learn by example===
* {{ll|Extension:Examples}} &ndash; <span lang="en" dir="ltr" class="mw-content-ltr">implements some example features with extensive inline documentation</span>
** {{git repo |project=mediawiki/extensions/examples |text=<span lang="en" dir="ltr" class="mw-content-ltr">examples git repo with this and other example code</span>}}
* {{ll|Extension:BoilerPlate}} &ndash; <span lang="en" dir="ltr" class="mw-content-ltr">a functioning boilerplate extension, useful as a starting point for your own extension</span> ({{Git repo |project=mediawiki/extensions/BoilerPlate |text=<span lang="en" dir="ltr" class="mw-content-ltr">git repo</span>}})
** <span lang="en" dir="ltr" class="mw-content-ltr">''Read'' the Example extension, ''base your own code on'' the BoilerPlate extension.</span>
* [https://github.com/JonasGroeger/cookiecutter-mediawiki-extension cookiecutter-mediawiki-extension] – <span lang="en" dir="ltr" class="mw-content-ltr">a [https://cookiecutter.readthedocs.io/en/latest/ cookiecutter] template which generates a boilerplate extension (with variables etc.)</span>
<div lang="en" dir="ltr" class="mw-content-ltr">
** Allows you to get going quickly with your own extension.
</div>
**<span lang="en" dir="ltr" class="mw-content-ltr">Can also generate the BoilerPlate extension.</span>
* {{ll|List of simple extensions}} - <span lang="en" dir="ltr" class="mw-content-ltr">copy specific code from them</span>


<span id="References"></span>
== Przypisy ==
<references />

[[Category:Extension creation{{#translation:}}|{{PAGENAME}}]]