MediaWiki REL1_28
Go to the documentation of this file.
37 public function __construct( $permission, $errors = [] ) {
40 if ( $permission === null && !$errors ) {
41 throw new \InvalidArgumentException( __METHOD__ .
42 ': $permission and $errors cannot both be empty' );
43 }
45 $this->permission = $permission;
47 if ( !count( $errors ) ) {
48 $groups = array_map(
49 [ 'User', 'makeGroupLinkWiki' ],
50 User::getGroupsWithPermission( $this->permission )
51 );
53 if ( $groups ) {
54 $errors[] = [ 'badaccess-groups', $wgLang->commaList( $groups ), count( $groups ) ];
55 } else {
56 $errors[] = [ 'badaccess-group0' ];
57 }
58 }
60 $this->errors = $errors;
61 }
63 public function report() {
66 $wgOut->showPermissionsErrorPage( $this->errors, $this->permission );
67 $wgOut->output();
68 }
Definition Setup.php:816
An error page which can definitely be safely rendered using the OutputPage.
Show an error when a user tries to do something they do not have the necessary permissions for.
Output a report about the exception and takes care of formatting.
__construct( $permission, $errors=[])
when a variable name is used in a it is silently declared as a new local masking the global
Definition design.txt:95
this class mediates it Skin Encapsulates a look and feel for the wiki All of the functions that render HTML and make choices about how to render it are here and are called from various other places when and is meant to be subclassed with other skins that may override some of its functions The User object contains a reference to a and so rather than having a global skin object we just rely on the global User and get the skin with $wgUser and also has some character encoding functions and other locale stuff The current user interface language is instantiated as $wgLang
Definition design.txt:56
if the prop value should be in the metadata multi language array can modify can modify indexed by page_id indexed by prefixed DB keys can modify can modify can modify this should be populated with an alert message to that effect to be fed to an HTMLForm object and populate $result with the reason in the form of error messages should be plain text with no special etc to show that they re errors
Definition hooks.txt:1705
injection txt This is an overview of how MediaWiki makes use of dependency injection The design described here grew from the discussion of RFC T384 The term dependency this means that anything an object needs to operate should be injected from the the object itself should only know narrow no concrete implementation of the logic it relies on The requirement to inject everything typically results in an architecture that based on two main types of and essentially stateless service objects that use other service objects to operate on the value objects As of the beginning MediaWiki is only starting to use the DI approach Much of the code still relies on global state or direct resulting in a highly cyclical dependency which acts as the top level factory for services in MediaWiki which can be used to gain access to default instances of various services MediaWikiServices however also allows new services to be defined and default services to be redefined Services are defined or redefined by providing a callback the instantiator that will return a new instance of the service When it will create an instance of MediaWikiServices and populate it with the services defined in the files listed by thereby bootstrapping the DI framework Per $wgServiceWiringFiles lists includes ServiceWiring php
Definition injection.txt:37