Manual:Administrators/mnw

Administrators are wiki users who are members of the "sysop" user group. The wiki software has few features which are only accessible to these users, but they are quite important.

ပရေင်မင်မွဲ
Administrators can edit protected pages and have the ability to protect and unprotect pages from editing and moving.

Versions of edit protection are:


 * Semi-protection: protection of a page against editing by an unregistered user.
 * Full protection: protection of a page against editing by a non-admin.
 * Cascading protection (&rarr; see demo):
 * in combination with full protection: protecting a page against editing by a non-admin, but also protecting images embedded on the page, provided that they are on the same site (not on Commons), and  also applying the same protection to transcluded pages for as long as they remain transcluded in the page (thus it works recursively).
 * Prior to MediaWiki 1.23, cascade protection did not apply to the targets of file redirects, if the redirect was listed on the protected page (T25542).
 * Cascading protection in combination with semi-protection does not make sense and should be avoided (see T10796); applies full protection to transcluded pages for as long as they remain transcluded in the page (again recursively).
 * Move protection is protection of a page against moving by a non-admin.


 * Procedure :
 * To protect a page, click the more dropdown menu and choose the "protect" option (or add  to the URL address bar). In the monobook skin, the shortcut alt+= can alternatively be used. This will lead to a confirmation screen with two menus and a checkbox. In the menu, the administrator can choose to protect the page from editing by unregistered users or all users. Similarly, the page can be protected from moves by either unregistered users (although this seems standard anyway) or all users (the system automatically adds the same level of protection to moves as it does to edits, but the protection level can be changed by checking the "Unlock move permissions" checkbox). Cascading protection is enabled by checking a separate checkbox. Enter the reason for page protection in the box and press "confirm". This will be logged.
 * To unprotect a page, click the unprotect tab. This will bring up the exact page as above, only this time the two menus will already be selected. Unprotection only involves selecting "(default)" under the "Edits" menu and pressing confirm. A reason for unprotection should be given as well. This action will likewise be logged.


 * Notes :
 * MediaWiki namespace: Pages in MediaWiki namespace can only be edited by users with  user right (by default, administrators and interface administrators). Since MediaWiki 1.32, JavaScript and CSS pages in MediaWiki namespace can only be edited by users with both   and (respectively)   or   user right (by default, interface administrators). These restriction is independent of the protection levels of these pages; these pages may still be protected individually.
 * Edit or view source: Depending on the status of the user and the status of the page, a user is provided an edit link or a link to just view the wikitext. After pressing edit on a fully protected page, an administrator is presented a warning at the top of the page informing about this page status. Also, the view source link may sometimes replace an edit link when the user is blocked.
 * Images: Protecting an image is mostly the same as protecting a page (see above). When the protect tab is clicked on the image description page, both the page and the image are protected. The image description page will be protected, and non-sysops will not be able to revert the image to an earlier version, or upload a new version over it.
 * Cascading protection of an important page is a crude measure, mainly for emergencies. If a template has to be protected just because it is transcluded in an important page, while it is also used elsewhere, it is better to make a copy for the transclusion in the important page, and use the other copy elsewhere. When this care is taken it makes little difference whether we use the automatic cascading protection or "manual cascading protection", i.e., protect the special copy of the template in the ordinary way. Initially, the main application of cascading protection is therefore the protection against creation, by transcluding non-existing pages on a page specially prepared for this purpose, like Meta:Protected against recreation. Protection of a non-existing page was not possible directly (an attempt would have given the message ""), but as of MediaWiki 1.13 this is now possible. Additionally, there is a known bug, which causes "view source" to show, even if the user has permission to edit the page with cascading protection.
 * Abuse filters: Additionally, if the AbuseFilter extension has been enabled, access to or viewing certain parts of the interface as well as modification of the interface is restricted to administrators.


 * Configuration :
 * which actions can be restricted via the protection interface is determined by the setting.
 * which permissions can be required via the protection interface is determined by the setting.

Deletion

 * See also: 

Administrators can delete pages and their history, and can view and restore deleted pages and their history. They can also delete images, which can be undeleted as normal.


 * Procedure :
 * To delete a page, click the delete link on the page that is to be deleted. (You may also add ?action=delete to the URL address bar). If an administrator is using the monobook skin, the shortcut alt+d can alternatively be used. This will bring up a new page asking for a confirmation that the page should be deleted, as well as an explanation of the deletion. A message should be typed into the input box to explain the deletion to other users. After the page has been deleted, it might have an existing talk page which should be deleted as well. Any links that point to the deleted page should be removed or corrected—whichever is the most appropriate action.
 * Pages can be undeleted for as long as they are in the archive. This archive is occasionally lost in database crashes. If a page has not been recreated since it was deleted, there will be a message on the page indicating how many deleted revisions there are. Clicking on this (or the undelete tab) will bring up a page displaying all the deleted revisions which can each be looked at separately. To undelete a page, click the restore button which appears on the confirmation page; this will restore all deleted revisions by default. Undeletion occurs as soon as the button is clicked, and will be logged just like deletions; if some revisions are not restored, the log will record how many were restored.  If a page already exists but an administrator wants to restore previous revisions, the administrator must go to the page history. There will be a link to undelete as described above.


 * Notes :
 * Delete revisions
 * Delete article revisions
 * Delete article revisions for the first time: To delete/keep just one or more revisions from the history, delete the article normally, then begin the undeletion procedure. Before clicking the "Restore" button, check the revisions you want to restore—all others will remain deleted.
 * Delete article revisions not for the first time: if the article already contains previously deleted revisions, be sure to follow Selective deletion on Wikipedia.
 * Delete image revisions: To delete one version of an image, click the (del) link beside that version under the "File history" heading. The most recent version cannot be deleted without deleting all previous versions.
 * Merge edit histories: the edit histories of two articles may be merged into one. To merge histories, delete the page where all the histories are supposed to be restored. Move the other page to the page just deleted, and then restore all the deleted revisions. This cannot be manually undone, and it is very difficult to split edit histories.
 * Split an edit history: To split an edit history, manually delete all revisions, then restore those belonging to one article (which may be difficult to recognize). Move the undeleted page to a new title to split off those revisions. Restore the revisions belonging to the deleted page (now a redirect), then revert to a the penultimate revision (before the redirect).

Rollback
Any user can revert a page by going back through the page's history. Administrators have a rollback button to expedite the process. To revert the edits of one user to the last version by the previous editor, click rollback on the page history, the user contribution list, or on the diff page. This can be used to revert edits from multiple vandalism attempts. The reversion will be marked as a minor edit and given an automatic edit summary based on the contents of Revertpage.

Sysops (and other users with right "MediaWiki:Right-markbotedits") can hide edits (typically, vandalism) from the Recent Changes page. To do this, add  to the end of the url used to access a user's contributions. For example,. When the rollback links on the contributions list are clicked, both the revert and the original edit that you are reverting will be hidden from the default Recentchanges display. This mechanism uses the marker originally added to keep massive bot edits from flooding recentchanges, hence the "bot". These changes will be hidden from recent changes unless you click the "bots" link to set. The edits are not hidden from contribs, history, watchlist, etc. The edits remain in the database and are not removed, but they no longer flood Recentchanges. The aim of this feature is to reduce the annoyance factor of a flood vandal with relatively little effort.

Block and unblock

 *  See . 

Making sysops
There is a simple interface (Special:Userrights) for granting a specific username 'sysop' status or (in MediaWiki 1.11) granting and revoking membership to groups with all associated user rights - a user with 'Bureaucrat' status has the rights to do to this. The initial user created by the installer should have 'Bureaucrat' rights.

Older versions of MediaWiki before 1.11 required you to manipulate the database records within MySQL in order to grant users certain rights.

Signed-in privileges
Users with ordinary access, including visitors who haven't "signed in", can still do many things, including the most important: editing pages and helping with maintenance tasks. But only signed-up users can upload files or rename pages.