66 $data = $this->manager->getAuthenticationSessionData(
'reset-pass' );
71 if ( is_array( $data ) ) {
74 if ( !is_object( $data ) ) {
75 throw new \UnexpectedValueException(
'reset-pass is not valid' );
78 if ( !isset( $data->msg ) ) {
79 throw new \UnexpectedValueException(
'reset-pass msg is missing' );
80 } elseif ( !$data->msg instanceof \
Message ) {
81 throw new \UnexpectedValueException(
'reset-pass msg is not valid' );
82 } elseif ( !isset( $data->hard ) ) {
83 throw new \UnexpectedValueException(
'reset-pass hard is missing' );
84 } elseif ( isset( $data->req ) && (
86 !array_key_exists(
'retype', $data->req->getFieldInfo() )
88 throw new \UnexpectedValueException(
'reset-pass req is not valid' );
94 $this->manager->removeAuthenticationSessionData(
'reset-pass' );
100 if ( !$needReq->action ) {
105 $needReqs = [ $needReq ];
106 if ( !$data->hard ) {
109 wfMessage(
'authprovider-resetpass-skip-label' ),
110 wfMessage(
'authprovider-resetpass-skip-help' )
115 if ( !
$req || !array_key_exists(
'retype',
$req->getFieldInfo() ) ) {
119 if (
$req->password !==
$req->retype ) {
124 $status = $this->manager->allowsAuthenticationDataChange(
$req );
128 $this->manager->changeAuthenticationData(
$req );
130 $this->manager->removeAuthenticationSessionData(
'reset-pass' );
the array() calling protocol came about after MediaWiki 1.4rc1.
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 object
getName()
Get the user name, or the IP of an anonymous user.
either a unescaped string or a HtmlArmor object after in associative array form externallinks including delete and has completed for all link tables whether this was an auto creation default is conds Array Extra conditions for the No matching items in log is displayed if loglist is empty msgKey Array If you want a nice box with a set this to the key of the message First element is the message additional optional elements are parameters for the key that are processed with wfMessage() -> params() ->parseAsBlock()-offset Set to overwrite offset parameter in $wgRequest set to ''to unsetoffset-wrap String Wrap the message in html(usually something like"<
this hook is for auditing only RecentChangesLinked and Watchlist RecentChangesLinked and Watchlist e g Watchlist removed from all revisions and log entries to which it was applied This gives extensions a chance to take it off their books as the deletion has already been partly carried out by this point or something similar the user will be unable to create the tag set and then return false from the hook function Ensure you consume the ChangeTagAfterDelete hook to carry out custom deletion actions as context called by AbstractContent::getParserOutput May be used to override the normal model specific rendering of page content as context as context $options
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 local account $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
this hook is for auditing only $req
this hook is for auditing only RecentChangesLinked and Watchlist RecentChangesLinked and Watchlist e g Watchlist removed from all revisions and log entries to which it was applied This gives extensions a chance to take it off their books as the deletion has already been partly carried out by this point or something similar the user will be unable to create the tag set $status