手冊:開發擴充功能

擴充功能：

• 開發
• 標籤擴充功能
• 解析器函數
• 函數鉤
• ���殊頁面
• 外觀
• 魔術字
• API
• 內容模型

如果你想在維基媒體的網站上部署你的擴充功能，請閱讀編寫一個部署用的擴充功能

每個擴充功能都由三部分組成：

1. 組態
2. 執行
3. 在地化

一個最小的擴充功能只需如下結構：

MyExtension/extension.json

儲存安裝的說明。 檔名必須為「extension.json」。 （在MediaWiki 1.25版之前，設定說明位於一個以副檔名命名的MyExtension/MyExtension.php檔案中。 許多擴充功能在此PHP檔案中仍然具有向下相容的間隙。）

MyExtension/includes/ (or MyExtension/src/)

儲存擴充功能的PHP可執行代碼。

MyExtension/resources/ (or MyExtension/modules/)

儲存擴充功能的客戶端資源，例如JavaScript，CSS和LESS。

MyExtension/i18n/*.json

儲存擴充功能的在地化資訊。

當您在開發擴充功能時，請將上文中的MyExtension替換為您開發的擴充功能的名字。 使用大駝峰式命名法來命名資料夾和PHP檔案，這是檔案命名的通常慣例。^[1] （BoilerPlate extension對於開發您的擴充功能是一個好的開始。）

設定

編寫設定部分的最終目標是使擴充功能安裝儘可能容易，因此使用者只需將此行添加到LocalSettings.php中：

wfLoadExtension( 'MyExtension' );

如果你要讓你的擴充功能是使用者可組態的，則需要定義和記錄一些組態參數，並且使用者的設定應如下所示：

wfLoadExtension( 'MyExtension' );
$wgMyExtensionConfigThis = 1;
$wgMyExtensionConfigThat = false;

為了讓這一操作變得簡單，您的設定檔案需要完成許多工（以下各節中有詳細描述）：

• 註冊您的擴充功能使用的所有媒體處理程式、解析器函數、特殊頁面、自訂XML標籤和變數。
• 定義和/或驗證為擴充功能定義的任何組態變數。
• 準備您的擴充功能程式用於自動載入的類（class）
• 確定哪些部分需要立即完成設定，哪些部分需要在MediaWiki核心已初始化和組態後再完成設定。
• 定義您的擴充功能添加的額外的鉤。
• 建立或檢查擴充功能所需的任何新資料庫表。
• 為您的擴充功能程式設定在地化。

通過MediaWiki註冊功能

MediaWiki在其Special:Version頁面上列出了已安裝的所有擴充功能。 例如，您可以在Special:Version上檢視此Wiki上安裝的所有擴充功能。

為此，請將擴充功能詳細資訊添加到extension.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
}

許多欄位都是可選的，但填寫它們仍然是一個好習慣。 manifest_version指的是extension.json 檔案所針對的架構版本。 可用的版本為1和2。請參見有關此功能的文件。 除非需要支援較舊版本的MediaWiki，否則請選擇最新版本。

除上述註冊外，您還必須將功能「鉤」到MediaWiki中。 上面僅設定了特殊:版本頁面。 執行此操作的方式取決於您開發的擴充功能的類型。 有關詳細資訊，請參閱每種擴充功能類型的文件：

擴充功能：

• 開發
• 標籤擴充功能
• 解析器函數
• 函數鉤
• 特殊頁面
• 外觀
• 魔術字
• API
• 內容模型

使您的擴充功能可由使用者組態

如果您希望使用者能夠組態您的擴充功能程式，則需要提供一個或多個組態變數。 最好能給這些變數起一個唯一的名稱。 同樣需要遵循MediaWiki命名常規（例如，全域變數名應以$wg作為開始）。

例如，如果您擴充功能的名字為「MyExtension」，您可能需要將所有相關的組態變數以$wgMyExtension作為開始。 重要的是，此時MediaWiki的核心變數尚未定義，您需要做一些合理的檢查，以確保沒有已發布的擴充功能以這種方式開始其變數命名。 使用者不會因為您使用了重疊的變數名而在您的擴充功能和其它擴充功能之間選擇。

同樣建議在安裝說明中包括所有組態變數的詳盡文件。

以下是一個可以用來入門的範例樣板：

{
	"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
}

注意：在wfLoadExtension( 'BoilerPlate' );執行後，全域變數$wgBoilerPlateEnableFoo不存在。 如果您給變數賦值（如在LocalSettings.php中），則來自extension.json的值將不會被使用。

關於在擴充功能中使用通用變數，請參考Manual:Configuration for developers 。

將class準備用於自動載入

如果您決定使用類/對象開發您的擴充功能，媒體維基提供了一個簡單的搜尋類檔案位置的方法。 在大多數情況下，這將免去開發自己的__autoload($classname)方法。

如想使用媒體維基的自動載入功能，您需要向AutoloadClasses 欄位添加資訊。 欄位名稱為類名稱，內容為檔名。 對於一個簡單的單類檔案擴充功能，類檔案經常與擴充功能同名。所以您的自動載入部分內容可能是如下：

{
	"AutoloadClasses": {
		"MyExtension": "includes/MyExtension.php"
	}
}

檔名的路徑與extension.json檔案所在目錄相對。

對於更複雜的擴充功能，應該要考慮到命名空間。 參見Manual:Extension.json/Schema#AutoloadNamespaces以取得更多細節。

定義額外的勾點

參見手冊:函數鉤 。

添加資料庫表格

Make sure the extension doesn't modify the core database tables. Instead, extension should create new tables with foreign keys to the relevant MW tables.

警告：	If your extension is used on any production WMF-hosted wiki please follow the Schema change guide.

If your extension needs to add its own database tables, use the LoadExtensionSchemaUpdates hook. See the manual page for more information on usage.

參見：

• 在地化（摘要）
• 在地化（詳情）
• 命名空間

添加紀錄檔

On MediaWiki, all actions by users on wiki are tracked for transparency and collaboration. See Manual:Logging to Special:Log for how to do it.

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

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.^[2][3]

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

	if ( ExtensionRegistry::getInstance()->isLoaded( 'OpenID Connect' ) {
    ...
	}

在地化

Localisation – 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. 新增訊息 Localization checks – discusses common problems with localized messages

Store message definitions in a localisation JSON file, one for each language key your extension is translated in. The messages are saved with a message key and the message itself using standard JSON format. Each message id should be lowercase and may not contain spaces. Each key should begin with the lowercased extension name. An example you can find in the MobileFrontend extension. Here is an example of a minimal JSON file (in this case en.json):

en.json

{
	"myextension-desc": "Adds the MyExtension great functionality.",
	"myextension-action-message": "This is a test message"
}

The documentation for message keys can be stored in the JSON file for the pseudo language with code qqq. A documentation of the example above can be:

qqq.json:

{
	"myextension-desc": "The description of MyExtension used in Extension credits.",
	"myextension-action-message": "Adds 'message' after 'action' triggered by user."
}

{
	"MessagesDirs": {
		"MyExtension": [
			"i18n"
		]
	}
}

In your setup and implementation code, replace each literal use of the message with a call to wfMessage( $msgID, $param1, $param2, ... ). In classes that implement IContextSource (as well as some others such as subclasses of SpecialPage), you can use $this->msg( $msgID, $param1, $param2, ... ) instead. Example:

wfMessage( 'myextension-addition', '1', '2', '3' )->parse()

It's possible to use i18n functions in JavaScript too. Look at 手冊:Messages API for details.

擴充功能類型

擴充功能：

• 開發
• 標籤擴充功能
• 解析器函數
• 函數鉤
• 特殊頁面
• 外觀
• 魔術字
• API
• 內容模型

Extensions can be categorized based on the programming techniques used to achieve their effect. Most complex extensions will use more than one of these techniques:

• Subclassing: MediaWiki expects certain kinds of extensions to be implemented as subclasses of a MediaWiki-provided base class:
  • 特殊頁面 – Subclasses of the 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. Both reports and data entry forms can be generated. They are used for both reporting and administration purposes.
  • 外觀 – Skins change the look and feel of MediaWiki by altering the code that outputs pages by subclassing the MediaWiki class SkinTemplate .
• 函數鉤 – A technique for injecting custom PHP code at key points within MediaWiki processing. They are widely used by MediaWiki's parser, its localization engine, its extension management system, and its page maintenance system.
  • Tag-function associations – XML style tags that are associated with a php function that outputs HTML code. You do not need to limit yourself to formatting the text inside the tags. You don't even need to display it. Many tag extensions use the text as parameters that guide the generation of HTML that embeds Google objects, data entry forms, RSS feeds, excerpts from selected wiki articles.
• 魔術字 – A technique for mapping a variety of wiki text string to a single id that is associated with a function. Both variables and parser functions use this technique. All text mapped to that id will be replaced with the return value of the function. The mapping between the text strings and the id is stored in the array $magicWords. The interpretation of the id is a somewhat complex process – see 手冊:魔術字 for more information.
  • Variable – Variables are something of a misnomer. They are bits of wikitext that look like templates but have no parameters and have been assigned hard-coded values. Standard wiki markup such as {{PAGENAME}} or {{SITENAME}} are examples of variables. 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.
  • 解析器函數 – {{functionname: argument 1 | argument 2 | argument 3...}}. Similar to tag extensions, parser functions process arguments and returns a value. Unlike tag extensions, the result of parser functions is wikitext.
• API模組 – You can add custom modules to MediaWiki's action API, that can be invoked by JavaScript, bots or third-party clients.
• 頁面內容模型 – If you need to store data in formats other than wikitext, JSON, etc. then you can create a new ContentHandler .

• 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.
• Release branches: release branches of the extension are compatible with matching branches of core, e.g. sites using MediaWiki 1.42 need to use the REL1_42 branch of the extension. (For extensions hosted on Gerrit, these branches are automatically created when new versions of MediaWiki are released.) 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 backported manually.

許可協定

MediaWiki is an open-source project and users are encouraged to make any MediaWiki extensions under an Open Source Initiative (OSI) approved license compatible with GPL-2.0-or-later (Wikimedia's standard software license).

We recommend adopting one of the following compatible licenses for your projects in Gerrit:

• GNU General Public License, version 2 or later (GPL-2.0-or-later)
• MIT License (MIT)
• BSD License (BSD-3-Clause)
• Apache License 2.0 (Apache-2.0)

For extensions that have a compatible license, you can request developer access to the MediaWiki source repositories for extensions. To specify the licence in code and with "license-name" a key should be used to provide it's short name, e.g. "GPL-2.0-or-later" or "MIT" adhering to the list of identifiers at spdx.org.

發布

To autocategorize and standardize the documentation of your existing extension, please see 模板:Extension/zh . To add your new extension to this Wiki:

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 create a 開發者帳戶 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.

If you intend to have your extension deployed on Wikimedia sites (including possibly Wikipedia), additional scrutiny is warranted in terms of performance and security. Consult 編寫一個部署用的擴充功能 .

You should provide public domain help documentation for features provided by your extension. 說明:CirrusSearch is a good example. You should give users a link to the documentation via the addHelpLink() function.

Extension developers should open an account on Wikimedia's Phabricator , and request a new project for the extension. 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.

參見

• 手冊:擴充功能登錄 - provides further developer documentation on how to register extensions and skins.
• API:擴���功能 – explains how your extension can provide an API to clients
• Manual:Extending wiki markup
• 手冊:代碼編寫約定
• Best practices for extensions
• 資源載入器

Learn by example

• 擴充功能:Examples – implements some example features with extensive inline documentation
  • examples git repo with this and other example code
• Extension:BoilerPlate – a functioning boilerplate extension, useful as a starting point for your own extension (git儲存庫)
  • Read the Example extension, base your own code on the BoilerPlate extension.
• cookiecutter-mediawiki-extension – a cookiecutter template which generates a boilerplate extension (with variables etc.)

• • Can also generate the BoilerPlate extension.
• List of simple extensions - copy specific code from them

參考資料