MediaWiki  1.23.8
Go to the documentation of this file.
1 <?php
12  private $skin;
14  private $messages;
17  private function initMessagesHref() {
18  # List of default messages for the sidebar. The sidebar doesn't care at
19  # all whether they are full URLs, interwiki links or local titles.
20  $URL_messages = array(
21  'mainpage',
22  'portal-url',
23  'currentevents-url',
24  'recentchanges-url',
25  'randompage-url',
26  'helppage',
27  );
29  # We're assuming that isValidURI works as advertised: it's also
30  # tested separately, in tests/phpunit/includes/HttpTest.php.
31  foreach ( $URL_messages as $m ) {
32  $titleName = MessageCache::singleton()->get( $m );
33  if ( Http::isValidURI( $titleName ) ) {
34  $this->messages[$m]['href'] = $titleName;
35  } else {
36  $title = Title::newFromText( $titleName );
37  $this->messages[$m]['href'] = $title->getLocalURL();
38  }
39  }
40  }
42  protected function setUp() {
43  parent::setUp();
44  $this->initMessagesHref();
45  $this->skin = new SkinTemplate();
46  $this->skin->getContext()->setLanguage( Language::factory( 'en' ) );
47  }
56  private function assertSideBar( $expected, $text, $message = '' ) {
57  $bar = array();
58  $this->skin->addToSidebarPlain( $bar, $text );
59  $this->assertEquals( $expected, $bar, $message );
60  }
65  public function testSidebarWithOnlyTwoTitles() {
66  $this->assertSideBar(
67  array(
68  'Title1' => array(),
69  'Title2' => array(),
70  ),
71  '* Title1
72 * Title2
73 '
74  );
75  }
80  public function testExpandMessages() {
81  $this->assertSidebar(
82  array( 'Title' => array(
83  array(
84  'text' => 'Help',
85  'href' => $this->messages['helppage']['href'],
86  'id' => 'n-help',
87  'active' => null
88  )
89  ) ),
90  '* Title
91 ** helppage|help
92 '
93  );
94  }
99  public function testExternalUrlsRequireADescription() {
100  $this->setMwGlobals( array(
101  'wgNoFollowLinks' => true,
102  'wgNoFollowDomainExceptions' => array(),
103  'wgNoFollowNsExceptions' => array(),
104  ) );
105  $this->assertSidebar(
106  array( 'Title' => array(
107  # **| Home
108  array(
109  'text' => 'Home',
110  'href' => '',
111  'id' => 'n-Home',
112  'active' => null,
113  'rel' => 'nofollow',
114  ),
115  # **
116  # ... skipped since it is missing a pipe with a description
117  ) ),
118  '* Title
119 **| Home
120 **
121 '
122  );
123  }
130  public function testTrickyPipe() {
131  $this->assertSidebar(
132  array( 'Title' => array(
133  # The first 2 are skipped
134  # Doesn't really test the url properly
135  # because it will vary with $wgArticlePath et al.
136  # ** Baz|Fred
137  array(
138  'text' => 'Fred',
139  'href' => Title::newFromText( 'Baz' )->getLocalURL(),
140  'id' => 'n-Fred',
141  'active' => null,
142  ),
143  array(
144  'text' => 'title-to-display',
145  'href' => Title::newFromText( 'page-to-go-to' )->getLocalURL(),
146  'id' => 'n-title-to-display',
147  'active' => null,
148  ),
149  ) ),
150  '* Title
151 ** {{PAGENAME|Foo}}
152 ** Bar
153 ** Baz|Fred
154 ** {{PLURAL:1|page-to-go-to{{int:pipe-separator/en}}title-to-display|branch not taken}}
155 '
156  );
157  }
159  #### Attributes for external links ##########################
160  private function getAttribs() {
161  # Sidebar text we will use everytime
162  $text = '* Title
163 **| Home';
165  $bar = array();
166  $this->skin->addToSideBarPlain( $bar, $text );
168  return $bar['Title'][0];
169  }
174  public function testTestAttributesAssertionHelper() {
175  $this->setMwGlobals( array(
176  'wgNoFollowLinks' => true,
177  'wgNoFollowDomainExceptions' => array(),
178  'wgNoFollowNsExceptions' => array(),
179  'wgExternalLinkTarget' => false,
180  ) );
181  $attribs = $this->getAttribs();
183  $this->assertArrayHasKey( 'rel', $attribs );
184  $this->assertEquals( 'nofollow', $attribs['rel'] );
186  $this->assertArrayNotHasKey( 'target', $attribs );
187  }
192  public function testRespectWgnofollowlinks() {
193  $this->setMwGlobals( 'wgNoFollowLinks', false );
195  $attribs = $this->getAttribs();
196  $this->assertArrayNotHasKey( 'rel', $attribs,
197  'External URL in sidebar do not have rel=nofollow when $wgNoFollowLinks = false'
198  );
199  }
205  public function testRespectExternallinktarget( $externalLinkTarget ) {
206  $this->setMwGlobals( 'wgExternalLinkTarget', $externalLinkTarget );
208  $attribs = $this->getAttribs();
209  $this->assertArrayHasKey( 'target', $attribs );
210  $this->assertEquals( $attribs['target'], $externalLinkTarget );
211  }
213  public static function dataRespectExternallinktarget() {
214  return array(
215  array( '_blank' ),
216  array( '_self' ),
217  );
218  }
219 }
static dataRespectExternallinktarget()
Definition: SideBarTest.php:212
Build $this->messages array.
Definition: SideBarTest.php:16
static newFromText( $text, $defaultNamespace=NS_MAIN)
Create a new Title from text, such as what one would find in a link.
Definition: Title.php:189
Get the RequestContext object.
Definition: ContextSource.php:40
bug 33321 - Make sure there's a | after transforming.
Definition: SideBarTest.php:129
Definition: SideBarTest.php:41
skin txt MediaWiki includes four core it has been set as the default in MediaWiki since the replacing Monobook it had been been the default skin since before being replaced by Vector largely rewritten in while keeping its appearance Several legacy skins were removed in the as the burden of supporting them became too heavy to bear Those in etc for skin dependent CSS etc for skin dependent JavaScript These can also be customised on a per user by etc This feature has led to a wide variety of user styles becoming that gallery is a good place to ending in php
Definition: skin.txt:62
@covers SkinTemplate::addToSidebarPlain
Definition: SideBarTest.php:98
testRespectExternallinktarget( $externalLinkTarget)
Test $wgExternaLinkTarget in sidebar @dataProvider dataRespectExternallinktarget.
Definition: SideBarTest.php:204
We use the convention $dbr for read and $dbw for write to help you keep track of whether the database object is a the world will explode Or to be a subsequent write query which succeeded on the master may fail when replicated to the slave due to a unique key collision Replication on the slave will stop and it may take hours to repair the database and get it back online Setting read_only in my cnf on the slave will avoid this but given the dire we prefer to have as many checks as possible We provide a but the wrapper functions like please read the documentation for except in special pages derived from QueryPage It s a common pitfall for new developers to submit code containing SQL queries which examine huge numbers of rows Remember that COUNT * is(N), counting rows in atable is like counting beans in a bucket.------------------------------------------------------------------------ Replication------------------------------------------------------------------------The largest installation of MediaWiki, Wikimedia, uses a large set ofslave MySQL servers replicating writes made to a master MySQL server. Itis important to understand the issues associated with this setup if youwant to write code destined for Wikipedia.It 's often the case that the best algorithm to use for a given taskdepends on whether or not replication is in use. Due to our unabashedWikipedia-centrism, we often just use the replication-friendly version, but if you like, you can use wfGetLB() ->getServerCount() > 1 tocheck to see if replication is in use.===Lag===Lag primarily occurs when large write queries are sent to the master.Writes on the master are executed in parallel, but they are executed inserial when they are replicated to the slaves. The master writes thequery to the binlog when the transaction is committed. The slaves pollthe binlog and start executing the query as soon as it appears. They canservice reads while they are performing a write query, but will not readanything more from the binlog and thus will perform no more writes. Thismeans that if the write query runs for a long time, the slaves will lagbehind the master for the time it takes for the write query to complete.Lag can be exacerbated by high read load. MediaWiki 's load balancer willstop sending reads to a slave when it is lagged by more than 30 seconds.If the load ratios are set incorrectly, or if there is too much loadgenerally, this may lead to a slave permanently hovering around 30seconds lag.If all slaves are lagged by more than 30 seconds, MediaWiki will stopwriting to the database. All edits and other write operations will berefused, with an error returned to the user. This gives the slaves achance to catch up. Before we had this mechanism, the slaves wouldregularly lag by several minutes, making review of recent editsdifficult.In addition to this, MediaWiki attempts to ensure that the user seesevents occurring on the wiki in chronological order. A few seconds of lagcan be tolerated, as long as the user sees a consistent picture fromsubsequent requests. This is done by saving the master binlog positionin the session, and then at the start of each request, waiting for theslave to catch up to that position before doing any reads from it. Ifthis wait times out, reads are allowed anyway, but the request isconsidered to be in "lagged slave mode". Lagged slave mode can bechecked by calling wfGetLB() ->getLaggedSlaveMode(). The onlypractical consequence at present is a warning displayed in the pagefooter.===Lag avoidance===To avoid excessive lag, queries which write large numbers of rows shouldbe split up, generally to write one row at a time. Multi-row INSERT ...SELECT queries are the worst offenders should be avoided altogether.Instead do the select first and then the insert.===Working with lag===Despite our best efforts, it 's not practical to guarantee a low-lagenvironment. Lag will usually be less than one second, but mayoccasionally be up to 30 seconds. For scalability, it 's very importantto keep load on the master low, so simply sending all your queries tothe master is not the answer. So when you have a genuine need forup-to-date data, the following approach is advised:1) Do a quick query to the master for a sequence number or timestamp 2) Run the full query on the slave and check if it matches the data you gotfrom the master 3) If it doesn 't, run the full query on the masterTo avoid swamping the master every time the slaves lag, use of thisapproach should be kept to a minimum. In most cases you should just readfrom the slave and let the user deal with the delay.------------------------------------------------------------------------ Lock contention------------------------------------------------------------------------Due to the high write rate on Wikipedia(and some other wikis), MediaWiki developers need to be very careful to structure their writesto avoid long-lasting locks. By default, MediaWiki opens a transactionat the first query, and commits it before the output is sent. Locks willbe held from the time when the query is done until the commit. So youcan reduce lock time by doing as much processing as possible before youdo your write queries.Often this approach is not good enough, and it becomes necessary toenclose small groups of queries in their own transaction. Use thefollowing syntax:$dbw=wfGetDB(DB_MASTER
SkinTemplate $skin
A skin template, reinitialized before each test.
Definition: SideBarTest.php:11
@covers SkinTemplate::addToSidebarPlain
Definition: SideBarTest.php:64
design txt This is a brief overview of the new design More thorough and up to date information is available on the documentation wiki at etc Handles the details of getting and saving to the user table of the and dealing with sessions and cookies OutputPage Encapsulates the entire HTML page that will be sent in response to any server request It is used by calling its functions to add text
Definition: design.txt:12
if(! $in) print Initializing normalization quick check tables n
Definition: UtfNormalGenerate.php:36
namespace and then decline to actually register it RecentChangesLinked and Watchlist RecentChangesLinked and Watchlist e g Watchlist but no entry for that model exists in $wgContentHandlers if desired whether it is OK to use $contentModel on $title Handler functions that modify $ok should generally return false to prevent further hooks from further modifying $ok in case the handler function wants to provide a converted Content object Note that $result getContentModel() must return $toModel. Handler functions that modify $result should generally return false to further attempts at conversion. 'ContribsPager you ll need to handle error messages
Definition: hooks.txt:896
to move a page</td >< td > &*You are moving the page across *A non empty talk page already exists under the new or *You uncheck the box below In those you will have to move or merge the page manually if desired</td >< td > be sure to &You are responsible for making sure that links continue to point where they are supposed to go Note that the page will &a page at the new title
Definition: All_system_messages.txt:2703
Local cache for sidebar messages.
Definition: SideBarTest.php:13
Simple test to verify our helper assertAttribs() is functional.
Definition: SideBarTest.php:173
setMwGlobals( $pairs, $value=null)
Definition: MediaWikiTestCase.php:302
the array() calling protocol came about after MediaWiki 1.4rc1.
List of Api Query prop modules.
static singleton()
Get the signleton instance of this class.
Definition: MessageCache.php:101
Definition: SideBarTest.php:159
assertSideBar( $expected, $text, $message='')
Internal helper to test the sidebar.
Definition: SideBarTest.php:55
@covers SkinTemplate::addToSidebarPlain
Definition: SideBarTest.php:79
presenting them properly to the user as errors is done by the caller $title
Definition: hooks.txt:1324
this class mediates it Skin Encapsulates a look and feel for the wiki All of the functions that render HTML and make choices about how to render it are here and are called from various other places when and is meant to be subclassed with other skins that may override some of its functions The User object contains a reference to a skin(according to that user 's preference)
Base class that store and restore the Language objects.
Definition: MediaWikiLangTestCase.php:6
@group Skin
Definition: SideBarTest.php:6
=Architecture==Two class hierarchies are used to provide the functionality associated with the different content models:*Content interface(and AbstractContent base class) define functionality that acts on the concrete content of a page, and *ContentHandler base class provides functionality specific to a content model, but not acting on concrete content. The most important function of ContentHandler is to act as a factory for the appropriate implementation of Content. These Content objects are to be used by MediaWiki everywhere, instead of passing page content around as text. All manipulation and analysis of page content must be done via the appropriate methods of the Content object. For each content model, a subclass of ContentHandler has to be registered with $wgContentHandlers. The ContentHandler object for a given content model can be obtained using ContentHandler::getForModelID($id). Also Title, WikiPage and Revision now have getContentHandler() methods for convenience. ContentHandler objects are singletons that provide functionality specific to the content type, but not directly acting on the content of some page. ContentHandler::makeEmptyContent() and ContentHandler::unserializeContent() can be used to create a Content object of the appropriate type. However, it is recommended to instead use WikiPage::getContent() resp. Revision::getContent() to get a page 's content as a Content object. These two methods should be the ONLY way in which page content is accessed. Another important function of ContentHandler objects is to define custom action handlers for a content model, see ContentHandler::getActionOverrides(). This is similar to what WikiPage::getActionOverrides() was already doing.==Serialization==With the ContentHandler facility, page content no longer has to be text based. Objects implementing the Content interface are used to represent and handle the content internally. For storage and data exchange, each content model supports at least one serialization format via ContentHandler::serializeContent($content). The list of supported formats for a given content model can be accessed using ContentHandler::getSupportedFormats(). Content serialization formats are identified using MIME type like strings. The following formats are built in:*text/x-wiki - wikitext *text/javascript - for js pages *text/css - for css pages *text/plain - for future use, e.g. with plain text messages. *text/html - for future use, e.g. with plain html messages. *application/vnd.php.serialized - for future use with the api and for extensions *application/json - for future use with the api, and for use by extensions *application/xml - for future use with the api, and for use by extensions In PHP, use the corresponding CONTENT_FORMAT_XXX constant. Note that when using the API to access page content, especially action=edit, action=parse and action=query &prop=revisions, the model and format of the content should always be handled explicitly. Without that information, interpretation of the provided content is not reliable. The same applies to XML dumps generated via maintenance/dumpBackup.php or Special:Export. Also note that the API will provide encapsulated, serialized content - so if the API was called with format=json, and contentformat is also json(or rather, application/json), the page content is represented as a string containing an escaped json structure. Extensions that use JSON to serialize some types of page content may provide specialized API modules that allow access to that content in a more natural form.==Compatibility==The ContentHandler facility is introduced in a way that should allow all existing code to keep functioning at least for pages that contain wikitext or other text based content. However, a number of functions and hooks have been deprecated in favor of new versions that are aware of the page 's content model, and will now generate warnings when used. Most importantly, the following functions have been deprecated:*Revisions::getText() and Revisions::getRawText() is deprecated in favor Revisions::getContent() *WikiPage::getText() is deprecated in favor WikiPage::getContent() Also, the old Article::getContent()(which returns text) is superceded by Article::getContentObject(). However, both methods should be avoided since they do not provide clean access to the page 's actual content. For instance, they may return a system message for non-existing pages. Use WikiPage::getContent() instead. Code that relies on a textual representation of the page content should eventually be rewritten. However, ContentHandler::getContentText() provides a stop-gap that can be used to get text for a page. Its behavior is controlled by $wgContentHandlerTextFallback it
Definition: contenthandler.txt:107
Represents a title within MediaWiki.
Definition: Title.php:35
The ContentHandler facility adds support for arbitrary content types on wiki instead of relying on wikitext for everything It was introduced in MediaWiki Each kind of and so on Built in content types are
Definition: contenthandler.txt:5
Test $wgNoFollowLinks in sidebar.
Definition: SideBarTest.php:191
This document is intended to provide useful advice for parties seeking to redistribute MediaWiki to end users It s targeted particularly at maintainers for Linux since it s been observed that distribution packages of MediaWiki often break We ve consistently had to recommend that users seeking support use official tarballs instead of their distribution s and this often solves whatever problem the user is having It would be nice if this could such as
Definition: distributors.txt:9
static isValidURI( $uri)
Checks that the given URI is a valid one.
Definition: HttpFunctions.php:172
static factory( $code)
Get a cached or new language object for a given language code.
Definition: Language.php:184
null means default in associative array with keys and values unescaped Should be merged with default with a value of false meaning to suppress the attribute in associative array with keys and values unescaped noclasses just before the function returns a value If you return an< a > element with HTML attributes $attribs and contents $html will be returned If you return $ret will be returned and may include noclasses after processing & $attribs
Definition: hooks.txt:1530
addToSidebarPlain(&$bar, $text)
Add content from plain text.
Definition: Skin.php:1294
shown</td >< td > a href
Definition: All_system_messages.txt:2674
Template-filler skin base class Formerly generic PHPTal (http://phptal.sourceforge....
Definition: SkinTemplate.php:70
do that in ParserLimitReportFormat instead use this to modify the parameters of the image and a DIV can begin in one section and end in another Make sure your code can handle that case gracefully See the EditSectionClearerLink extension for an example zero but section is usually empty its values are the globals values my talk page
Definition: hooks.txt:1956