MediaWiki  1.33.0
importSites.php
Go to the documentation of this file.
1 <?php
2 
3 $basePath = getenv( 'MW_INSTALL_PATH' ) !== false ? getenv( 'MW_INSTALL_PATH' ) : __DIR__ . '/..';
4 
5 require_once $basePath . '/maintenance/Maintenance.php';
6 
15 class ImportSites extends Maintenance {
16 
17  public function __construct() {
18  $this->addDescription( 'Imports site definitions from XML into the sites table.' );
19 
20  $this->addArg( 'file', 'An XML file containing site definitions (see docs/sitelist.txt). ' .
21  'Use "php://stdin" to read from stdin.', true
22  );
23 
24  parent::__construct();
25  }
26 
30  public function execute() {
31  $file = $this->getArg( 0 );
32 
33  $siteStore = \MediaWiki\MediaWikiServices::getInstance()->getSiteStore();
34  $importer = new SiteImporter( $siteStore );
35  $importer->setExceptionCallback( [ $this, 'reportException' ] );
36 
37  $importer->importFromFile( $file );
38 
39  $this->output( "Done.\n" );
40  }
41 
47  public function reportException( Exception $ex ) {
48  $msg = $ex->getMessage();
49  $this->output( "$msg\n" );
50  }
51 }
52 
54 require_once RUN_MAINTENANCE_IF_MAIN;
ImportSites\reportException
reportException(Exception $ex)
Outputs a message via the output() method.
Definition: importSites.php:47
$file
if(PHP_SAPI !='cli-server') if(!isset( $_SERVER['SCRIPT_FILENAME'])) $file
Definition: router.php:42
Maintenance\addDescription
addDescription( $text)
Set the description text.
Definition: Maintenance.php:329
RUN_MAINTENANCE_IF_MAIN
require_once RUN_MAINTENANCE_IF_MAIN
Definition: maintenance.txt:50
SiteImporter
Definition: SiteImporter.php:30
Maintenance
Abstract maintenance class for quickly writing and churning out maintenance scripts with minimal effo...
Definition: maintenance.txt:39
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
ImportSites\__construct
__construct()
Default constructor.
Definition: importSites.php:17
ImportSites
Maintenance script for importing site definitions from XML into the sites table.
Definition: importSites.php:15
$basePath
$basePath
Definition: importSites.php:3
Maintenance\addArg
addArg( $arg, $description, $required=true)
Add some args that are needed.
Definition: Maintenance.php:300
Maintenance\output
output( $out, $channel=null)
Throw some output to the user.
Definition: Maintenance.php:434
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
Maintenance\getArg
getArg( $argId=0, $default=null)
Get an argument.
Definition: Maintenance.php:352
ImportSites\execute
execute()
Do the import.
Definition: importSites.php:30
$maintClass
$maintClass
Definition: importSites.php:53