| アクセス権: $wgRestrictionLevels | |
|---|---|
| Set of permission keys that can be selected on the "page protection" page. | |
| 導入されたバージョン: | 1.6.0 (r12207) |
| 除去されたバージョン: | 使用中 |
| 許容される値: | (文字列の配列) |
| 既定値: | ['','autoconfirmed','sysop'] |
| その他の設定:アルファベット順 |機能順 | |
This variable contains a list of permission keys that can be selected for eachrestriction type on the "page protection" page (action=protect).'autoconfirmed' allows all registered users if$wgAutoConfirmAge and$wgAutoConfirmCount are 0.
$wgRestrictionLevels は、利用者グループではなく利用者権限を保持します。If you need to, you can make up your own permission and then assign it to the different user groups as required.例:
# add an additional protection level restricting edit/move/etc. to users with the "school-project" permission$wgRestrictionLevels[]='school-project';# give the "school-project" permission to users in the "students" and "teachers" groups$wgGroupPermissions['students']['school-project']=true;$wgGroupPermissions['teachers']['school-project']=true;# give the "school-project" permission to sysops (needed so sysops can apply this protection level to pages)$wgGroupPermissions['sysop']['school-project']=true;
If you add additional levels (e.g. 'docwriters'), you can set the "display name" seen in the user interface by creating a MediaWiki page like 'MediaWiki:Protect-level-docwriters'.
If you set a level higher than sysops, that is, protection from sysop editing, sysops cannot give a page that level of protection nor remove it, even with the 'protect' permission.
A user with the 'protect' permission still cannot protect a page that they can't edit, such as if defined as such by$wgNamespaceProtection.
Cascade protection is exempt from removing create protection.
If a user with the 'protect' permission has the permission to edit a page but it is protected so that they can't move it, the protection interface will offer to change the move-protection level so you will gain the capability to move that page.
The first one in the list is not the default one.