MediaWiki  1.23.12
tests/parser/preprocess/All_system_messages.txt File Reference

Functions

See &</td >< td > &Fill in a specific reason below (for example, citing particular pages that were vandalized).</td >< td >
 
page as if applicable</td >< td > ve followed a link to a page that doesn &To create the start typing in the box below (see the &#91;&#91;Wiktionary:Help &#124;help page]] for more info). If you are here by mistake
 
could not be made into a sysop (Did you enter the name correctly?) &lt
 
which are not or by specifying more than one search term (only pages containing all of the search terms will appear in the result).</td >< td >
 

Variables

 __pad0__
 
 __pad1__
 
Attention __pad2__
 
WARNING __pad3__
 
 __pad4__
 
optional __pad5__
 
optional __pad6__
 
If this is not the you may have found a bug in the software Please report this to an administrator
 
accesskey contributions & amp
 
If this is not the case
 
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 cases
 
in the sidebar</td >< td > font color =red&gt
 
matched page titles and the text of pages</td >< td > t write to or create math output directory</td >< td > t write to or create math temp directory</td >< td > check for correct installation of dvips
 
Please log in again after you receive it</td >< td > s a saved copy from
 
matched page titles and the text of pages</td >< td > t write to or create math output directory</td >< td > t write to or create math temp directory</td >< td > check for correct installation of gs
 
 gt
 
shown</td >< td > a href =&quot
 
which are not indexed
 
Your real if you choose to provide it
 
If you want to remove the page from your watchlist later
 
matched page titles and the text of pages</td >< td > t write to or create math output directory</td >< td > t write to or create math temp directory</td >< td > check for correct installation of latex
 
 lt
 
address of the mail
 
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 unless it is empty or a redirect and has no past edit history This means that you can rename a page back to where it was just renamed from if you make a mistake
 
Your real name
 
to move a page</td >< td > &*You are moving the page across namespaces
 
 nbsp
 
target page
 
</td >< td > &</td >< td > & quot
 
This list may contain false positives That usually means there is additional text with links below the first Each row contains links to the first and second redirect
 
</td >< td > this can then be imported into another wiki running MediaWiki software
 
wiki Special
 
This list may contain false positives That usually means there is additional text with links below the first Each row contains links to the first and second as well as the first line of the second redirect text
 
has been added to your &Future changes to this page and its associated Talk page will be listed there
 
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
 
</td >< td > this can then be imported into another wiki running MediaWiki transformed
 
 User
 
page as well
 
</td >< td > &</td >< td > t want your writing to be edited mercilessly and redistributed at will
 
</td >< td > &</td >< td > t want your writing to be edited mercilessly and redistributed at then don &You are also promising us that you wrote this yourself
 

Function Documentation

◆ below() [1/2]

See&</td><td> & Fill in a specific reason below ( for  example,
citing particular pages that were  vandalized 
)

Definition at line 649 of file All_system_messages.txt.

◆ below() [2/2]

page as if applicable</td><td> ve followed a link to a page that doesn& To create the start typing in the box below ( see the &#91;&#91;Wiktionary:Help &#124;help page]] for more  info)

◆ sysop()

could not be made into a sysop ( Did you enter the name correctly?  ) &

Referenced by showUsage().

◆ term()

which are not or by specifying more than one search term ( only pages containing all of the search terms will appear in the  result)

Variable Documentation

◆ __pad0__

__pad0__

Definition at line 1079 of file All_system_messages.txt.

◆ __pad1__

__pad1__

Definition at line 1090 of file All_system_messages.txt.

◆ __pad2__

Attention __pad2__

Definition at line 1266 of file All_system_messages.txt.

◆ __pad3__

WARNING __pad3__

Definition at line 1325 of file All_system_messages.txt.

◆ __pad4__

__pad4__

Definition at line 3011 of file All_system_messages.txt.

◆ __pad5__

optional __pad5__

Definition at line 3391 of file All_system_messages.txt.

◆ __pad6__

optional __pad6__

Definition at line 3393 of file All_system_messages.txt.

◆ administrator

If this is not the you may have found a bug in the software Please report this to an administrator

Definition at line 2602 of file All_system_messages.txt.

◆ amp

List redirects & amp

Definition at line 83 of file All_system_messages.txt.

◆ case

If this is not the case

Definition at line 2602 of file All_system_messages.txt.

◆ cases

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 cases

◆ color

in the sidebar</td><td> font color =red&gt

◆ dvips

matched page titles and the text of pages</td><td> t write to or create math output directory</td><td> t write to or create math temp directory</td><td> check for correct installation of dvips

Definition at line 2472 of file All_system_messages.txt.

◆ from

◆ gs

matched page titles and the text of pages</td><td> t write to or create math output directory</td><td> t write to or create math temp directory</td><td> check for correct installation of gs

Definition at line 2472 of file All_system_messages.txt.

◆ gt

a& gt

Definition at line 83 of file All_system_messages.txt.

◆ href

◆ indexed

which are not indexed

Definition at line 3011 of file All_system_messages.txt.

◆ it

Your real if you choose to provide it

Definition at line 1355 of file All_system_messages.txt.

◆ later

If you want to remove the page from your watchlist later

Definition at line 361 of file All_system_messages.txt.

Referenced by PoolCounterRedis::initAndPopPoolSlotList().

◆ latex

matched page titles and the text of pages</td><td> t write to or create math output directory</td><td> t write to or create math temp directory</td><td> check for correct installation of latex
Initial value:
{{int:Math_bad_tmpdir}}
</td></tr><tr><td>
[http:
</td><td>
Failed to parse
</td><td>
{{int:Math_failure}}
</td></tr><tr><td>
[http:
</td><td>
PNG conversion failed

Definition at line 2472 of file All_system_messages.txt.

◆ lt

logged in& lt

Definition at line 1 of file All_system_messages.txt.

◆ mail

address of the mail

Definition at line 1386 of file All_system_messages.txt.

Referenced by UserMailer::send().

◆ mistake

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 unless it is empty or a redirect and has no past edit history This means that you can rename a page back to where it was just renamed from if you make a mistake

Definition at line 2703 of file All_system_messages.txt.

◆ name

to move a page</td><td> & * You are moving the page across * A non empty talk page already exists under the new name

Definition at line 1355 of file All_system_messages.txt.

◆ namespaces

to move a page</td><td> & * You are moving the page across namespaces

◆ nbsp

& nbsp

Definition at line 3377 of file All_system_messages.txt.

◆ page

page as if applicable</td><td> ve followed a link to a page that doesn& To create the page

Definition at line 1267 of file All_system_messages.txt.

◆ quot

optional and it can be used to send you a new password if you forget it</td >< td > & quot
Initial value:
{{int:Accmailtext}}
</td></tr><tr><td>
[http:
</td><td>
Password sent.
</td><td>
{{int:Accmailtitle}}
</td></tr><tr><td>
[http:
</td><td>
</td><td>
{{int:Actioncomplete}}
</td></tr><tr><td>
[http:
</td><td>
Added to watchlist
</td><td>
{{int:Addedwatch}}
</td></tr><tr><td>
[http:
</td><td>
The page &quot

Definition at line 330 of file All_system_messages.txt.

◆ redirect

This list may contain false positives That usually means there is additional text with links below the first Each row contains links to the first and second redirect

◆ software

</td><td> this can then be imported into another wiki running MediaWiki software
Initial value:
{{int:Explainconflict}}
</td></tr><tr><td>
[http:
</td><td>
Export pages
</td><td>
{{int:Export}}
</td></tr><tr><td>
[http:
</td><td>
Include only the current revision, not the full history
</td><td>
{{int:Exportcuronly}}
</td></tr><tr><td>
[http:
</td><td>
You can export the text and editing history of a particular
page or set of pages wrapped in some XML

Definition at line 1488 of file All_system_messages.txt.

◆ Special

wiki Special

Definition at line 2674 of file All_system_messages.txt.

Referenced by BackupReader::__construct(), and CheckLanguageCLI::help().

◆ text

This list may contain false positives That usually means there is additional text with links below the first Each row contains links to the first and second as well as the first line of the second redirect text

Definition at line 1267 of file All_system_messages.txt.

◆ there

has been added to your& Future changes to this page and its associated Talk page will be listed there

◆ title

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
Initial value:
{{int:Movepagetalktext}}
</td></tr><tr><td>
[http:
</td><td>
Using the form below will rename a page, moving all
of its history to the new name.
The old title will become a redirect page to the new title.
Links to the old page title will not be changed

Definition at line 2703 of file All_system_messages.txt.

Referenced by RecentChangeTest::__construct(), PageArchive::__construct(), ErrorPageError::__construct(), RevisionListBase::__construct(), UpdateCollation::__construct(), FileDeleteForm::__construct(), FeedItem::__construct(), CategoryViewer::__construct(), UnregisteredLocalFile::__construct(), ArchivedFile::__construct(), BacklinkCache::__construct(), JobSpecification::__construct(), Exif::__construct(), Job::__construct(), File::__construct(), PPFuzzTest::__construct(), MergeHistoryPager::__construct(), PPFrame_Hash::__construct(), PPFrame_DOM::__construct(), PPTemplateFrame_Hash::__construct(), PPTemplateFrame_DOM::__construct(), EmailNotification::actuallyNotifyOnPageChange(), RecentChangeTest::assertIRCComment(), File::assertTitleDefined(), DerivativeContext::canUseWikiPage(), EmailNotification::composeCommonMailtext(), CategoryViewer::doCategoryQuery(), RevDel_RevisionList::doPostCommitUpdates(), RevDel_FileList::doPostCommitUpdates(), RevDel_RevisionList::doPreCommitUpdates(), RevDel_RevisionList::doQuery(), RevisionList::doQuery(), RevDel_ArchiveList::doQuery(), RevDel_FileList::doQuery(), RevDel_ArchivedFileList::doQuery(), WebRequest::doSecurityRedirect(), ConvertLinks::execute(), FileDeleteForm::execute(), PPFuzzTest::execute(), PPFrame_Hash::expand(), PPFrame_DOM::expand(), CategoryViewer::formatList(), FileDeleteForm::getAction(), BacklinkCache::getConditions(), RevDel_RevisionList::getCurrent(), LocalFile::getDescriptionText(), LocalFile::getDescriptionUrl(), LocalFile::getHistory(), CategoryViewer::getImageSection(), PageArchive::getLastRevisionText(), File::getName(), BacklinkCache::getNumLinks(), CategoryViewer::getPagesSection(), PPFrame_Hash::getPDBK(), PPFrame_DOM::getPDBK(), PageArchive::getPreviousRevision(), PPFuzzTest::getReport(), PageArchive::getRevision(), RefreshLinksJob2::getSingleTitleJobs(), FeedItem::getTitle(), RequestContext::getTitle(), DerivativeContext::getTitle(), WikiRevision::importOldRevision(), ApiFormatBase::initPrinter(), PageArchive::isDeleted(), LogPager::limitTitle(), PageArchive::listFiles(), PageArchive::listRevisions(), ArchivedFile::load(), LocalFile::move(), LogFormatterTest::newLogEntry(), LocalFile::nextHistoryLine(), outHeader(), AtomFeed::outHeader(), outItem(), AtomFeed::outItem(), WebInstallerOutput::outputFooter(), WebInstallerOutput::outputHeader(), WebInstallerOutput::outputShortHeader(), CoreParserFunctions::pagesincategory(), CategoryViewer::pagingLinks(), BacklinkCache::partition(), SpecialJavaScriptTest::plainQUnit(), FileDeleteForm::prepareMessage(), ErrorPageError::report(), EnotifNotifyJob::run(), HTMLCacheUpdateJob::run(), RefreshLinksJob2::run(), UploadFromUrlJob::run(), RefreshLinksJob::run(), DoubleRedirectJob::run(), TitlePermissionTest::runCSSandJSPermissions(), TitlePermissionTest::runGroupPermissions(), FileDeleteForm::setHeaders(), TitlePermissionTest::setTitle(), RequestContext::setTitle(), DerivativeContext::setTitle(), WikiRevision::setTitle(), ArticleTest::setUp(), ParserPreloadTest::setUp(), LogFormatterTest::setUp(), TitlePermissionTest::setUp(), Sanitizer::setupAttributeWhitelist(), RevDel_List::setVisibility(), FileDeleteForm::showForm(), FileDeleteForm::showLogEntries(), ArticleTest::tearDown(), ParserPreloadTest::tearDown(), TitlePermissionTest::testActionPermissions(), TitlePermissionTest::testCascadingSourcesRestrictions(), LogFormatterTest::testLogParamsTypeRaw(), LogFormatterTest::testLogParamsTypeTitleLink(), LogFormatterTest::testNormalLogParams(), TitlePermissionTest::testPageRestrictions(), TitlePermissionTest::testQuickPermissions(), TitlePermissionTest::testSpecialsAndNSPermissions(), SideBarTest::testTrickyPipe(), TitlePermissionTest::testUserBlock(), Job::toString(), PageArchive::undelete(), PageArchive::undeleteRevisions(), ApiWatch::watchTitle(), wfPHPVersionError(), and wfThumbError().

◆ transformed

</td><td> this can then be imported into another wiki running MediaWiki transformed

Definition at line 1488 of file All_system_messages.txt.

◆ User

◆ well

page as well

Definition at line 2732 of file All_system_messages.txt.

Referenced by CheckLanguageCLI::help().

◆ will

◆ yourself

</td><td> &</td><td> t want your writing to be edited mercilessly and redistributed at then don& You are also promising us that you wrote this yourself

Definition at line 914 of file All_system_messages.txt.

data
and how to run hooks for an and one after Each event has a preferably in CamelCase For ArticleDelete hook A clump of code and data that should be run when an event happens This can be either a function and a chunk of data
Definition: hooks.txt:6
of
globals txt Globals are evil The original MediaWiki code relied on globals for processing context far too often MediaWiki development since then has been a story of slowly moving context out of global variables and into objects Storing processing context in object member variables allows those objects to be reused in a much more flexible way Consider the elegance of
Definition: globals.txt:10
is
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
wiki
Prior to maintenance scripts were a hodgepodge of code that had no cohesion or formal method of action Beginning maintenance scripts have been cleaned up to use a unified class Directory structure How to run a script How to write your own DIRECTORY STRUCTURE The maintenance directory of a MediaWiki installation contains several all of which have unique purposes HOW TO RUN A SCRIPT Ridiculously just call php someScript php that s in the top level maintenance directory if not default wiki
Definition: maintenance.txt:1
quot
</td >< td > &</td >< td > & quot
Definition: All_system_messages.txt:330
pages
The ContentHandler facility adds support for arbitrary content types on wiki pages
Definition: contenthandler.txt:1
Action
Actions are things which can be done to pages (edit, delete, rollback, etc).
Definition: Action.php:37
conversion
This document describes the state of Postgres support in and is fairly well maintained The main code is very well while extensions are very hit and miss it is probably the most supported database after MySQL Much of the work in making MediaWiki database agnostic came about through the work of creating Postgres as and are nearing end of but without copying over all the usage comments General notes on the conversion
Definition: postgres.txt:22
title
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
page
target page
Definition: All_system_messages.txt:1267
form
null means default in associative array form
Definition: hooks.txt:1530
database
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 database
Definition: design.txt:12
will
</td >< td > &</td >< td > t want your writing to be edited mercilessly and redistributed at will
Definition: All_system_messages.txt:914
below
See &</td >< td > &Fill in a specific reason below(for example, citing particular pages that were vandalized).</td >< td >
Definition: All_system_messages.txt:649
set
it s the revision text itself In either if gzip is set
Definition: hooks.txt:2118
some
I won t presume to tell you how to I m just describing the methods I chose to use for myself If you do choose to follow these it will probably be easier for you to collaborate with others on the but if you want to contribute without by all means do which work well I also use K &R brace matching style I know that s a religious issue for some
Definition: design.txt:79
up
static configuration should be added through ResourceLoaderGetConfigVars instead can be used to get the real title after the basic globals have been set up
Definition: hooks.txt:1684
following
Prior to maintenance scripts were a hodgepodge of code that had no cohesion or formal method of action Beginning maintenance scripts have been cleaned up to use a unified class Directory structure How to run a script How to write your own DIRECTORY STRUCTURE The maintenance directory of a MediaWiki installation contains several all of which have unique purposes HOW TO RUN A SCRIPT Ridiculously just call php someScript php that s in the top level maintenance directory if not default do this many per batch HOW TO WRITE YOUR OWN Make a file in the maintenance directory called myScript php or something In write the following
Definition: maintenance.txt:1
only
published in in Madrid In the first edition of the Vocabolario for was published In in Rotterdam was the Dictionnaire Universel ! html< p > The first monolingual dictionary written in a Romance language was< i > Sebastián Covarrubias</i >< i > Tesoro de la lengua castellana o published in in Madrid In the first edition of the< i > Vocabolario dell< a href="/index.php?title=Accademia_della_Crusca&amp;action=edit&amp;redlink=1" class="new" title="Accademia della Crusca (page does not exist)"> Accademia della Crusca</a ></i > for was published In in Rotterdam was the< i > Dictionnaire Universel</i ></p > ! end ! test Italics and ! wikitext foo ! html< p >< i > foo</i ></p > !end ! test Italics and ! wikitext foo ! html< p >< i > foo</i ></p > !end ! test Italics and ! wikitext foo ! html< p >< i > foo</i ></p > !end ! test Italics and ! wikitext foo ! html php< p >< i > foo</i ></p > ! html parsoid< p >< i > foo</i >< b ></b ></p > !end ! test Italics and ! wikitext foo ! html< p >< i > foo</i ></p > !end ! test Italics and ! wikitext foo ! html< p >< b > foo</b ></p > !end ! test Italics and ! wikitext foo ! html< p >< b > foo</b ></p > !end ! test Italics and ! wikitext foo ! html php< p >< b > foo</b ></p > ! html parsoid< p >< b > foo</b >< i ></i ></p > !end ! test Italics and ! wikitext foo ! html< p >< i > foo</i ></p > !end ! test Italics and ! wikitext foo ! html< p >< b > foo</b ></p > !end ! test Italics and ! wikitext foo ! html< p >< b > foo</b ></p > !end ! test Italics and ! wikitext foo ! html php< p >< b > foo</b ></p > ! html parsoid< p >< b > foo</b >< i ></i ></p > !end ! test Italics and ! options ! wikitext foo ! html< p >< b >< i > foo</i ></b ></p > !end ! test Italics and ! wikitext foo ! html< p >< i >< b > foo</b ></i ></p > !end ! test Italics and ! wikitext foo ! html< p >< i >< b > foo</b ></i ></p > !end ! test Italics and ! wikitext foo ! html< p >< i >< b > foo</b ></i ></p > !end ! test Italics and ! wikitext foo bar ! html< p >< i > foo< b > bar</b ></i ></p > !end ! test Italics and ! wikitext foo bar ! html< p >< i > foo< b > bar</b ></i ></p > !end ! test Italics and ! wikitext foo bar ! html< p >< i > foo< b > bar</b ></i ></p > !end ! test Italics and ! wikitext foo bar ! html php< p >< b > foo</b > bar</p > ! html parsoid< p >< b > foo</b > bar< i ></i ></p > !end ! test Italics and ! wikitext foo bar ! html php< p >< b > foo</b > bar</p > ! html parsoid< p >< b > foo</b > bar< b ></b ></p > !end ! test Italics and ! wikitext this is about foo s family ! html< p >< i > this is about< b > foo s family</b ></i ></p > !end ! test Italics and ! wikitext this is about foo s family ! html< p >< i > this is about< b > foo s</b > family</i ></p > !end ! test Italics and ! wikitext this is about foo s family ! html< p >< b > this is about< i > foo</i ></b >< i > s family</i ></p > !end ! test Italics and ! options ! wikitext this is about foo s family ! html< p >< i > this is about</i > foo< b > s family</b ></p > !end ! test Italics and ! wikitext this is about foo s family ! html< p >< b > this is about< i > foo s</i > family</b ></p > !end ! test Italicized possessive ! wikitext The s talk page ! html< p > The< i >< a href="/wiki/Main_Page" title="Main Page"> Main Page</a ></i > s talk page</p > ! end ! test Parsoid only
Definition: parserTests.txt:396
text
This list may contain false positives That usually means there is additional text with links below the first Each row contains links to the first and second as well as the first line of the second redirect text
Definition: All_system_messages.txt:1267
it
=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
in
Prior to maintenance scripts were a hodgepodge of code that had no cohesion or formal method of action Beginning in
Definition: maintenance.txt:1
editing
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 editing
Definition: skin.txt:10
that
deferred txt A few of the database updates required by various functions here can be deferred until after the result page is displayed to the user For updating the view updating the linked to tables after a etc PHP does not yet have any way to tell the server to actually return and disconnect while still running these but it might have such a feature in the future We handle these by creating a deferred update object and putting those objects on a global then executing the whole list after the page is displayed We don t do anything smart like collating updates to the same table or such because the list is almost always going to have just one item on if that
Definition: deferred.txt:11
complete
Returning false makes less sense for events where the action is complete
Definition: hooks.txt:198
name
Your real name
Definition: All_system_messages.txt:1355
redirect
This list may contain false positives That usually means there is additional text with links below the first Each row contains links to the first and second redirect
Definition: All_system_messages.txt:1267