MediaWiki  1.30.0
ViewAction.php
Go to the documentation of this file.
1 <?php
33 class ViewAction extends FormlessAction {
34 
35  public function getName() {
36  return 'view';
37  }
38 
39  public function onView() {
40  return null;
41  }
42 
43  public function show() {
44  $config = $this->context->getConfig();
45 
46  if (
47  $config->get( 'DebugToolbar' ) == false && // don't let this get stuck on pages
48  $this->page->checkTouched() // page exists and is not a redirect
49  ) {
50  // Include any redirect in the last-modified calculation
51  $redirFromTitle = $this->page->getRedirectedFrom();
52  if ( !$redirFromTitle ) {
53  $touched = $this->page->getTouched();
54  } elseif ( $config->get( 'MaxRedirects' ) <= 1 ) {
55  $touched = max( $this->page->getTouched(), $redirFromTitle->getTouched() );
56  } else {
57  // Don't bother following the chain and getting the max mtime
58  $touched = null;
59  }
60 
61  // Send HTTP 304 if the IMS matches or otherwise set expiry/last-modified headers
62  if ( $touched && $this->getOutput()->checkLastModified( $touched ) ) {
63  wfDebug( __METHOD__ . ": done 304\n" );
64  return;
65  }
66  }
67 
68  $this->page->view();
69  }
70 }
FormlessAction
An action which just does something, without showing a form first.
Definition: FormlessAction.php:28
ViewAction\onView
onView()
Show something on GET request.
Definition: ViewAction.php:39
page
target page
Definition: All_system_messages.txt:1267
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
wfDebug
wfDebug( $text, $dest='all', array $context=[])
Sends a line to the debug log if enabled or, optionally, to a comment in output.
Definition: GlobalFunctions.php:1047
ViewAction
An action that views article content.
Definition: ViewAction.php:33
Action\getOutput
getOutput()
Get the OutputPage being used for this instance.
Definition: Action.php:207
ViewAction\getName
getName()
Return the name of the action this object responds to.
Definition: ViewAction.php:35
ViewAction\show
show()
The main action entry point.
Definition: ViewAction.php:43