MediaWiki  1.29.2
CountFancyCaptchas.php
Go to the documentation of this file.
1 <?php
23 if ( getenv( 'MW_INSTALL_PATH' ) ) {
24  $IP = getenv( 'MW_INSTALL_PATH' );
25 } else {
26  $IP = __DIR__ . '/../../..';
27 }
28 
29 require_once ( "$IP/maintenance/Maintenance.php" );
30 
37  public function __construct() {
38  parent::__construct();
39  $this->mDescription = "Counts the number of fancy aptchas in storage";
40  $this->requireExtension( "FancyCaptcha" );
41  }
42 
43  public function execute() {
44  $instance = ConfirmEditHooks::getInstance();
45  if ( !( $instance instanceof FancyCaptcha ) ) {
46  $this->error( "\$wgCaptchaClass is not FancyCaptcha.\n", 1 );
47  }
48 
49  $countAct = $instance->getCaptchaCount();
50  $this->output( "Current number of captchas is $countAct.\n" );
51  }
52 }
53 
54 $maintClass = "CountFancyCaptchas";
55 require_once ( RUN_MAINTENANCE_IF_MAIN );
CountFancyCaptchas
Maintenance script that counts the number of captchas remaining.
Definition: CountFancyCaptchas.php:36
RUN_MAINTENANCE_IF_MAIN
require_once RUN_MAINTENANCE_IF_MAIN
Definition: maintenance.txt:50
$maintClass
$maintClass
Definition: CountFancyCaptchas.php:54
Maintenance
Abstract maintenance class for quickly writing and churning out maintenance scripts with minimal effo...
Definition: maintenance.txt:39
ConfirmEditHooks\getInstance
static getInstance()
Get the global Captcha instance.
Definition: ConfirmEditHooks.php:13
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
$IP
$IP
Definition: update.php:3
Maintenance\requireExtension
requireExtension( $name)
Indicate that the specified extension must be loaded before the script can run.
Definition: Maintenance.php:529
FancyCaptcha
FancyCaptcha for displaying captchas precomputed by captcha.py.
Definition: FancyCaptcha.class.php:9
CountFancyCaptchas\execute
execute()
Do the actual work.
Definition: CountFancyCaptchas.php:43
Maintenance\error
error( $err, $die=0)
Throw an error to the user.
Definition: Maintenance.php:392
Maintenance\output
output( $out, $channel=null)
Throw some output to the user.
Definition: Maintenance.php:373
CountFancyCaptchas\__construct
__construct()
Default constructor.
Definition: CountFancyCaptchas.php:37