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). 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, an <code>Access-Control-Allow-Origin</code> header will be set.

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.

When accessing the API using a cross-domain AJAX request (CORS), use this to authenticate as the current SUL user. Use <kbd>[[Special:ApiHelp/centralauthtoken|action=centralauthtoken]]</kbd> on this wiki to retrieve the token, before making the CORS request. Each token may only be used once, and expires after 10 seconds. This should be included in any pre-flight request, and therefore should be included in the request URI (not the POST body).

The title of the article to link. If this parameter is an empty string or both linktitle and badges are not set, the link will be removed.

The MediaWiki template may have a <code>permission</code> parameter; when it does, an attempt to detect the copyright licence based on the metadata value can be made. GWToolset looks for Creative Commons URLs that match possible copyright licences; e.g., https://creativecommons.org/licenses/by-sa/3.0/ matches the MediaWiki licence template <code>{{tl|Template:Cc-by-sa-3.0}}</code>. If this checkbox is left unchecked, the raw metadata value for each item in the batch upload will be placed in the permission parameter.

The MediaWiki template may have a <code>permission</code> parameter. When it does, an attempt to detect the copyright license based on the metadata value can be made. GWToolset looks for Creative Commons URLs that match possible copyright licenses, e.g., https://creativecommons.org/licenses/by-sa/3.0/ matches the MediaWiki license template <code>{{tl|Template:Cc-by-sa-3.0}}</code>. If this box is left unchecked, the raw metadata value for each item in the batch upload will be placed in the permission parameter.

The IDs of items to be set as badges. They will replace the current ones. If this parameter is not set, the badges will not be changed

<div class="hlist plainlinks api-main-links">
* [[mw:API:Main_page|Documentation]]
* [[mw:API:FAQ|FAQ]]
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-api Mailing list]
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-api-announce API Announcements]
* [https://phabricator.wikimedia.org/maniphest/query/GebfyV4uCaLd/#R Bugs & requests]
</div>
<strong>Status:</strong> All features shown on this page should be working, but the API is still in active development, and may change at any time. Subscribe to [https://lists.wikimedia.org/pipermail/mediawiki-api-announce/ the mediawiki-api-announce mailing list] for notice of updates.

<strong>Erroneous requests:</strong> When erroneous requests are sent to the API, an HTTP header will be sent with the key "MediaWiki-API-Error" and then both the value of the header and the error code sent back will be set to the same value. For more information see [[mw:API:Errors_and_warnings|API: Errors and warnings]].

<strong>Testing:</strong> For ease of testing API requests, see [[Special:ApiSandbox]].

  #<!-- leave this line exactly as it is --> <pre>
# This message lets you configure the settings of the "Did you mean" suggestions.
# See also https://www.elastic.co/guide/en/elasticsearch/reference/current/search-suggesters-phrase.html
# Changes to this take effect immediately.
# The syntax is as follows:
#  * Everything from a "#" character to the end of the line is a comment.
#  * Every non-blank line is the setting name followed by a ":" character followed by the setting value
# The settings are :
#  * max_errors (integer): the maximum number of terms that will be considered misspelled in order to be corrected. 1 or 2.
#  * confidence (float): The confidence level defines a factor applied to the input phrases score which is used as a threshold for other suggestion candidates. Only candidates that score higher than the threshold will be included in the result. For instance a confidence level of 1.0 will only return suggestions that score higher than the input phrase. If set to 0.0 the best candidate are returned.
#  * min_doc_freq (float 0 to 1): The minimal threshold in number of documents a suggestion should appear in.
#                  High frequency terms are generally "stop words".
#  * max_term_freq (float 0 to 1): The maximum threshold in number of documents in which a term can exist in order to be included.
#  * prefix_length (integer): The minimal number of prefix characters that must match a term in order to be a suggestion.
#  * suggest_mode (missing, popular, always): The suggest mode controls the way suggestions are included.
# Examples of good lines:
# max_errors:2
# confidence:2.0
# max_term_freq:0.5
# min_doc_freq:0.01
# prefix_length:2
# suggest_mode:always
#
# </pre> <!-- leave this line exactly as it is -->

  #<!-- leave this line exactly as it is --> <pre>
# This message lets you configure the settings of the "Did you mean" suggestions.
# See also https://www.elastic.co/guide/en/elasticsearch/reference/current/search-suggesters-phrase.html
# Changes to this take effect immediately.
# The syntax is as follows:
#  * Everything from a "#" character to the end of the line is a comment.
#  * Every non-blank line is the setting name followed by a ":" character followed by the setting value
# The settings are :
#  * max_errors (integer): the maximum number of terms that will be considered misspelled in order to be corrected. 1 or 2.
#  * confidence (float): The confidence level defines a factor applied to the input phrases score which is used as a threshold for other suggestion candidates. Only candidates that score higher than the threshold will be included in the result. For instance a confidence level of 1.0 will only return suggestions that score higher than the input phrase. If set to 0.0 the best candidate are returned.
#  * min_doc_freq (float 0 to 1): The minimal threshold in number of documents a suggestion should appear in.
#                  High frequency terms are generally "stop words".
#  * max_term_freq (float 0 to 1): The maximum threshold in number of documents in which a term can exist in order to be included.
#  * prefix_length (integer): The minimal number of prefix characters that must match a term in order to be a suggestion.
#  * suggest_mode (missing, popular, always): The suggest mode controls the way suggestions are included.
# Examples of good lines:
# max_errors:2
# confidence:2.0
# max_term_freq:0.5
# min_doc_freq:0.01
# prefix_length:2
# suggest_mode:always
#
# </pre> <!-- leave this line exactly as it is -->

If set, a new entity will be created.
Set this to the type of the entity you want to create.
It is not allowed to have this set when <var>id</var> is also set.

{{Doc-important|Do not translate function name <code>unstrip</code>.}}
This error is shown when a parser extension tag such as <code><nowiki><pre></nowiki></code> includes a reference to itself in its own output.

The reference must be to the exact same invocation of the tag at the same location in the source, merely writing <code><nowiki><pre><pre></pre></pre></nowiki></code> will not do it.

This is usually impossible and unlikely to happen by accident, so translation is not essential.

"Unstrip" refers to the internal function of the parser, called "unstrip", which recursively puts the output of parser functions in the place of the parser function call and which would enter an infinite loop in the situation above.

See also:
*{{msg-mw|Parser-unstrip-recursion-limit}}

This checkbox allows you to re-upload media for an item that has already been uploaded to the wiki. If the item already exists because of one of your previous uploads, an additional media file will be added to the wiki. If someone else has already uploaded a new version of the media file, then your new upload will be ignored. If the media file does not yet exist in the wiki, it will be uploaded whether this checkbox is checked or not.

This is the text of a Special page. See example [[mw:Special:CentralAutoLogin/P3P]].

This provides an explanation for the [[:w:en:P3P|P3P]] hack that allows IE to set cookies. The text is technical and is only linked from a url in an http header response, so it is not something end users will generally find.

<strong>Congratulations!</strong>
You have installed MediaWiki.

The installer has generated a <code>LocalSettings.php</code> file.
It contains all your configuration.

You will need to download it and put it in the base of your wiki installation (the same directory as index.php). The download should have started automatically.

If the download was not offered, or if you cancelled it, you can restart the download by clicking the link below:

$3

<strong>Note:</strong> If you do not do this now, this generated configuration file will not be available to you later if you exit the installation without downloading it.

When that has been done, you can <strong>[$2 enter your wiki]</strong>.

If set, a new entity will be created.
Set this to the type of the entity you want to create.

Beim Zugriff auf die API mit einer Kreuz-Domain-AJAX-Anfrage (CORS) muss dies als entstehende Domäne festgelegt werden. Dies muss in jeder Vorfluganfrage mit eingeschlossen werden und deshalb ein Teil der Anfragen-URI sein (nicht des POST-Körpers).

Für authentifizierte Anfragen muss dies exakt einem der Ursprünge im Header <code>Origin</code> entsprechen, so dass es auf etwas wie <kbd>https://de.wikipedia.org</kbd> oder <kbd>https://meta.wikimedia.org</kbd> festgelegt werden muss. Falls dieser Parameter nicht mit dem Header <code>Origin</code> übereinstimmt, wird eine 403-Antwort zurückgegeben. Falls dieser Parameter mit dem Header <code>Origin</code> übereinstimmt und der Ursprung weißgelistet ist, werden die Header <code>Access-Control-Allow-Origin</code> und <code>Access-Control-Allow-Credentials</code> festgelegt.

Gib für nicht authentifizierte Anfragen den Wert <kbd>*</kbd> an. Dies verursacht, dass der Header <code>Access-Control-Allow-Origin</code> festgelegt wird, aber <code>Access-Control-Allow-Credentials</code> wird <code>false</code> sein und alle benutzerspezifischen Daten werden beschränkt.

The message appears in the Mediawiki code as follows:

 if ( $this->parsedUrl['scheme'] != 'http' ) {
$this->status->fatal( 'http-invalid-scheme', $this->parsedUrl['scheme'] );
 }

Siebrand think this has to do with allowing MediaWiki to fetch remote URLs, and in that not allowing anything but "http://" request. So if this for example is "irc://" or "https://", $1 would be "irc" or "https" respectively.

If 'scheme' is difficult to translate, then you could use 'prefix' instead.

Warning displayed during preview when editing a page if #incat parser function acted incorrectly (Acting incorrectly means acting as if page was not in category, but page actually is) . This can happen if someone does something like ''put this page in category foo only if its not in category foo'' or more generally when people include category links inside <code>#incat</code> functions. Compare this to {{msg-mw|pageincat-wrong-warn}}. Generally this error message can happen when support for checking actual categories in the preview is enabled (but the category functions still behave incorrectly), the other error message will be triggered when such support is disabled.

*$1 is the list of categories (in a localized comma separated list with the last two items separated by {{msg-mw|and}}. The individual category names will be italicized).
*$2 is how many categories

If set, the input must NOT match the regular expression to be valid. I.e. the regular expression is inverted.

The error message if a parameter to some parser function is not set. Parameters:
* $1 - parameter name. any one of the following: <code>url</code>, <code>data</code>, <code>filter</code>, <code>domain</code>, <code>db</code>, <code>from</code>

This message, assuming that the server of the website is located in the USA (like Wikimedia Commons), reminds the user that for the work to be considered in the public domain its copyright is required to be expired in the USA specifically, as being PD in the country of origin is not enough.

Templates that if contained on a page will raise or lower the score of the page in search results.  They must be specied Namespace:Template Name|<boost factor>%. You can translate the text, including "Leave this line exactly as it is". Some lines of this messages have one (1) leading space. 

This message will be shown with left-to-right direction, so when you are translating to a right-to-left language, you may want to test how it looks in left-to-right and add right-to-left marks as needed.

  #<!-- این بخش را دقیقا به همین صورت رها کنید --> <pre>
# This message lets you configure the settings of the "Did you mean" suggestions.
# See also https://www.elastic.co/guide/en/elasticsearch/reference/current/search-suggesters-phrase.html
# Changes to this take effect immediately.
# The syntax is as follows:
#  * Everything from a "#" character to the end of the line is a comment.
#  * Every non-blank line is the setting name followed by a ":" character followed by the setting value
# The settings are :
#  * max_errors (integer): the maximum number of terms that will be considered misspelled in order to be corrected. 1 or 2.
#  * confidence (float): The confidence level defines a factor applied to the input phrases score which is used as a threshold for other suggestion candidates. Only candidates that score higher than the threshold will be included in the result. For instance a confidence level of 1.0 will only return suggestions that score higher than the input phrase. If set to 0.0 the best candidate are returned.
#  * min_doc_freq (float 0 to 1): The minimal threshold in number of documents a suggestion should appear in.
#                  High frequency terms are generally "stop words".
#  * max_term_freq (float 0 to 1): The maximum threshold in number of documents in which a term can exist in order to be included.
#  * prefix_length (integer): The minimal number of prefix characters that must match a term in order to be a suggestion.
#  * suggest_mode (missing, popular, always): The suggest mode controls the way suggestions are included.
# Examples of good lines:
# max_errors:2
# confidence:2.0
# max_term_freq:0.5
# min_doc_freq:0.01
# prefix_length:2
# suggest_mode:always
#
# </pre> <!-- این بخش را دقیقا به همین صورت رها کنید -->

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>.