45 return $this->
page->doPurge();
56 if (
$user->pingLimiter(
'purge' ) ) {
64 [
'title' =>
null,
'action' =>
null ]
70 $this->redirectParams = $this->
getRequest()->getVal(
'redirectparams',
'' );
72 if ( $form->show() ) {
86 'vertical-label' =>
true,
88 'default' => $this->
msg(
'confirm-purge-top' )->parse()
99 return $this->
msg(
'confirm-purge-bottom' )->parse();
103 $this->
getOutput()->redirect( $this->
getTitle()->getFullURL( $this->redirectParams ) );
wfArrayToCgi( $array1, $array2=null, $prefix='')
This function takes one or two arrays as input, and returns a CGI-style string, e....
checkCanExecute(User $user)
Checks if the given user (identified by an object) can perform this action.
getTitle()
Shortcut to get the Title object from the page.
getOutput()
Get the OutputPage being used for this instance.
msg( $key)
Get a Message object with context set Parameters are the same as wfMessage()
getUser()
Shortcut to get the User being used for this instance.
setHeaders()
Set output headers for noindexing etc.
getRequest()
Get the WebRequest being used for this instance.
User-requested page cache purging.
usesOOUI()
Whether the form should use OOUI.
requiresUnblock()
Whether this action can still be executed by a blocked user.
show()
The basic pattern for actions is to display some sort of HTMLForm UI, maybe with some stuff underneat...
getDescription()
Returns the description that goes below the <h1> tag.
onSubmit( $data)
Process the form on POST submission.
doesWrites()
Indicates whether this action may perform database writes.
getFormFields()
Get an HTMLForm descriptor array.
alterForm(HTMLForm $form)
Play with the HTMLForm if you need to more substantially.
onSuccess()
Do something exciting on successful processing of the form.
getName()
Return the name of the action this object responds to.
$data
Utility to generate mapping file used in mw.Title (phpCharToUpper.json)
return true to allow those checks to and false if checking is done & $user
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