MediaWiki  master
SkinFallback.php
Go to the documentation of this file.
1 <?php
12 class SkinFallback extends SkinTemplate {
13 
14  public $skinname = 'fallback';
15  public $template = SkinFallbackTemplate::class;
16 
17  public function getDefaultModules() {
18  $modules = parent::getDefaultModules();
19  $modules['styles']['skin'][] = 'mediawiki.skinning.interface';
20  return $modules;
21  }
22 
26  public function initPage( OutputPage $out ) {
27  parent::initPage( $out );
28  $out->enableClientCache( false );
29  }
30 }
$out
this hook is for auditing only or null if authentication failed before getting that far or null if we can t even determine that When $user is not it can be in the form of< username >< more info > e g for bot passwords intended to be added to log contexts Fields it might only if the login was with a bot password it is not rendered in wiki pages or galleries in category pages allow injecting custom HTML after the section Any uses of the hook need to handle escaping see BaseTemplate::getToolbox and BaseTemplate::makeListItem for details on the format of individual items inside of this array or by returning and letting standard HTTP rendering take place modifiable or by returning false and taking over the output $out
Definition: hooks.txt:773
$modules
$modules
Definition: HTMLFormElement.php:12
OutputPage\enableClientCache
enableClientCache( $state)
Use enableClientCache(false) to force it to send nocache headers.
Definition: OutputPage.php:2174
SkinTemplate
Base class for template-based skins.
Definition: SkinTemplate.php:38
SkinFallback
SkinTemplate class for the fallback skin.
Definition: SkinFallback.php:12
SkinFallback\initPage
initPage(OutputPage $out)
Definition: SkinFallback.php:26
php
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:35
class
you have access to all of the normal MediaWiki so you can get a DB use the etc For full docs on the Maintenance class
Definition: maintenance.txt:52