<strong>The tag "$1" is still active, and will continue to be applied in the future.</strong> To stop this from happening, go to the place(s) where the tag is set to be applied, and disable it there.

The tag "$1" is not allowed to be manually applied.

Using the form below will rename a page, moving all of its history to the new name.
The old title will become a redirect page to the new title.
You can update redirects that point to the original title automatically.
If you choose not to, be sure to check for [[Special:DoubleRedirects|double]] or [[Special:BrokenRedirects|broken redirects]].
You are responsible for making sure that links continue to point where they are supposed to go.

Note that the page will <strong>not</strong> be moved if there is already a page at the new title, unless the latter is a redirect and has no past edit history.
This means that you can rename a page back to where it was renamed from if you make a mistake, and you cannot overwrite an existing page.

<strong>Note:</strong>
This can be a drastic and unexpected change for a popular page;
please be sure you understand the consequences of this before proceeding.

Using the form below will rename a page, moving all of its history to the new name.
The old title will become a redirect page to the new title.
Be sure to check for [[Special:DoubleRedirects|double]] or [[Special:BrokenRedirects|broken redirects]].
You are responsible for making sure that links continue to point where they are supposed to go.

Note that the page will <strong>not</strong> be moved if there is already a page at the new title, unless it is a redirect and has no past edit history.
This means that you can rename a page back to where it was renamed from if you make a mistake, and you cannot overwrite an existing page.

<strong>Note:</strong>
This can be a drastic and unexpected change for a popular page;
please be sure you understand the consequences of this before proceeding.

The following {{PLURAL:$2|tag is|tags are}} not allowed to be manually applied: $1

The tag "$1" is applied to more than $2 {{PLURAL:$2|revision|revisions}}, which means it cannot be deleted.

This action is <strong>irreversible</strong> and <strong>cannot be undone</strong>, not even by database administrators. Be certain this is the tag you mean to delete.

"It" refers to a tag.

This is the second paragraph (not always shown) of an explanation to tell users what they are about to do. The first paragraph is probably {{msg-mw|tags-delete-explanation-initial}}.

Parameters:
* $1 - the code name of the tag that is about to be deleted
* $2 - the number of places the tag is used. The value is the sum of (revisions + log entries) where the tag is used.

Other administrators will still be able to access the hidden content and to undelete it, unless additional restrictions are set.

Whether the tag is still being applied.

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

Enter the institution the course belongs to and the year in which it is active.

It is possible to restore all Semantic MediaWiki data based on the current contents of the wiki.
This can be useful to repair broken data or to refresh the data if the internal format has changed due to some software upgrade.
The update is executed page by page and will not be completed immediately.
The following shows if an update is in progress and allows you to start or stop updates (unless this feature was disabled by the site administrator).

 #<!-- leave this line exactly as it is --> <pre>
# This message lets you configure the settings of the "more like this" feature.
# 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:
#  * min_doc_freq (integer): Minimum number of documents (per shard) that need a term for it to be considered.
#  * max_doc_freq (integer): Maximum number of documents (per shard) that have a term for it to be considered.
#                  High frequency terms are generally "stop words".
#  * max_query_terms (integer): Maximum number of terms to be considered. This value is limited to $wgCirrusSearchMoreLikeThisMaxQueryTermsLimit (100).
#  * min_term_freq (integer): Minimum number of times the term appears in the input to doc to be considered. For small fields (title) this value should be 1.
#  * minimum_should_match (percentage -100% to 100%, or integer number of terms): The percentage of terms to match on. Defaults to 30%.
#  * min_word_len (integer): Minimal length of a term to be considered. Defaults to 0.
#  * max_word_len (integer): The maximum word length above which words will be ignored. Defaults to unbounded (0).
#  * fields (comma separated list of values): These are the fields to use. Allowed fields are title, text, auxiliary_text, opening_text, headings and all.
#  * use_fields (true|false) : Tell the "more like this" query to use only the field data. Defaults to false: the system will extract the content of the text field to build the query.
# Examples of good lines:
# min_doc_freq:2
# max_doc_freq:20000
# max_query_terms:25
# min_term_freq:2
# minimum_should_match:30%
# min_word_len:2
# max_word_len:40
# fields:text,opening_text
# use_fields:true
# </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 "more like this" feature.
# 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:
#  * min_doc_freq (integer): Minimum number of documents (per shard) that need a term for it to be considered.
#  * max_doc_freq (integer): Maximum number of documents (per shard) that have a term for it to be considered.
#                  High frequency terms are generally "stop words".
#  * max_query_terms (integer): Maximum number of terms to be considered. This value is limited to $wgCirrusSearchMoreLikeThisMaxQueryTermsLimit (100).
#  * min_term_freq (integer): Minimum number of times the term appears in the input to doc to be considered. For small fields (title) this value should be 1.
#  * minimum_should_match (percentage -100% to 100%, or integer number of terms): The percentage of terms to match on. Defaults to 30%.
#  * min_word_len (integer): Minimal length of a term to be considered. Defaults to 0.
#  * max_word_len (integer): The maximum word length above which words will be ignored. Defaults to unbounded (0).
#  * fields (comma separated list of values): These are the fields to use. Allowed fields are title, text, auxiliary_text, opening_text, headings and all.
#  * use_fields (true|false) : Tell the "more like this" query to use only the field data. Defaults to false: the system will extract the content of the text field to build the query.
# Examples of good lines:
# min_doc_freq:2
# max_doc_freq:20000
# max_query_terms:25
# min_term_freq:2
# minimum_should_match:30%
# min_word_len:2
# max_word_len:40
# fields:text,opening_text
# use_fields:true
# </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 -->

  #<!-- 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 -->

The tag "$1" is not allowed to be manually added.

The tag "$1" is not allowed to be removed.

This special page allows you to move pages which are marked for translation.
The move action will not be instant, because many pages will need to be moved.
While the pages are being moved, it is not possible to interact with the pages in question.
Failures will be logged in the [[Special:Log/pagetranslation|page translation log]] and they need to be repaired by hand.

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.

Tag to create, delete, activate or deactivate. For tag creation, the tag must not exist. For tag deletion, the tag must exist. For tag activation, the tag must exist and not be in use by an extension. For tag deactivation, the tag must be currently active and manually defined.

The database is currently locked to new entries and other modifications, probably for routine database maintenance, after which it will be back to normal.

The system administrator who locked it offered this explanation: $1

The database is currently locked to new entries and other modifications, probably for routine database maintenance, after which it will be back to normal. The administrator who locked it offered this explanation: $1

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.