Go to the documentation of this file.
35 parent::__construct(
'Lockdb',
'siteadmin' );
47 parent::checkExecutePermissions(
$user );
48 # If the lock file isn't writable, we can do sweet bugger all
49 if ( !is_writable( dirname( $this->
getConfig()->
get(
'ReadOnlyFile' ) ) ) ) {
52 if ( file_exists( $this->
getConfig()->
get(
'ReadOnlyFile' ) ) ) {
62 'vertical-label' =>
true,
63 'label-message' =>
'enterlockreason',
67 'label-message' =>
'lockconfirm',
74 ->setHeaderText( $this->
msg(
'lockdbtext' )->parseAsBlock() )
75 ->setSubmitTextMsg(
'lockbtn' );
79 if ( !$data[
'Confirm'] ) {
83 Wikimedia\suppressWarnings();
84 $fp = fopen( $this->
getConfig()->
get(
'ReadOnlyFile' ),
'w' );
85 Wikimedia\restoreWarnings();
87 if (
false === $fp ) {
88 # This used to show a file not found error, but the likeliest reason for fopen()
89 # to fail at this point is insufficient permission to write to the file...good old
90 # is_writable() is plain wrong in some cases, it seems...
93 fwrite( $fp, $data[
'Reason'] );
95 $contLang = MediaWikiServices::getInstance()->getContentLanguage();
96 fwrite( $fp,
"\n<p>" . $this->
msg(
'lockedbyandtime',
98 $contLang->date( $timestamp,
false,
false ),
99 $contLang->time( $timestamp,
false,
false )
100 )->inContentLanguage()->text() .
"</p>\n" );
108 $out->addSubtitle( $this->
msg(
'lockdbsuccesssub' ) );
109 $out->addWikiMsg(
'lockdbsuccesstext' );
please add to it if you re going to add events to the MediaWiki code where normally authentication against an external auth plugin would be creating a account $user
msg( $key)
Wrapper around wfMessage that sets the current context.
getOutput()
Get the OutputPage being used for this instance.
static newFatal( $message)
Factory function for fatal errors.
Special page which uses an HTMLForm to handle processing.
getName()
Get the name of this Special Page.
alterForm(HTMLForm $form)
Play with the HTMLForm if you need to more substantially.
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
requiresWrite()
Whether this action requires the wiki not to be locked.
getConfig()
Shortcut to get main config object.
doesWrites()
Indicates whether this special page may perform database writes.
as see the revision history and available at free of to any person obtaining a copy of this software and associated documentation to deal in the Software without including without limitation the rights to use
getUser()
Shortcut to get the User executing this instance.
wfTimestampNow()
Convenience function; returns MediaWiki timestamp for the present time.
The wiki should then use memcached to cache various data To use multiple just add more items to the array To increase the weight of a make its entry a array("192.168.0.1:11211", 2))
static newGood( $value=null)
Factory function for good results.
A form to make the database readonly (eg for maintenance purposes).
onSuccess()
Do something exciting on successful processing of the form, most likely to show a confirmation messag...
getFormFields()
Get an HTMLForm descriptor array.
onSubmit(array $data)
Process the form on POST submission.
getDisplayFormat()
Get display format for the form.
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 MediaWikiServices
An error page which can definitely be safely rendered using the OutputPage.
checkExecutePermissions(User $user)
Called from execute() to check if the given user can perform this action.
The User object encapsulates all of the user-specific settings (user_id, name, rights,...
getGroupName()
Under which header this special page is listed in Special:SpecialPages See messages 'specialpages-gro...
this hook is for auditing only or null if authentication failed before getting that far or null if we can t even determine that probably a stub 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