Everything Food & Drink:Page Protection

From: Everything Food & Drink.org
Jump to: navigation, search
Request for page protection or page "un-protection" can be made HERE
Fully protected
Fully protected

Semi-protected
Semi-protected

Template protected
Template protected

Create protected
Create protected

Move protected
Move protected

Upload protected
Upload protected

Indefinite  protected
Indefinite protected

Author protected
Author protected

Staff protected
Staff protected

Administrators are able to protect a page to restrict editing or moving of that page, and remove such protection. Protection can be indefinite, or expire after a specified time.

  • Full protection prevents editing by everyone except administrators. Fully protected media files cannot be overwritten by new uploads.
  • Semi-protection prevents editing by unregistered contributors and contributors with accounts which are not autoconfirmed.
  • Move protection protects the page solely from moves.
  • Template protection
  • Creation protection prevents a page (normally a previously deleted one) from being recreated (also known as "salting").
  • Upload protection protects the file from reupload, does not protect the file page from editing.
  • Author protection prevents page access (page can be viewed) by anyone except the page author.
  • Staff protection

Any type of protection or unprotection may be requested at Requests for page protection. Changes to a fully protected page should be proposed on the corresponding talk page, and carried out if they are uncontroversial or if there is consensus for them.

Except in the case of Founder actions (see below), administrators may unprotect a page if the reason for its protection no longer applies, a reasonable period has elapsed, and there is no consensus that continued protection is necessary. Contacting the administrator who originally protected the page is advised in unclear circumstances. A log of protections and unprotections is available at Special:Log/protect.

Content disputes

On pages that are experiencing edit warring, temporary full protection can force the parties to discuss their edits on the talk page, where they can reach consensus. Isolated incidents of edit warring, and persistent edit warring by particular users, may be better addressed by blocking, so as not to prevent normal editing of the page by others.

Policy shortcut:
EFD:PREFER

When protecting a page because of a content dispute, administrators normally protect the current version, except where the current version contains content that clearly violates content policies, such as vandalism, copyright violations, or defamation of living persons. Since protecting the most current version sometimes rewards edit warring by establishing a contentious revision, administrators may also revert to an old version of the page predating the edit war if such a clear point exists. Pages that are protected because of content disputes should not be edited except to make changes which are uncontroversial or for which there is clear consensus (see above).

Administrators should not protect or unprotect a page to further their own position in a content dispute.

Vandalism

Policy shortcut:
EFD:NO-PREEMPT

Pre-emptive full protection of articles is contrary to the open nature of Everything Food & Drink. Brief periods of full protection are used in rare cases when a large number of autoconfirmed accounts are used to make a sustained vandalism attack on an article. Persistent vandalism, or the possibility of future vandalism for highly trafficked articles, rarely provides a basis for full-protection. Semi-protection is used for articles that have a pattern of heavy sustained vandalism.

Types of protection

Full protection

Padlock-red.svg
Policy shortcuts:
EFD:FULL
EFD:REDLOCK

A fully protected page can be edited only by administrators. The protection may be for a specified time, such as 7 or 14 days, or may be indefinite. The "Edit" tab for a protected page is replaced by a "View source" tab, where users can view and copy, but not edit, the wikitext of that page. Administrators still have an edit tab, but the edit box is shaded red with a warning above it.

Any modification to a fully protected page should be proposed on its talk page (or in another appropriate forum). After consensus has been established for the change, or if the change is uncontroversial, any administrator may make the necessary edits to the protected page. To draw administrators' attention to a request for an edit to a protected page, place the {{editprotected}} template on the talk page.

All requests are submitted at EFD:Requests for page protection.

Semi-protection

Padlock.svg
Policy shortcuts:
EFD:SEMI
EFD:GOLDLOCK

Semi-protection prevents edits from anonymous users (IP addresses), as well as edits from any account that is not autoconfirmed (is at least four days old and has ten or more edits to Wikipedia) or confirmed. Such users can request edits to a semi-protected page by proposing them on its talk page, using the {{Edit semi-protected}} template if necessary to gain attention. They may also request the confirmed userright by visiting Requests for permissions.

Administrators may apply indefinite semi-protection to pages which are subject to heavy and persistent vandalism or violations of content policy. Semi-protection should not be used as a pre-emptive measure against vandalism that has not yet occurred, nor should it be used solely to prevent editing by anonymous and newly registered users.

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) when blocking individual users is not a feasible option.
  • Subject to edit-warring where all parties involved are anonymous or new editors (i.e., in cases in which full-protection would otherwise be applied). This does not apply when autoconfirmed users are involved.
  • Article discussion pages, when they have been subject to persistent disruption. Such protection should be used sparingly because it prevents anonymous and newly registered users from participating in discussions. A page and its talk page should not both be protected at the same time.
  • Talk pages of blocked IP addresses that are being used for continued inappropriate editing, including repeated abuse of the {{unblock}} template, or continued uncivil or offensive remarks. The protection should be timed so as to not exceed the length of the block. Although administrators may also choose to change the block settings to block the user from editing their talk page instead, since there is no need to synchronize the block period with the page protection time period with this method.


Template protection

Zebra padlock
Policy shortcuts:
EFD:TEMP-P
EFD:TEMP-PRO
EFD:ZEBRALOCK

A template-protected page can be edited only by administrators or users in the Template editors group. This protection level may only be used on sensitive and high-risk templates, and possibly in rarer cases where pages in other namespaces become transcluded to a very high degree.

This is a new protection level[1] that replaces full protection on pages that are merely protected due to high transclusion rates, rather than content disputes. It should only be used on templates whose risk factor would have otherwise warranted full protection. It should not be used on less risky templates on the grounds that the template editor user right exists.

Create protection

Padlock-skyblue-plus.svg
Policy shortcuts:
EFD:SALT
EFD:BLUELOCK

Administrators can prevent the creation of a page through the protection interface. This is useful for articles that have been deleted but repeatedly recreated by an editor. Such protection is case-sensitive. A list of protected titles may be found at Special:Protectedtitles (see also historical lists).

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 more appropriate content should contact an administrator or use the deletion review process.

Move protection

Padlock-olive-arrow.svg
Policy shortcuts:
EFD:MOVP
EFD:GREENLOCK

Move-protected pages cannot be moved to a new title except by a confirmed user or 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.

Fully protected pages are also move-protected.

As with full protection, administrators should avoid favoring one name over another, and protection should not be considered an endorsement of the current name. An obvious exception to this rule is when pages are protected due to page-move vandalism.

Upload protection

Padlock-purple-uparrow.svg
Policy shortcut:
EFD:PURPLELOCK

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.

As with full protection, administrators should avoid favoring one file version over another, and protection should not be considered an endorsement of the current file version. An obvious exception to this rule is when files are protected due to upload vandalism.

Indefinite protection

Padlock-red-inf.svg
Policy shortcut:
EFD:REDLOCK

Some areas of the Everything Food & Drink project are permanently protected by the MediaWiki software. The MediaWiki namespace, which defines parts of the site interface, is fully protected; it is impossible for administrators to remove this protection. In addition, user CSS and JavaScript pages, such as User:Example/monobook.css and User:Example/cologneblue.js, are automatically fully protected. Only accounts that are associated with these pages or administrators are able to edit them. This protection applies to any user subpage with a ".css" or ".js" extension, whether an equivalent MediaWiki skin exists or not. Administrators may modify these pages, for example, to remove a user script that has been used in an inappropriate way.

In addition to the hard-coded protection, the following are usually permanently protected:

Cascading protection

Shortcuts:
EFD:CASCADE
EFD:CASCADING

Cascading protection fully protects a page, and extends that full protection automatically to any page that is transcluded onto the protected page, whether directly or indirectly. This includes templates, images and other media that are hosted on Everything Food & Drink project. Files stored onMyWiki (project repository) will not be protected by cascading protection, and need to be temporarily protected at MyWiki. Cascading protection:

  • 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 semi-protected pages as it represents a security flaw. See Bugzilla:8796 for more information.
  • Is not instantaneous; it may be several hours before it takes effect. See Bugzilla:18483 for more information.

Author protect

On MyWiki, GargoyleWiki and SupportWiki, confirmed and autoconfirmed users

User pages

Shortcut:
EFD:UPROT

User pages and subpages are sometimes protected at the user's request, or if there is evidence of vandalism or disruption. User talk pages are rarely protected, and are semi-protected for short durations only in the most severe cases of vandalism from IP users.

Users whose talk page is semi-protected for lengthy or indefinite periods of time should have an unprotected user talk subpage linked conspicuously from their main talk page to allow good faith comments from non-autoconfirmed users.

Staff/Office

Padlock-blue-X.png


Protection by namespace

Talk pages

Modifications to a protected page can be proposed on its talk page (or at another appropriate forum) for discussion. Administrators can make changes to the protected article reflecting consensus. Placing the {{Edit protected}} template on the talk page will draw the attention of administrators for implementing uncontroversial changes.

Talk pages are not usually protected, and are only semi-protected for a limited duration in the most severe cases of vandalism.

User talk pages

User talk pages are rarely protected, and are semi-protected for short durations only in the most severe cases of vandalism from IP users. Users whose talk pages are semi-protected should have an unprotected user talk subpage linked conspicuously from their main talk page to allow good faith comments from non-autoconfirmed users.

A user's request to have his or her own talk page protected is not a sufficient rationale to protect the page.

Blocked users' user talk pages

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 {{unblock}} template, re-blocking the user without talk page access should be preferred over protection. If the user has been indefinitely blocked from editing the talk page, they should be informed of off-wiki ways to appeal their block, such as the UTRS tool interface or ban appeals subcommittee of the Arbitration Committee.

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

Policy shortcuts:
WP:UPROT
WP:UPPROT

User pages and subpages can be protected by simple request from the user; this does not apply to the main user talk page. This is common for retired users and talk page archives.

Deceased users

In the event of the confirmed death of a user, the user's user page and userspace (but not user talk pages), 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 particularly vulnerable to vandalism, as vandalism to the template may introduce vandalism to hundreds of other pages. Therefore, they are frequently semi- or fully protected based on the degree of visibility, type of use, content, and other factors.

Semi and fully 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 a protected template. Only manually add {{pp-template}} to protected templates that don't use {{documentation}} (mostly the stub and flag templates).

Cascading protection should generally not be applied directly to templates, as it will not protect transclusions inside Template:Tag 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 full set of subtemplates is transcluded whenever the main template is trancluded, transclude the main template on Wikipedia:Cascade-protected items or a similar page.
  • 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 (which can, however, be overridden by account creators).

Sandboxes

Wikipedia:Sandbox and other sandboxes should also not ordinarily be protected since their purpose is to let new users test and experiment with wiki syntax. These pages are automatically cleaned every 12 hours, although they are frequently overwritten by other testing users much faster than that. Those who do use the sandboxes for malicious purposes, or to violate policies such as no personal attacks, civility, and copyrights, should instead be warned and/or blocked.

Retired users

Retired users may have their user pages protected upon request. Talk pages of retired editors are not usually protected except with limited duration to deal with vandalism. A user's request to have his or her own talk page protected due to retirement is not a sufficient rationale to protect the page.

Blocked users' user pages

Blocked users' user pages and user talk pages should not ordinarily be protected, as this interferes with the user's ability to contest their block through the normal process. In extreme cases of abuse, such as abuse of the {{unblock}} template, the talk page may be protected for a short time to prevent abusive editing. When required, it should be implemented for a brief period which should not exceed the length of the block, whichever is shorter. Consider disabling the user's talk page access via the block feature instead. In cases where the user has been blocked indefinitely, they should be informed of off-wiki ways to appeal their block, such as the unblock-en-l mailing list or ban appeals subcommittee of the Arbitration Committee. Confirmed socks of registered users should be dealt with in accordance with Wikipedia:Sockpuppetry; their pages are not normally protected.

Author protection

Pages Mac.png
Policy shortcuts:
EFD:AUTHPROT
EFD:AUTH

Not available on this wiki ( until I can figure a way to disable it in NS_MAIN ) however it is available at Everything Food & Drink's sister sites. This type of protection has no place in recipes or cocktail pages. It is available on the sister sites as mainspace is not defined to certain area's or subjects. Author protection is just that the page is protected from editing and/or moving to the author of the page. It is implemented by Extension:AuthorProtect where the subdomains are more utilitarian and developer based usage allows such protection. This allows page authors to protect pages from non-authors on a page-by-page basis. Authors with the 'authorprotect' permission Autoconfirmed users by default, will gain a protect tab on pages they author that gives them access to this interface. Because logs and anonymous users don't mix very well (as with the fact that all anonymous users share the same user id), anonymous users are unable to use this extension regardless of if they have the 'authorprotect' right or not. Administrators and oversight have the ability to to access any author protected page for obvious maintenance and liability reasons.

Web sourced files

Web sourced files uploaded to MyWiki are NOT eligable for {{authorprotec}}. These files are downloaded from a website therefore are not the uploader's images to author protect. Web sourced files can be {{semiprotec}} to protect from vandalism. Web sourced file talk pages will not be edit protected, this is to insure anyone to be able to leave any messages about the file, These files can be semi - move protected or fully - move protected upon request.

Founder protection

The death.svg
Policy shortcuts:
EFD:FDRPROT
EFD:FLOCK

If you need access to a founder protected page just leave a note on my (Talk)

  1. ^ Created October 2013 as a result of Wikipedia:Requests for comment/Template editor user right‎