MediaWiki REL1_30
rebuildmessages.php
Go to the documentation of this file.
1<?php
24require_once __DIR__ . '/Maintenance.php';
25
32 public function __construct() {
33 parent::__construct();
34 $this->addDescription( 'Purge all language messages from the cache' );
35 }
36
37 public function execute() {
39 if ( $wgLocalDatabases ) {
40 $databases = $wgLocalDatabases;
41 } else {
42 $databases = [ $wgDBname ];
43 }
44
45 foreach ( $databases as $db ) {
46 $this->output( "Deleting message cache for {$db}... " );
47 $messageMemc->delete( "{$db}:messages" );
49 $messageMemc->delete( "{$db}:sidebar" );
50 }
51 $this->output( "Deleted\n" );
52 }
53 }
54}
55
56$maintClass = "RebuildMessages";
57require_once RUN_MAINTENANCE_IF_MAIN;
$wgLocalDatabases
Other wikis on this site, can be administered from a single developer account.
$wgEnableSidebarCache
If on, the sidebar navigation links are cached for users with the current language set.
Abstract maintenance class for quickly writing and churning out maintenance scripts with minimal effo...
addDescription( $text)
Set the description text.
Maintenance script that purges all languages from the message cache.
execute()
Do the actual work.
__construct()
Default constructor.
design txt This is a brief overview of the new design More thorough and up to date information is available on the documentation wiki at etc Handles the details of getting and saving to the user table of the and dealing with sessions and cookies OutputPage Encapsulates the entire HTML page that will be sent in response to any server request It is used by calling its functions to add in any and then calling output() to send it all. It could be easily changed to send incrementally if that becomes useful
globals will be eliminated from MediaWiki replaced by an application object which would be passed to constructors Whether that would be an convenient solution remains to be but certainly PHP makes such object oriented programming models easier than they were in previous versions For the time being MediaWiki programmers will have to work in an environment with some global context At the time of globals were initialised on startup by MediaWiki of these were configuration which are documented in DefaultSettings php There is no comprehensive documentation for the remaining however some of the most important ones are listed below They are typically initialised either in index php or in Setup php For a description of the see design txt $wgTitle Title object created from the request URL $wgOut OutputPage object for HTTP response $wgUser User object for the user associated with the current request $wgLang Language object selected by user preferences $wgContLang Language object associated with the wiki being viewed $wgParser Parser object Parser extensions register their hooks here $wgRequest WebRequest to get request data $messageMemc
Definition globals.txt:66
require_once RUN_MAINTENANCE_IF_MAIN
controlled by $wgMainCacheType controlled by $wgParserCacheType controlled by $wgMessageCacheType If you set CACHE_NONE to one of the three control default value for MediaWiki still create a but requests to it are no ops and we always fall through to the database If the cache daemon can t be it should also disable itself fairly smoothly By $wgMemc is used but when it is $parserMemc or $messageMemc this is mentioned $wgDBname
$maintClass