MediaWiki  1.33.0
EnotifNotifyJob.php
Go to the documentation of this file.
1 <?php
29 class EnotifNotifyJob extends Job {
30  function __construct( Title $title, array $params ) {
31  parent::__construct( 'enotifNotify', $title, $params );
32  }
33 
34  function run() {
35  $enotif = new EmailNotification();
36  // Get the user from ID (rename safe). Anons are 0, so defer to name.
37  if ( isset( $this->params['editorID'] ) && $this->params['editorID'] ) {
38  $editor = User::newFromId( $this->params['editorID'] );
39  // B/C, only the name might be given.
40  } else {
41  # @todo FIXME: newFromName could return false on a badly configured wiki.
42  $editor = User::newFromName( $this->params['editor'], false );
43  }
44  $enotif->actuallyNotifyOnPageChange(
45  $editor,
46  $this->title,
47  $this->params['timestamp'],
48  $this->params['summary'],
49  $this->params['minorEdit'],
50  $this->params['oldid'],
51  $this->params['watchers'],
52  $this->params['pageStatus']
53  );
54 
55  return true;
56  }
57 }
EnotifNotifyJob\run
run()
Run the job.
Definition: EnotifNotifyJob.php:34
User\newFromId
static newFromId( $id)
Static factory method for creation from a given user ID.
Definition: User.php:609
Job\$title
Title $title
Definition: Job.php:41
User\newFromName
static newFromName( $name, $validate='valid')
Static factory method for creation from username.
Definition: User.php:585
Job\$params
array $params
Array of job parameters.
Definition: Job.php:35
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
Job
Class to both describe a background job and handle jobs.
Definition: Job.php:30
array
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))
$editor
passed in as a query string parameter to the various URLs constructed here(i.e. $prevlink) $ldel you ll need to handle error etc yourself modifying $error and returning true will cause the contents of $error to be echoed at the top of the edit form as wikitext Return true without altering $error to allow the edit to proceed & $editor
Definition: hooks.txt:1290
EnotifNotifyJob\__construct
__construct(Title $title, array $params)
Definition: EnotifNotifyJob.php:30
title
title
Definition: parserTests.txt:245
Title
Represents a title within MediaWiki.
Definition: Title.php:40
EmailNotification
This module processes the email notifications when the current page is changed.
Definition: EmailNotification.php:48
EnotifNotifyJob
Job for email notification mails.
Definition: EnotifNotifyJob.php:29