RuneScape Wiki
No edit summary
(→‎Full protection: doesn't apply to us)
Line 12: Line 12:
 
== Full protection ==
 
== Full protection ==
   
*Protecting highly vandalised pages, such as the [[Main Page]] on large wikis.
 
 
*Maintaining the integrity of the [[:Image:Wiki.png|site's logo]] and [[:Image:Favicon.ico|favicon]].
 
*Maintaining the integrity of the [[:Image:Wiki.png|site's logo]] and [[:Image:Favicon.ico|favicon]].
 
*Protecting the interface and system messages in the [[Help:MediaWiki namespace|MediaWiki namespace]] (these are protected automatically)
 
*Protecting the interface and system messages in the [[Help:MediaWiki namespace|MediaWiki namespace]] (these are protected automatically)

Revision as of 17:59, 11 November 2007

Administrators can protect pages and unprotect pages. Protection of a page or image means that a non-admin cannot modify it.

The majority of pages on the wiki should remain publicly editable, and not protected. Pages may, however, be temporarily or permanently protected for legal reasons (for example, license texts should not be changed) or in cases of extreme vandalism or edit warring.

There are two kinds of protection:

  • Full protection disables editing for everyone except other administrators.
  • Semi-protection disables editing from IP addresses and accounts less than four days old.

All protections and unprotections are automatically logged in the protection log.

Full protection

  • Maintaining the integrity of the site's logo and favicon.
  • Protecting the interface and system messages in the MediaWiki namespace (these are protected automatically)
  • Deleted pages that are continually recreated. An example would be walking rocks.
  • Pages that are subject to an ongoing edit war.
  • Talk pages of blocked users, if they abuse the ability to appeal their block.

Semi-protection

Indefinite semi-protection may be used for:

  • The Main Page and all templates on it.
  • User pages when requested by the user.

Temporary semi-protection may be used for:

  • Articles, talk pages, and images that are persistently vandalized by multiple users.

There is no need to protect personal .css and .js pages like user/monobook.css or user/cologneblue.js. Only the accounts associated with these pages (and admins) are able to edit them. (For more information on using these pages, see the help page on Central.)

Unprotection

Any administrator may unprotect any page after a reasonable period has lapsed, particularly a few days.

Rules

  1. Do not protect pages preemptively. Only protect when there is persistent vandalism coming from many IPs/accounts, or there is an ongoing edit war that does not appear to be cooling down.
  2. Do not edit a temporarily protected page except to add a notice explaining the page is protected.
  3. Do not protect a page you are involved in an edit dispute over. Admin powers are not editor privileges - admins should only act as servants to the user community at large.
  4. Avoid favoring one version of the article over another, unless one version is vandalism.
  5. Temporarily protected pages should not be left protected for very long.
  6. Talk pages and user talk pages are not protected except in extreme circumstances.
  7. The protection of a page on any particular version is not meant to express support for that version and requests should therefore not be made that the protected version be reverted to a different one.