منتخب السعودية لكرة القدم

هذه المقالة تحوي الكثير من المعلومات وتمثل أحدى أفضل مقالات اللاموسوعة وعليه فقد تم إختيارها كمقالة مختارة

Wikipedia:Protection policy From Wikipedia, the free encyclopedia Page semi-protected "WP:PP" redirects here. You may be looking for Wikipedia:Requests for page protection, Wikipedia:Lists of protected pages, Wikipedia:Perennial proposals or WikiProject Parliamentary Procedure. "WP:PROTECT" redirects here. You may be looking for Wikipedia:Child protection or Wikipedia:WikiProject Protected areas. Green check.svg This page documents an English Wikipedia policy, a widely accepted standard that all editors must normally follow. Changes made to it should reflect consensus. Shortcuts: WP:PP WP:PROTECT Enforcement policies Administrators Banning policy Blocking policy Protection policy v t e Gold padlock Fully protected Pink padlock Template-protected Silver padlock Semi-protected Blue padlock Create protected Green padlock Move protected Purple padlock Upload protected White padlock Pending changes protected (level 1) Orange padlock Pending changes protected (level 2) Red padlock Permanently protected Black padlock Protected by Office Wikipedia is built around the principle that anyone can edit it, and it therefore aims to have as many of its pages as possible open for public editing, so that anyone can add material and correct errors. However, in particular circumstances, because of a specifically identified likelihood of damage resulting if editing is left open, some individual pages may need to be subject to technical restrictions (often only temporary) on who is permitted to modify them. The placing of such restrictions on pages is called protection. Protection can be applied to or removed from pages by Wikipedia's administrators, although any user may request these actions. Protection can be indefinite, or expire after a specified time period. The most commonly encountered types of protection are full protection, which means that a page can be modified only by administrators, and semi-protection, which means that a page can be modified only by users who are logged in and whose accounts have been confirmed (any account is automatically confirmed if it is at least four days old and has made at least ten edits or posts). Other forms of protection are detailed below. Protected pages are normally marked with a small padlock symbol in the top corner; different color padlocks represent different protection types, as shown in the images at the right. Template:Pp-protected is usually used to display the padlock. Positioning the mouse pointer over the padlock symbol produces an informational tooltip which says "This article is (semi-)protected." If قالب:Pp-protected's reason parameter is specified, the tooltip also says why the page is protected. If the expiry parameter is specified, the tooltip says for what duration the page is protected. This policy explains in detail the protection types and procedures for page protection and unprotection, and the reasons for which protection should and should not be applied. Contents 1 Overview of types of protection 2 Types of protection 2.1 Full protection 2.1.1 Content disputes 2.1.2 Vandalism 2.1.3 "History only" review 2.1.4 Protected generic image names 2.2 Template protection 2.3 Semi-protection 2.3.1 Guidance for administrators 2.4 Creation protection 2.5 Move protection 2.6 Upload protection 2.7 Pending changes protection 2.7.1 When to apply pending changes protection 2.8 Permanent protection 2.9 Office actions 2.10 Cascading protection 2.11 Comparison table 3 Protection by namespace 3.1 Talk pages 3.1.1 User talk pages 3.1.1.1 Blocked users 3.2 User pages 3.2.1 Deceased users 3.3 Protection of templates 3.4 Sandboxes 4 Available templates 5 See also 6 Notes Overview of types of protection The following technical options are available to administrators for protecting pages: 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 that are not confirmed. Creation protection prevents a page (normally a previously deleted one) from being recreated (also known as "salting"). Move protection protects the page solely from renaming/moving. Upload protection prevents new versions of a file from being uploaded except by administrators, but it does not prevent editing the file's description page. Pending-changes 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 administrator. Any type of protection or unprotection may be requested at Wikipedia:Requests for page protection. Changes to a fully protected page should be proposed on the corresponding talk page, and carried out by an administrator if they are uncontroversial or if there is consensus for them. Except in the case of office actions (see below) or pages in the MediaWiki namespace (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. Types of protection Full protection Gold padlock Policy shortcuts: WP:FPP WP:FULL WP:FULL-PRO WP:GOLDLOCK A fully protected page can be edited or moved only by administrators. The protection may be for a specified time or may be indefinite. Modifications to a fully 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. 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: WP: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 positions in content disputes. Vandalism Policy shortcut: WP:NO-PREEMPT Pre-emptive full protection of articles is contrary to the open nature of Wikipedia. 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, such as Jesus, that have a pattern of heavy sustained vandalism. "History only" review If a deleted page is undergoing deletion review, only administrators are normally capable of viewing the former content of the page. If they feel it would benefit the discussion to allow other users to view the page content, administrators may restore the page, blank it or replace the contents with قالب:TempUndelete or a similar notice, and fully protect the page to prevent further editing. The previous contents of the page are then accessible to non-admins via the page history. Protected generic image names Generic image names such as File:map.jpg or File:Photo.jpg are tagged with قالب:Protected generic image name and fully protected to prevent new versions being uploaded. Template protection Pink padlock Policy shortcuts: WP:TEMP-P WP:TEMP-PRO WP:TPROT WP:PINKLOCK Main page: Wikipedia:Template editor 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 high-risk templates and modules, 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 – the existence of the right should not result in more templates becoming uneditable for the general editor population. Semi-protection Silver padlock Policy shortcuts: WP:S-P WP:SPP WP:SEMI WP:SEMI-PRO WP:SILVERLOCK See also: Wikipedia:Rough guide to semi-protection Semi-protection prevents edits from unregistered users (IP addresses), as well as edits from any account that is not autoconfirmed (is at least four days old and has at least ten 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. If the page in question and its talk page are both protected please make your edit request at Wikipedia:Request for edit instead. New users may also request the confirmed user right by visiting Requests for permissions. 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, nor should it be used 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) when blocking individual users is not a feasible option. Subject to edit-warring where 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 vandalism or edit-warring where unregistered editors are engaging in IP-hopping by using different computers, obtaining new addresses by using dynamic IP allocation, or other address changing schemes such as IP address spoofing. Article discussion pages, when 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 edit, to 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 reblocked with talk page editing disallowed. When required, or when reblocking without talk page editing allowed is unsuccessful, protection should be implemented for only a brief period, and not exceeding the duration of the block. Today's featured article may be semi-protected just like any other article. But since this 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 Blue padlock Policy shortcuts: WP:SALT WP:PDP WP: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. 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 (look for one who was previously involved) or use the deletion review process. There are two levels of creation protection that can be applied to pages. One version is similar to semi-protection which allows autoconfirmed editors to create the page. The other version is similar to full protection which allows only administrators to create the page. Move protection Green padlock Policy shortcuts: WP:MOVP WP:MOVE-PRO WP:GREENLOCK 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 protected pages are also move-protected. As with full protection, protection because of editwarring 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. Upload protection Purple padlock Policy shortcuts: WP:UPLOAD-P WP: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. Pending changes protection Further information: Wikipedia:Pending changes Policy shortcuts: WP:PCPP WP:WHITELOCK WP:ORANGELOCK White padlock Orange padlock Pending changes protection is a tool used to suppress vandalism and certain other persistent problems, while allowing all users to continue to submit edits. Pending changes protection can be used as an alternative to semi-protection to allow unregistered and new users to edit pages, while keeping the edits hidden to most readers until they are accepted by a reviewer. When a page under pending changes protection is edited by an unregistered (IP addresses) editor or a new user, the edit is not directly visible to the majority of Wikipedia readers, until it is reviewed and accepted by an editor with the reviewer right. Pending changes are visible in the page history, where they are marked as pending review. The latest accepted revision is displayed to the general public. Logged-in users see the latest revision of the page, with all changes 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. Both logged-in users and anonymous users who click the "edit this page" tab may edit the latest version as usual. If there are pending changes awaiting review, there will be a dropdown box next to the article title, pointing to the pending changes. For more details, see Help:Pending changes. Reviewing of pending changes should be resolved within reasonable time limits. Backlog management should be coordinated at a community level. 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 only be used in cases of severe long-term disruption. Only what is known as "Pending changes level 1" should be used, which is labeled "Require review for revisions from new and unregistered users". Pending changes level 2, or "Require review for revisions from everyone except Reviewers", should not be used at this time per WP:PC2012/RfC 1. Removal of pending changes protection can be requested of any administrator, or at requests for unprotection. The reviewing process is described in detail at reviewing. Permanent protection Red padlock Policy shortcuts: WP:PPINDEF WP:PERM-PRO WP:REDLOCK Some areas of Wikipedia 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. 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 hard-coded protection, the following are usually permanently protected: Pages that are very visible, such as the Main Page or File:Wiki.png. Pages that should not be modified for copyright or legal reasons, such as the general disclaimer or the local copy of the site copyright license. Pages that are very frequently transcluded, such as {{[[Template:{{{1}}}|{{{1}}}]]}} or قالب:Ambox, 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 for more information. Files are indefinitely move-protected, though file movers and administrators may still move them. Office actions Black padlock Policy shortcuts: WP:WMF-P WP:WMF-PRO WP:BLACKLOCK As outlined at Wikipedia:Office actions, pages may be protected by Wikimedia Foundation staff in response to issues such as copyright or libel. Such actions override community consensus. Administrators should not edit or unprotect such pages without permission from Wikimedia Foundation staff. A list of pages under the scrutiny of the Wikimedia Foundation can be found here. Cascading protection Shortcuts: WP:CASCADE WP:CASCADING "WP:CASCADE" redirects here. You may be also looking for Wikipedia:Cascading style sheets. 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 English Wikipedia. Files stored on Commons will not be protected by cascading protection, and need to be temporarily uploaded to English Wikipedia or protected at Commons. 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. Should generally not be applied directly to templates, as it will not protect transclusions inside

منتخب السعودية لكرة القدم

معلومات عامة
أسم الدلع	الأخضر السعودي