Handbuch:$wgRestrictionLevels

From mediawiki.org
This page is a translated version of the page Manual:$wgRestrictionLevels and the translation is 35% complete.
Zugang: $wgRestrictionLevels
Einstellung der Gruppenberechtigungen zum Bearbeiten von Seiten
Eingeführt in Version:1.6.0 (r12207)
Entfernt in Version:weiterhin vorhanden
Erlaubte Werte:(Array von Strings)
Standardwert:[ '', 'autoconfirmed', 'sysop' ]

Details

This variable contains a list of permission keys that can be selected for each restriction type on the "page protection" page (action=protect). 'autoconfirmed' haben alle registrierten Benutzer, wenn $wgAutoConfirmAge und $wgAutoConfirmCount standardmäßig auf 0 eingestellt sind.

$wgRestrictionLevels holds a list of user permissions/rights, not user groups. If you need to, you can make up your own permission and then assign it to the different user groups as required. Zum Beispiel:

# 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;
'sysop' and 'autoconfirmed' are actually user groups rather than user rights, but are allowed for backwards compatibility. They should be mapped to 'editprotected' and 'editsemiprotected' respectively when comparing against user rights.

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 .

Caveats

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.

Siehe auch