User:ArticleEditor404/sandbox
This page documents an English Wikipedia consensus. |
This page in a nutshell: While Wikipedia strives to be as open as possible, sometimes it is necessary to limit editing of certain pages in order to prevent disruptive edits . |
Are you in the right place?
If you need to make a request or report relating to a page protection, see the following pages:
|
状況によっては、特定の編集者グループによる変更からページを保護する必要がある場合があります。ブロックなどの他の手段では防ぐことができない特定の損傷イベントが特定された場合、ページは保護されます。それ以外の場合、ウィキペディアは誰でも編集できるという原則に基づいて構築されているため、誰でも資料を追加してエラーを修正できるように、できるだけ多くのページを公開編集できるようにすることを目指しています。このポリシーでは、ページの保護と保護解除の保護の種類と手順、および各保護を適用する必要がある場合と適用しない場合について詳しく説明しています。
保護は管理者によってのみ適用される技術的な制限ですが、どのユーザーも保護を要求できます。保護は無期限にすることも、指定した時間が経過すると期限切れになることもあります。さまざまなレベルの保護について以下に詳しく説明します。これらは、ページの編集、ページの移動、ページの作成、およびファイルのアップロードのアクションに適用できます。ページが編集から保護されている場合でも、ページのソースコードテキストはどのユーザーでも表示およびコピーできます。
保護されたページの右上には、通常ppで保護されたテンプレートによって追加される南京錠のアイコンが付いています。
Types of protection
The following technical options are available to administrators for protecting different actions to pages:
- Edit protection protects the page from being edited.
- Move protection protects the page from being moved or renamed.
- Creation protection prevents a page (normally a previously deleted one) from being created (also known as "salting").
- Upload protection prevents new versions of a file from being uploaded, but it does not prevent editing to the file's description page (unless edit protection is applied).
The following technical options are available to administrators for adding protection levels to the different actions to pages:
- Pending changes protection (only available for edit protection) means edits by unregistered and new contributors are not visible to readers who are not logged-in until the edits are approved by a reviewer or an administrator.
- Semi-protection prevents the action by unregistered contributors and contributors with accounts that are not confirmed.
- Extended confirmed protection, also known as 30/500 protection, prevents the action by users without 30 days' tenure and 500 edits on the English Wikipedia. It is applied to combat any form of disruption where semi-protection has proven to be ineffective. It should not be applied as a protection level of first resort. Its use is logged at the Administrators' noticeboard.
- Template protection prevents the action by everyone except template editors and administrators (who have this right as part of their toolset).
- Full protection prevents the action by everyone except administrators.
Any type of protection (with the exception of
Except in the case of
Unregistered or newly registered | Confirmed or autoconfirmed | Extended confirmed | Template editor | Admin | Interface admin | Appropriate for (See also: Wikipedia:Protection policy) | |
---|---|---|---|---|---|---|---|
No protection | Normal editing | The vast majority of pages. This is the default protection level. | |||||
Pending changes | All users can edit Edits by unregistered or new editors (and any subsequent edits by anyone) are hidden from readers who are not logged in, until reviewed by a pending changes reviewer or admin. Logged-in editors see all edits, whether accepted or not. |
Infrequently edited pages with high levels of vandalism, BLP violations, edit-warring, or other disruption from unregistered and new users.
| |||||
Semi | Cannot edit | Normal editing | Pages that have been persistently vandalized by anonymous and registered users. Some highly visible templates and modules. | ||||
Extended confirmed | Cannot edit | Normal editing* | Specific topic areas authorized by ArbCom, pages where semi-protection has failed, or high-risk templates where template protection would be too restrictive. | ||||
Template | Cannot edit | Normal editing | High-risk or very-frequently used templates and modules. Some high-risk pages outside of template space. | ||||
Full | Cannot edit | Normal editing | Pages with persistent disruption from extended confirmed accounts. Critical templates and modules. | ||||
Interface | Cannot edit | Normal editing | Scripts, stylesheets, and similar objects central to operation of the site or that are in other editors' user spaces. | ||||
* In order to edit through extended confirmed protection, a template editor must also be extended confirmed, but in practice this is almost always the case. Other modes of protection: |
Full protection
A fully protected page cannot be edited or moved by anyone except administrators. The protection may be for a specified time or may be indefinite.
Modifications to a fully protected page can be proposed on its
Content disputes
While content disputes and
When protecting a page because of a content dispute, administrators have a duty to avoid protecting a version that contains policy-violating content, such as
Protected pages may not be edited except to make changes that are uncontroversial or for which there is clear consensus. Editors convinced that the protected version of an article contains policy-violating content, or that protection has rewarded edit warring or disruption by establishing a contentious revision, may identify a stable version prior to the edit war and request reversion to that version. Before making such a request, editors should consider how independent editors might view the suggestion and recognize that continuing an edit war is grounds for being blocked.
Administrators who have made substantive content changes to an article are considered
Vandalism
Applying page protection as a preemptive measure is contrary to the open nature of Wikipedia and is generally not allowed if applied for these reasons. However, brief periods of an appropriate and reasonable protection level are allowed in situations where blatant vandalism or disruption is occurring by multiple users and at a level of frequency that requires its use in order to stop it. The duration of the protection should be set as short as possible, and the protection level should be set to the lowest restriction needed in order to stop the disruption while still allowing productive editors to make changes.
"History only" review
If a deleted page is going through
{{Temporarily undeleted}}
or a similar notice, and fully protect the page to prevent further editing. The previous contents of the page are then accessible to everyone via the page historyProtected generic file names
Generic file names such as File:Map.jpg, File:Photo.jpg, and File:Sound.wav are fully protected to prevent new versions being uploaded.
Permanent protection
Administrators cannot change or remove the protection for some areas on Wikipedia which are permanently protected by the MediaWiki software:
- Edits to the MediaWiki namespace, which defines parts of the site interface, are restricted to administrators.
- Edits to system-wide CSS and JavaScript pages such as interface administrators.
- Edits to system-wide CSS and JavaScript pages such as
- Edits to personal CSS and JavaScript pages such as User:Example/monobook.css and User:Example/cologneblue.js are restricted to the associated user and interface administrators. Interface administrators may edit these pages, for example, to remove a user script that has been used in an inappropriate way. Administrators may delete (but not edit or restore) these pages.
- Edits to personal JSON pages such as User:Example/data.json are restricted to the associated user and administrators.
In addition to hard-coded protection, the following are usually fully protected for an indefinite period of time:
- Pages that are very visible, such as the Main Page
- Pages that should not be modified for copyright or legal reasons, such as the local copy of the site copyright license.
- Pages that are very frequently tl}} orfor more information.
{{citation needed}}
, to prevent vandalism or denial of service attacks. This includes images or templates used in other highly visible or frequently transcluded pages. See Wikipedia:High-risk templates
Template protection
A template-protected page can be edited only by administrators or users in the Template editors group. This protection level should be used almost exclusively on
This is a protection level
Editors may request edits to a template-protected page by proposing them on its talk page, using the {{Edit template-protected}}
template if necessary to gain attention.
Semi-protection
Semi-protected pages cannot be edited by
Such users can request edits to a semi-protected page by proposing them on its talk page, using the {{
Guidance for administrators
Administrators may apply indefinite semi-protection to pages that are subject to heavy and persistent vandalism or violations of content policy (such as biographies of living persons, neutral point of view). Semi-protection should not be used as a preemptive measure against vandalism that has not yet occurred or to privilege registered users over unregistered users in (valid) content disputes.
In addition, administrators may apply temporary semi-protection on pages that are:
- Subject to significant but temporary vandalism or disruption (for example, due to media attention) if blocking individual users is not a feasible option.
- Subject to edit warring if all parties involved are unregistered or new editors (i.e. in cases in which full protection would otherwise be applied). This does not apply when autoconfirmed users are involved.
- Subject to dynamic IPallocation, or other address-changing schemes.
- Article discussion pages, if they have been subject to persistent disruption. Such protection should be used sparingly because it prevents unregistered and newly registered users from participating in discussions. A page and its talk page should not normally be protected at the same time. If a page and its talk page are both protected, the talk page should direct affected editors to Wikipedia:Request for editto ensure that no editor is entirely prevented from contributing.
- Protection should be used sparingly on the talk pages of blocked users, including IP addresses. Instead the user should be re-blocked with talk page editing disallowed. When required, or when re-blocking without talk page editing allowed is unsuccessful, protection should be implemented for only a brief period not exceeding the duration of the block.
Today's featured article may be semi-protected just like any other article. But since that article is subject to sudden spurts of vandalism during certain times of day, administrators should semi-protect it for brief periods in most instances. For the former guideline, see Wikipedia:Main Page featured article protection.
Creation protection (salting)
Administrators can prevent the creation of pages. This level of protection is useful for bad pages that have been
Pre-emptive restrictions on new article titles are instituted through the title blacklist system, which allows for more flexible protection with support for substrings and regular expressions.
Pages that have been creation-protected are sometimes referred to as "salted". Contributors wishing to re-create a salted title with appropriate content should either contact an administrator (preferably the protecting administrator), file a request at Wikipedia:Requests for page protection#Current requests for reduction in protection level, or use the deletion review process. To make a convincing case for re-creation, it is helpful to show a draft version of the intended article when filing a request.
Administrators should choose the appropriate level of create protection—autoconfirmed, extended-confirmed,
While creation-protection is usually permanent, temporary creation protection may be applied if a page is repeatedly recreated by a single user (or
Move protection
Move protected pages, or more technically, fully move-protected pages, cannot be moved to a new title except by an administrator. Move protection is commonly applied to:
- Pages subject to persistent page-move vandalism.
- Pages subject to a page-name dispute.
- Highly visible pages that have no reason to be moved, such as the administrators' noticeboard and articles selected as "Today's featured article" on the main page.
Fully edit-protected pages are also implicitly move-protected.
As with full edit protection, protection because of edit warring should not be considered an endorsement of the current name. When move protection is applied during a requested move discussion, the page should be protected at the location it was at when the move request was started.
All
Upload protection
Upload protected files, or more technically, fully upload-protected files, cannot be replaced with new versions except by an administrator. Upload protection does not protect file pages from editing. Upload protection may be applied by an administrator to:
- Files subject to persistent upload vandalism.
- Files subject to a dispute between editors.
- Files that should not be replaced, such as images used in the interface or transcluded to the main page.
- Files with common or generic names. (eg. File:Map.png)
As with full edit protection, administrators should avoid favoring one file version over another, and protection should not be considered an endorsement of the current file version. An exception to this rule is when files are protected due to upload vandalism.
Pending changes protection
Pending changes protection is a tool used to suppress
When a page under pending changes protection is edited by an
Pending changes are visible in the page history, where they are marked as pending review. Readers that are not logged in (the vast majority of readers) are shown the latest accepted version of the page; logged-in users see the latest version of the page, with all changes (reviewed or not) applied. When editors who are not reviewers make changes to an article with unreviewed pending changes, their edits are also marked as pending and are not visible to most readers.
A user who clicks "edit this page" is always, at that point, shown the latest version of the page for editing regardless of whether the user is logged in or not.
- If the editor is not logged in, their changes join any other changes to the article awaiting review – for the present they remain hidden from not-logged-in users. (This means that when the editor looks at the article after saving, the editor won't see the change made.)
- If the editor is logged in and a pending changes reviewer, and there are pending changes, the editor will be prompted to review the pending changes before editing – see Wikipedia:Pending changes.
- If the editor is logged in and not a pending changes reviewer, then ...
- If there are no unreviewed pending edits waiting, this editor's edits will be visible to everyone immediately; but
- If there are unreviewed pending edits waiting, then this editor's edits will be visible only to other logged-in users (including themself) immediately, but not to readers not logged in.
Reviewing of pending changes should be resolved within reasonable time limits.
When to apply pending changes protection
Pending changes may be used to protect articles against:
- Persistent vandalism
- Violations of the biographies of living persons policy
- Copyright violations
Pending changes protection should not be used as a preemptive measure against violations that have not yet occurred. Like semi-protection, PC protection should never be used in genuine content disputes, where there is a risk of placing a particular group of editors (unregistered users) at a disadvantage. Pending changes protection should not be used on articles with a very high edit rate, even if they meet the aforementioned criteria. Instead semi-protection should be considered.
In addition, administrators may apply temporary pending changes protection on pages that are subject to significant but temporary vandalism or disruption (for example, due to media attention) when blocking individual users is not a feasible option. As with other forms of protection, the time frame of the protection should be proportional to the problem. Indefinite PC protection should be used only in cases of severe long-term disruption.
Removal of pending changes protection can be requested of any administrator, or at
The reviewing process is described in detail at Wikipedia:Reviewing pending changes.
Extended confirmed protection
Extended confirmed protection, also known as 30/500 protection, only allows edits by editors with the extended confirmed user access level, granted automatically to registered users with at least 30 days tenure and 500 edits.
Where semi-protection has proven to be ineffective, administrators may use extended confirmed protection to combat disruption (such as
Until August 12, 2016,.
Users can request edits to an extended confirmed-protected page by proposing them on its talk page, using the {{Edit extended-protected}}
template if necessary to gain attention.
Office actions
As outlined in Meta:Office actions#Use of advanced rights by Foundation staff, pages may be protected by Wikimedia Foundation staff in response to issues such as copyright infringement or libel. Such actions override community consensus. Administrators should not edit or unprotect such pages without permission from Wikimedia Foundation staff.
Cascading protection
Cascading protection fully protects a page, and extends that full protection automatically to any page that is
- Should be used only to prevent vandalism when placed on particularly visible pages, such as the main page.
- Is available only for fully protected pages; it is disabled for lower levels of protection as it represents a security flaw. See Phabricator:T10796 for more information.
- Is not instantaneous; it may be several hours before it takes effect. See Phabricator:T20483 for more information.
- Should generally not be applied directly to templates or modules, as it will not protect transclusions insidebelow for alternatives.
<includeonly>
tags or transclusions that depend on template parameters, but will protect the documentation subpage. See the "Protection of templates" section
The list of cascading-protected pages can be found at Wikipedia:Cascade-protected items. Requests to add or remove cascading protection on a page should be made at Wikipedia talk:Cascade-protected items as an edit request.
Deprecated protection
Superprotect
Superprotect was a level of protection, allowing editing only by Wikimedia Foundation employees who are in the Staff global group. It was implemented on August 10, 2014 and used the same day to override community consensus regarding the use of the Media Viewer on the German Wikipedia's primary site JavaScript, common.js. It was never used on the English Wikipedia. On November 5, 2015, the WMF decided to remove superprotect from all Wikimedia wikis.
Cascading semi-protection
Cascading semi-protection was formerly possible, but it was disabled in 2007 after users noticed that non-administrators could fully protect any page by transcluding it onto the page to which cascading semi-protection had been applied by an administrator.
Pending changes protection level 2
Originally, two levels of pending changes protection existed, where level 2 required edits by all users who are not pending changes reviewers to be reviewed. Following a community discussion, level 2 was retired from the English Wikipedia in January 2017. It was suggested then that "Pending changes level 1" be referred to in the future as simply "Pending changes".[10]
Protection by namespace
Article talk pages
Modifications to a protected page can be proposed on its
Talk pages are not usually protected, and are semi-protected only for a limited duration in the most severe cases of vandalism.
User talk pages
User talk pages are rarely protected. However, protection may be applied if there is severe vandalism or abuse. Users whose talk pages are protected may wish to have an unprotected user talk subpage linked conspicuously from their main talk page to allow good-faith comments from users that the protection restricts editing from.
A user's request to have their own talk page protected is not a sufficient rationale by itself to protect the page, although requests may be considered if a reason is provided.
Blocked users
Blocked users' user talk pages should not ordinarily be protected, as this interferes with the user's ability to contest their block through the normal process. It also prevents others from being able to use the talk page to communicate with the blocked editor.
In extreme cases of abuse by the blocked user, such as abuse of the {{
When required, protection should be implemented for only a brief period, not exceeding the duration of the block.
Confirmed socks of registered users should be dealt with in accordance with Wikipedia:Sockpuppetry; their pages are not normally protected.
User pages
Base user pages (for example, the page User:Example, and not User:Example/subpage or User talk:Example) are automatically protected from creation or editing by unconfirmed accounts and anonymous IP users. An exception to this includes an unconfirmed registered account attempting to create or edit their own user page. IP editors and unconfirmed accounts are also unable to create or edit user pages that do not belong to a currently-registered account. This protection is enforced by an edit filter.[11] Users may opt-out of this protection by placing {{unlocked userpage}}
anywhere on their own user page.
User pages and subpages within their own user space may be protected upon a request from the user, as long as a need exists. Pages within the user space should not be automatically or pre-emptively protected without good reason or cause.[12][13] Requests for protection specifically at uncommon levels (such as template protection) may be granted if the user has expressed a genuine and realistic need.
When a filter is insufficient to stop user page vandalism, a user may choose to create a ".css" subpage (ex. User:Example/Userpage.css), copy all the contents of their user page onto the subpage, transclude the subpage by putting {{User:Example/Userpage.css}} on their user page, and then ask an administrator to fully protect their user page. Because user space pages that end in ".css", ".js", and ".json" are editable only by the user to which that user space belongs (and interface administrators), this will protect your user page from further vandalism.
Deceased users
In the event of the confirmed death of a user, the user's user page (but not the user talk page) should be fully protected.
Protection of templates
Highly visible templates, which are used on an extremely large number of pages or substituted with great frequency, are often semi-, template-, or fully-protected based on the degree of visibility, type of use, content, etc.
Protected templates should normally have the {{documentation}} template. It loads the unprotected /doc
page, so that non-admins and IP-users can edit the documentation, categories and interwiki links. It also automatically adds {{pp-template}} to protected templates, which displays a small padlock in the top right corner and categorizes the template as protected. Only manually add {{pp-template}} to protected templates that don't use {{documentation}} (mostly the flag templates).
Cascading protection should generally not be applied directly to templates, as it will not protect transclusions inside <includeonly>
tags or transclusions that depend on template parameters, but will protect the template's documentation subpage. Instead, consider any of the following:
- If the set of subtemplates is static (even if large), protect them using normal protection mechanisms.
- If the set of subtemplates is unbounded, use MediaWiki:Titleblacklist to protect all subtemplates using a particular naming format (as is done for editnotice templates and subtemplates of Template:TFA title).
Note: All editnotice templates (except those in userspace) are already protected via MediaWiki:Titleblacklist. They can be edited by admins, template editors and page movers only.
Sandboxes
Sandboxes should not ordinarily be protected since their purpose is to let new users test and experiment with
Available templates
The following templates may be added at the very top of a page to indicate that it is protected:
On redirect pages, use the {{Redirect category shell}} template, which automatically categorizes by protection level, below the redirect line. A protection template may also be added below the redirect line, but it will serve only to categorize the page, as it will not be visible on the page, and it will have to be manually removed when protection is removed.
See also
- MediaWiki:Protectedpagetext
- Special:Protectedpages
- Special:Protectedtitles
- Wikipedia:Edit lock
- Wikipedia:List of indefinitely protected pages
- Wikipedia:Requests for page protection
- Wikipedia:Rough guide to semi-protection
- Wikipedia:Make protection requests sparingly, an essay
- m:Protected pages considered harmful
- m:The Wrong Version
- Wikipedia:Protection policy/Padlocks
Notes
- ^ Created October 2013 as a result of Wikipedia:Requests for comment/Template editor user right
- ^ a b Wikipedia:Requests for comment/Extended confirmed protection policy 2
- ^ Wikipedia:Requests for comment/Extended confirmed protection policy
- ^ Wikipedia:Arbitration/Requests/Case/Palestine-Israel articles 4#ARBPIA General Sanctions (Note: This sanction was originally authorised in Wikipedia:Arbitration/Requests/Case/Palestine-Israel articles 3).
- ^ Arbitration motions regarding extended confirmed protection
- ^ Wikipedia:Village pump (proposals)/Archive 129#New usergroup with autopromotion to implement arbitration "30-500" bans as a page protection
- ^ AN discussion authorizing India-Pakistan general prohibition
- ^ Antisemitism in Poland: Motion (May 2020)
- ^ Wikipedia talk:Protection Policy discussion to remove manual posting requirement
- ^ VPR RfC to remove PC2
- ^ Please refer to Wikipedia:Requests for comment/Protect user pages by default and its talk page for community discussion related to a preventative measure for user pages.
- ^ Per discussion at Wikipedia talk:Protection policy/Archive 15#Own userspace pages protection policy, June 2013
- ^ Per discussion at Wikipedia:Administrators' noticeboard/Archive314#Protecting an editor's user page or user space per their request, September 2019