وِکیٖپیٖڈیا:رٲچھؠ حِکمَتہِ عَملی - وِکیٖپیٖڈیا

وِکیٖپیٖڈیا:رٲچھؠ حِکمَتہِ عَملی - وِکیٖپیٖڈیا
مَوادَس کُن گٔژھِو
وِکیٖپیٖڈیا پؠٹھٕ، اَکھ آزاد اِنسایکلوپیٖڈیا
یہ صَفہٕ چھُ اَکھ وِکیٖپیٖڈیا
حِکمَتہِ عَملی
بَیان کران۔
یہٕ چھِ اَکھ مٔعیار واضِح کران یوس تمامَن صٲرفَن پَزِ مانُن۔ کانٛہہ بُنیٲدؠ اؠڑِٹ یَتھ صَفَس کرنہٕ برونٛہہ گژھہِ گۄڑٕ
کَتھ باتھ صَفَس
یا
حِکمَتہِ عَملی اؠسَمبَلی
پیٹھ بَحَث کٔرُن تہٕ بَرادری ہٕنٛز راے پرژھِن۔
مُختصَر وَتہٕ
وپ:رحع
وپ:رٲچھؠ
یہٕ صَفہٕ ایکِس نَظرٕ مَنٛز:
ییٚلہِ زَن وِکیٖپیٖڈیا چھُ اَکھ یَلہٕ اِنسایکلوپیٖڈیا چھُ یَتھ ہَر کانٛہہ ہؠکہٕ اؠڑِٹ کٔرِتھ، کُنہِ ساتھ چھُ اؠڑِٹ کَرنَس پؠٹھ رُکاوَٹھ ضروٗری صَفہٕ فضول اؠڑِٹو نِش بَچاونہٕ خٲطرٕ.
تُہی چھا صحیح جاے؟
This page is for documenting and explaining the English Wikipedia
policy
on page protection.
Are you trying to request protection of a page?
Request page protection
Are you trying to request removal of a page's protection?
Request a change in page protection level
Do you want to request an edit be made to a protected page?
Create an edit request
Do you need to report persistent vandalism or spam to an
administrator
File a vandalism report
Do you need to report an inappropriate username or an account with a username that blatantly violates Wikipedia's
username policy
File a username report
Are you currently blocked from editing Wikipedia and wish to request an unblock? You can resolve this matter by
appealing your block
Do you need to report an
edit war
or
three-revert rule
violation to an administrator?
File an edit war report
Do you need to report or discuss a policy violation or behavioral issue (such as an evasion of a
block
, abuse of tools, or other incidents) on Wikipedia that requires administrator intervention?
File an incident report
لاگوٗو حِکمَتہِ عَملی
اِنتِظامؠ
بُلاک حِکمَتہِ عَملی
رٲچھؠ حِکمَتہِ عَملی
مُکَمل رٲچھؠ
سۄنہٕ قُلُف
اِنٹَرفیس رٲچھؠ
وَزُل قُلُف
نؠصف رٲچھؠ
سوٗرؠ قُلُف
تَخلیٖق رٲچھؠ
آسمأنؠ قُلُف
پَکناوَن رٲچھؠ
سَبٕز
اپلوڈ رٲچھؠ
Purplelock
وِکیٖمیٖڈیا اِدارٕ رٲچھؠ
کرٛہُن قُلُف
آبشار رٲچھؠ
فیروزی قُلُف
کینٛہہ حالاتَن مَنٛز چھِ صَفَن یِوان
رٲچھؠ
یا قُلُف کَرنہٕ تاکِہ صِرف کانٛہہ خَصوصی رُکُن چمٲژ ہێکہِ اَتھ اؠڑِٹ کٔرِتھ. صَفَن چھِ یِوان رٲچھؠ کَرنہٕ ییٚلہِ صَفہٕ کِس مَوادَس نوقصان آسِہ واتناونہٕ یِوان یُس باقٕے تَدبیٖرو مِثال
بُلاک
سٲتؠ آسہِ نہٕ بَچاونہٕ یِوان. نَتہٕ چھُ وِکیٖپیٖڈیا اَکھ آزاد انسائيكلوپيڈيا یَتھ مَنٛز ہَر کانٛہہ ہیٚکہِ اؠڈِٹ کٔرِتھ مَگر کُنہِ ساتھ چھِ یِم عَملہ ضَروری. یہِ
حِکمَتہِ عَملی چھِ صَفَن رٲچھؠ کَرنَس تہٕ رٲچھؠ ییٚلہِ تَراونَس پؠٹھ کینٛہہ اصول واضَع کَران.
رٲچھؠ یا قُلُف کَرُن چھُ اَکھ تَکنیٖکی رُکاوَٹھ یُس خألی اَکھ
اِنتِظٲمؠ
ہێکہِ اَنجام دیتھ ہَلاکِہ باقٕے رُکُن ہیکَن
|رأچھؠ دَرخاست
دِیتھ. رأچھؠ ہێکہِ یا
لامہدود
آسِتھ یا کُنِہٕ مَخصوص وَقتَس خٲطرٕ. رٲچھؠ یا قُلُف کَرنَس چھِ واریاہ قسٕم یِم بونہٕ کَن چھِ. رٲچھؠ کَرنہٕ پَتہٕ تِہ چھُ صَفُک کوڈ یِوان وُچھنہٕ.
رأچھؠ کٔرِتھ صَفَس چھُ اَکھ لۄکُٹ کقُلُف نِشان آسان یُس
pp-protected
فرما سٲتی یِوان چھُ.
رٲچھؠ قٕسم
مُختصَر وتھ
وپ:رقف
The following technical options are available to administrators for protecting different actions to pages:
اؠڑِٹ رٲچھؠ
چھُ صَفَن اؠڑِٹ کَرنہٕ نِش رُکاوَٹھ اَنان.
پَکناوَن رٲچھؠ
چھُ صَفَن پَکناونہٕ یا ناو بَدلانہٕ نِش رُکاوَٹھ اَنان.
تَخلیٖق رٲچھؠ
چھُ صَفہٕ تَخلیٖق کَرنہٕ نِش رُکاوَٹھ اَنان.
اَپلوڈ رٲچھؠ
چھُ فَیِل تَخلیٖق کَرنہٕ نِش رُکاوَٹھ اَنان.
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 editors 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 editors and editors 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. In most cases it should not be a protection level of first resort, and should be used where semi-protection has proven to be ineffective. 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
cascading protection
) may be requested at
Wikipedia:Requests for page protection
. Changes to a fully protected page should be proposed on the corresponding
talk page
, then carried out by an administrator if they are uncontroversial or there is
consensus
for them.
Except in the case of
office actions
(see
below
),
Arbitration Committee
remedies, 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. Editors desiring the unprotection of a page should, in the first instance, ask the administrator who applied the protection unless the administrator is inactive or no longer an administrator; thereafter, requests may be made at
Requests for unprotection
. Note that such requests will normally be declined if the protecting administrator is active and was not consulted first. A log of protections and unprotections is available at
Special:Log/protect
فرما:Protection table
مُکمَل رٲچھؠ
مُختصَر وتھ
وپ: مر
أکِس مُکمَل رٲچھؠ کٔرِتھ صَفَس چھُ صرِف اَکھ
اِنتِظأمؠ
اؠڑِٹ یا پَکنٲوِتھ. باقٕے رُکُن چھِ نہٕ یِم کامِہ اَنجام ہیکان دِیتھ. مُکمَل رٲچھؠ چھِ یا کُنہِ وَقتَس یا لامہَدوٗد وَقتَس یِوان کَرنہٕ.
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 fully-protected
template on the talk page will draw the attention of administrators for implementing uncontroversial changes.
Content disputes
یہِ تہِ ؤچُھو:
Wikipedia:Stable version
"WP:PREFER" redirects here. For what title name should be preferred, see
Wikipedia:Disambiguation §
Primary topic
While content disputes and
edit warring
may be addressed with user
blocks
issued by
uninvolved
administrators, allowing normal page editing by other editors at the same time, the protection policy provides an alternative approach as administrators have the discretion to temporarily fully protect an article to end an ongoing edit war. This approach may better suit multi-party disputes and contentious content, as it makes talk page
consensus
a requirement for implementation of
requested edits
مُختصَر وتھ
WP:PREFER
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
vandalism
copyright violations
defamation
, or
poor-quality coverage of living people
. Administrators are deemed to remain uninvolved when exercising discretion on whether to apply protection to the current version of an article, or to an older,
stable
, or pre-edit-war version.
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
involved
and must not use their advanced permissions to further their own positions. When involved in a dispute, it is almost always wisest to respect the editing policies that bind all editors and call for input from an uninvolved administrator, rather than to invite controversy by acting unilaterally.
Vandalism
مُختصَر وَتہٕ
WP:NO-PREEMPT
WP:PREEMPTIVE
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
مُختصَر وتھ
WP:PPDRV
If a deleted page is going through
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
Temporarily undeleted
template 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 history
Protected generic file names
Generic file names such as
File:Photo.jpg
File:Map.jpg
, and
File:Sound.wav
are fully protected to prevent new versions being uploaded. Furthermore,
File:Map.jpg
and
File:Sound.wav
are
salted
Permanent protection
Icon for pages that can be edited only by interface administrators
مُختصَر وَتہٕ
WP:PPINDEF
WP:REDLOCK
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
MediaWiki:common.js
are further restricted to
interface administrators
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
general disclaimer
or the
local copy of the site copyright license
Pages that are very frequently
transcluded
, such as
tl
or
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
for more information.
Semi-protection
یہِ تہِ ؤچُھو:
Wikipedia:Rough guide to semi-protection
مُختصَر وَتہٕ
WP:SEMI
WP:SILVERLOCK
Semi-protected pages cannot be edited by
unregistered users
IP addresses
), as well as accounts that are not
autoconfirmed
(accounts that are at least four days old and have made at least ten edits to Wikipedia) or
confirmed
. Semi-protection is useful when there is a significant amount of disruption or
vandalism
from new or unregistered users, or to prevent
sockpuppets
of blocked or banned users from editing, especially when it occurs on
biographies of living persons
who have had a recent high level of media interest. An alternative to semi-protection is
pending changes
, which is sometimes favored when an article is being vandalized regularly, but otherwise receives a low amount of editing.
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:Requests for page protection
instead. New users may also request the confirmed user right at
Wikipedia:Requests for permissions/Confirmed
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
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.
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 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 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
تَخلیٖق رٲچھؠ
مُختصَر وتھ
وپ:تر
Administrators can prevent the creation of pages. This level of protection is useful for pages that have been
deleted
but repeatedly recreated. Such protection is case-sensitive. There are several levels of creation protection that can be applied to pages, identical to the levels for edit protection. 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
". Editors 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,
or full. Due to the implementation of
ACPERM
, non-confirmed editors cannot create pages in
mainspace
; thus, semi-creation protection should be rare, used only for protection of pages outside of mainspace.
While creation-protection is usually permanent, temporary creation protection may be applied if a page is repeatedly recreated by a single user (or
sockpuppets
of that user, if applicable).
Move protection
مُختصَر وَتہٕ
WP:MOVP
WP:GREENLOCK
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
files
are implicitly move-protected; only
file movers
and administrators can rename files.
Upload protection
مُختصَر وَتہٕ
WP:UPLOAD-P
WP:PURPLELOCK
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. It 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. (e.g.,
As with full edit protection, administrators should avoid favoring one version over another, and protection should not be considered an endorsement of the current version. An exception to this rule is when they are protected due to upload vandalism.
Office actions
یہِ تہِ ؤچُھو:
Wikipedia:Office actions
مُختصَر وَتہٕ
WP:WMF-PRO
WP:BLACKLOCK
As outlined in
Meta-Wiki: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
"WP:CASCADE" redirects here. You may be also looking for
Help:Cascading Style Sheets
or
Wikipedia:Cascade-protected items
مُختصَر وَتہٕ
WP:CASCADE
WP:TURQUOISELOCK
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 the English Wikipedia. Files stored on Commons are
not
protected by any other wiki's cascading protection and, if they are to be protected, must be either temporarily uploaded to the English Wikipedia or explicitly protected at Commons (whether manually or through cascading protection there). When operational,
KrinkleBot
cascade-protects Commons files transcluded at
Wikipedia:Main Page/Tomorrow
Wikipedia:Main Page/Commons media protection
and
Main Page
. As the bot's response time varies, media should
not
be transcluded on the main page (or its constituent templates) until after it has been protected. (This is particularly relevant to
Template:In the news
, for which upcoming images are not queued at
Wikipedia:Main Page/Tomorrow
.) 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 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 inside
includeonly
tags or transclusions that depend on template parameters, but
will
protect the
documentation subpage
فرما:Xref
, for alternatives.
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
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.
رٲچھؠ ناوجاے مُطٲبِق
مُختصَر وتھ
WP:PROTNS
Article talk pages
مُختصَر وتھ
WP:ATPROT
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 semi-protected only for a limited duration in the most severe cases of vandalism.
User talk pages
مُختصَر وتھ
WP:UTPROT
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
unblock
template, re-blocking the user with talk page access removed should be preferred over applying protection to the page. If the user has been blocked and with the ability to edit their user talk page disabled, they should be informed of this in a block notice, subsequent notice, or message, and it should include information and instructions for appealing their block off-wiki, such as through the
UTRS tool interface
or, as a last recourse,
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
مُختصَر وَتہٕ
WP:UPROT
WP:UPPROT
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
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.
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
یہِ تہِ ؤچُھو:
Wikipedia:Deceased Wikipedians/Guidelines
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
مُختصَر وتھ
WP:PTPROT
یہِ تہِ ؤچُھو:
Wikipedia:High-risk templates
and
Wikipedia:Template documentation
Highly visible templates
those used on a large number of pages or frequently substituted
are often edit protected based on the degree of visibility, type of use, content, and other considerations.
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
یہِ تہِ ؤچُھو:
Wikipedia:About the sandbox
Sandboxes should not ordinarily be protected since their purpose is to let new users test and experiment with
wiki syntax
. Most sandboxes are automatically cleaned every 12 hours, although they are frequently overwritten by other testing users. The
Wikipedia:Sandbox
is cleaned every hour. Those who use sandboxes for malicious purposes, or to violate policies such as
no personal attacks
civility
, or
copyrights
, should instead be warned and/or blocked.
دٕستِیاب فرما
The following templates may be added at the very top of a page to indicate that it is protected:
Protection templates
Edit
Move
Pending changes
Upload
Generic
pp
pp-protected
pp
pp-move
pp
pp-pc
pp
pp-upload
BLP
pp-blp
Dispute
pp-dispute
pp-move-dispute
Extended confirmed protection
pp-extended
pp-extended
Main Page
Image
pp-main-page
Office
pp-office
pp-reset
pp-office-dmca
pp-office
pp-reset
pp-office-dmca
pp-office
pp-reset
pp-office-dmca
Sockpuppetry
pp-sock
High-visibility
pp-template
Blocked user's talk
pp-usertalk
Vandalism
pp-vandalism
pp-move-vandalism
Talk page
permanently protected
temporarily protected
Long-term
pp-semi-indef
pp-move-indef
Module:Protection banner
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.
بیٚیہِ وُچھِو
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
Meta-Wiki:Protected pages considered harmful
Meta-Wiki:The Wrong Version
Wikipedia:Protection policy/Padlocks
نوٹ
حَوالہٕ غَلطی: Invalid

tag; no text was provided for refs named
ECPRFC2
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
فرما:New admin school
فرما:Wikipedia policies and guidelines
پؠٹھٕ اِستِمال کۄٚرمُت
زٲژ
Wikipedia semi-protected project pages
وِکیٖپیٖڈیا حِکمَتہِ عَملی
Wikipedia vandalism
Wikipedia page protection
صَفہٕ یِمَن مَنٛز حَوالہٕ غلطی چھِ
وِکیٖپیٖڈیا
رٲچھؠ حِکمَتہِ عَملی
نٔو موضوٗع