Search translations

Unrecognised value for parameter <var>$1</var>: $2.

Unrecognised {{PLURAL:$3|value|values}} for parameter <var>$1</var>: $2.

A unique identifier for networks assigned to a region and further to organisations like governments and ISPs

Serialisation format used for <var>$1difftotext</var> and expected for output of content.

Unrecognised value for parameter "$1": $2.

Configuration for and customisations to Wikibase that are specific to wikidata.org

The client is not authorised to request an authorisation code using this method.

Or you can specific a global licence below that will be applied to all items in the batch upload. This value can be a free text value or a MediaWiki template. If this field has a value in it then any metadata value mapped to the permission parameter will be ignored.

Allows usage of OAuth 1.0a and OAuth 2.0 for API authorisation

Adds an [[Special:Petition|includable page]] to collect signatures, and for authorised users to [[Special:PetitionData|download signatures]] as a CSV file

Request a licence form

Unrecognised {{PLURAL:$4|value|values}} for parameter "$1": $3

Gives the additional CSS classes (e.g. link colours) used for links to this page if they were to appear on the page named by <var>$1linkcontext</var>.

The authorisation server is currently unable to handle the request due to a temporary overloading or maintenance of the server.

The authorisation headers in your request are for a different user

Choose a title for the userbox, add text (or an image) and colour to the left and right side, and press create! It's that easy!

Developers should use the form below to request a token for a new OAuth 2.0 client (see the [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:OAuth extension documentation] for more details). After submitting this form, you will receive a token that your application will use to identify itself to MediaWiki. Depending on what capabilities you request, an OAuth administrator might need to approve your application before it can be authorised by other users.

A few recommendations and remarks:
* Try to use as few scopes as possible. Avoid scopes that are not actually needed now.
* Versions are of the form "major.minor.release" (the last two being optional) and increase as scope changes are needed.
* You can use a project ID to restrict the consumer to a single project on this site (use "*" for all projects).

Literal data field for a quantity that relates to some kind of well-defined unit. The actual unit goes in the data values that is entered.
* amount – implicit part of the string (mapping of unit prefix is unclear)
* unit – implicit part of the string that defaults to "1" (mapping to standardising body is unclear)
* upperbound - quantity's upper bound
* lowerbound - quantity's lower bound

The context title to use when determining extra CSS classes (e.g. link colours) when <var>$1prop</var> contains <var>linkclasses</var>.

''If you wish to use the '''Wikimedia logo''', you may [[Special:Contact/requestlicense|request a trademark licence]].''

Get the item for page "<var>Berlin</var>" on the site "<var>enwiki</var>" after normalising the title from "<var>berlin</var>"

Input to MediaWiki should be NFC-normalised UTF-8. MediaWiki may attempt to convert other input, but this may cause some operations (such as [[Special:ApiHelp/edit|edits]] with MD5 checks) to fail.

Parameters that take multiple values are normally submitted with the values separated using the pipe character, e.g. <kbd>param=value1|value2</kbd> or <kbd>param=value1%7Cvalue2</kbd>. If a value must contain the pipe character, use U+001F (Unit Separator) as the separator ''and'' prefix the value with U+001F, e.g. <kbd>param=%1Fvalue1%1Fvalue2</kbd>.

Some parameter types in API requests need further explanation:

Deleting CSS page on {{GENDER:$1|user}} request due to deployment of [[mw:Special:MyLanguage/Help:Extension:GlobalCssJs]]

Deleting JavaScript page on {{GENDER:$1|user}} request due to deployment of [[mw:Special:MyLanguage/Help:Extension:GlobalCssJs]]

The authorisation headers in your request are for a user that does not exist here