If specified, wraps the output into a given function call. For safety, all user-specific data will be restricted.

If given and the HashTables extension is available this will create a hash with the specified name (no visible output then)

Use this form to import HTML content into your wiki.

If you upload a zip file, the Collection Name field is used to differentiate the collection from a later version. Also all files will be grouped in a category by the same name. For example, let's say you're importing a collection of HTML files output from your software documentation system, you would enter a unique Collection ID like 'FluxCapacitor-v1.1' so that the whole collection is imported into an article hierarchy starting with 'FluxCapacitor-v1.1'. This way 10 different collections can be imported without clobbering each other.

Specifying an existing Collection Name (or parent path) will update existing wiki content.

If you want to import a single file into an existing article hierarchy, simply specify it's 'parent' as the Collection Name.

For example, if importing a new 'advanced_topics.html' that should exist at <code>'FluxCapacitor-v1.1/docs/advanced_topics.html'</code>, the parent would be 'FluxCapacitor-v1.1/docs/'

If given and ArrayExtension is available this will create an array with the specified name (no visible output then)

SQLite stores all data in a single file.

The directory you provide must be writable by the webserver during installation.

It should <strong>not</strong> be accessible via the web; this is why we're not putting it where your PHP files are.

The installer will write a <code>.htaccess</code> file along with it, but if that fails someone can gain access to your raw database.
That includes raw user data (email addresses, hashed passwords) as well as deleted revisions and other restricted data on the wiki.

Consider putting the database somewhere else altogether, for example in <code>/var/lib/mediawiki/yourwiki</code>.

When accessing the API using a cross-domain AJAX request (CORS), set this to the originating domain. This must be included in any pre-flight request, and therefore must be part of the request URI (not the POST body).

For authenticated requests, this must match one of the origins in the <code>Origin</code> header exactly, so it has to be set to something like <kbd>https://en.wikipedia.org</kbd> or <kbd>https://meta.wikimedia.org</kbd>. If this parameter does not match the <code>Origin</code> header, a 403 response will be returned. If this parameter matches the <code>Origin</code> header and the origin is whitelisted, the <code>Access-Control-Allow-Origin</code> and <code>Access-Control-Allow-Credentials</code> headers will be set.

For non-authenticated requests, specify the value <kbd>*</kbd>. This will cause the <code>Access-Control-Allow-Origin</code> header to be set, but <code>Access-Control-Allow-Credentials</code> will be <code>false</code> and all user-specific data will be restricted.

Label for a checkbox which will cause all banners in a campaign to be given the same weight

Button text. When clicked, the block log entries for a given user will be displayed.

If specified, will unblock the user.

Explains what data will be shared if the user chooses to submit data to MediaWiki.org. $1 is the JSON data that will be sent

User agent to query. If not specified, the agent in the request will be queried.

An identifier for persistent client-side data stored by this feature (such as impression counts). This field is optional for most campaigns. If you leave it blank, campaigns in the same category will share impression counts, or, if this campaign does not use the category feature, counts will be specific to this campaign. To share this data across several campaign categories, specify the same identifier for each campaign. Note: certain campaign categories used to be configured to use cookies for this feature. For campaigns in those categories, this identifier was the cookie name; such legacy cookies will be migrated. Also note that if the identifier is changed during a campaign, all counts to date will be lost.

The projects to list pages for. If this parameter is omitted, all projects will be included.

Undo the last edit to the page.

If the last user who edited the page made multiple edits in a row, they will all be rolled back.

Which pieces of information to get.

Note that if no values are selected, the result will contain the wikitext, but the output will be in a deprecated format.

Error message which will be shown if given user name is invalid. Parameters:
* $1 - the old or new username

Obtain the banner allocations for banners served by CentralNotice for all user types under the parametric filter.

This is a JSON only call.

Title of the special page. Special page title can be for a user or for an overview over all existing reviews. This depends on whether a user is passed as a parameter to the special page.
* $1 is the number if a user is passed
**0 means overview over all reviews
**1 reviews of one specific user
*$2 is the real name of the user

This page provides a linked data interface to entity values. Please provide the entity ID in the URL, using subpage syntax.
* Content negotiation applies based on you client's Accept header. This means that the entity data will be provided in the format preferred by your client. For a web browser, this will be HTML, causing your browser to be redirected to the regular entity page.
* You can explicitly request a specific data format by adding the appropriate file extension to the entity ID: Q23.json will return data in the JSON format, Q23.ttl will return RDF/Turtle, and so on.

The body of the notification on user talk page.
* $1 - plain username, can be used for GENDER
* $2 - translator's username or real name, if specified
* $3 - a comma list of language names, or the placeholder text {{msg-mw|Translationnotifications-generic-languages}}
* $4 - translatable page name
* $5 - a bulleted list of URLs to translation pages
* $6 - The message {{msg-mw|translationnotifications-email-priority}}. Empty if no priority was specified.
* $7 - The message {{msg-mw|translationnotifications-email-deadline}}. Empty if no deadline was specified.
* $8 - a custom message that can be added by the notification sender
* $9 - number of languages, can be used in PLURAL
* $10 - URL to notification preferences

User error message when there is a problem with the metadata mapping JSON format. Parameters:
* $1 - the technical error message given by PHP for the specific JSON error

There are three supported scenarios for installing Oracle as database backend:

If you wish to create database account as part of the installation process, please supply an account with SYSDBA role as database account for installation and specify the desired credentials for the web-access account, otherwise you can either create the web-access account manually and supply only that account (if it has required permissions to create the schema objects) or supply two different accounts, one with create privileges and a restricted one for web access.

Script for creating an account with required privileges can be found in "maintenance/oracle/" directory of this installation. Keep in mind that using a restricted account will disable all maintenance capabilities with the default account.

Timestamp format to use for output, 'ISO_8601' or 'MW'.  'MW' is deprecated here, so all clients should switch to 'ISO_8601'.  This parameter will be removed, and 'ISO_8601' will become the only output format.

Placeholder, which will be inserted into the text area, if the user clicks the bold text button in editor, and no text is selected.

Placeholder, which will be inserted into the text area, if the user clicks the italic text button in editor, and no text is selected.