MediaWiki  1.23.3
Defines.php
Go to the documentation of this file.
1 <?php
34 define( 'MW_SPECIALPAGE_VERSION', 2 );
35 
39 define( 'DBO_DEBUG', 1 );
40 define( 'DBO_NOBUFFER', 2 );
41 define( 'DBO_IGNORE', 4 );
42 define( 'DBO_TRX', 8 ); // automatically start transaction on first query
43 define( 'DBO_DEFAULT', 16 );
44 define( 'DBO_PERSISTENT', 32 );
45 define( 'DBO_SYSDBA', 64 ); //for oracle maintenance
46 define( 'DBO_DDLMODE', 128 ); // when using schema files: mostly for Oracle
47 define( 'DBO_SSL', 256 );
48 define( 'DBO_COMPRESS', 512 );
55 define( 'DB_SLAVE', -1 ); # Read from the slave (or only server)
56 define( 'DB_MASTER', -2 ); # Write to master (or only server)
57 
59 # Obsolete aliases
60 define( 'DB_READ', -1 );
61 define( 'DB_WRITE', -2 );
62 define( 'DB_LAST', -3 ); # deprecated since 2008, usage throws exception
63 
67 define( 'NS_MEDIA', -2 );
68 define( 'NS_SPECIAL', -1 );
79 define( 'NS_MAIN', 0 );
80 define( 'NS_TALK', 1 );
81 define( 'NS_USER', 2 );
82 define( 'NS_USER_TALK', 3 );
83 define( 'NS_PROJECT', 4 );
84 define( 'NS_PROJECT_TALK', 5 );
85 define( 'NS_FILE', 6 );
86 define( 'NS_FILE_TALK', 7 );
87 define( 'NS_MEDIAWIKI', 8 );
88 define( 'NS_MEDIAWIKI_TALK', 9 );
89 define( 'NS_TEMPLATE', 10 );
90 define( 'NS_TEMPLATE_TALK', 11 );
91 define( 'NS_HELP', 12 );
92 define( 'NS_HELP_TALK', 13 );
93 define( 'NS_CATEGORY', 14 );
94 define( 'NS_CATEGORY_TALK', 15 );
95 
104 define( 'NS_IMAGE', NS_FILE );
105 define( 'NS_IMAGE_TALK', NS_FILE_TALK );
111 define( 'CACHE_ANYTHING', -1 ); // Use anything, as long as it works
112 define( 'CACHE_NONE', 0 ); // Do not cache
113 define( 'CACHE_DB', 1 ); // Store cache objects in the DB
114 define( 'CACHE_MEMCACHED', 2 ); // MemCached, must specify servers in $wgMemCacheServers
115 define( 'CACHE_ACCEL', 3 ); // APC, XCache or WinCache
122 // unknown format
123 define( 'MEDIATYPE_UNKNOWN', 'UNKNOWN' );
124 // some bitmap image or image source (like psd, etc). Can't scale up.
125 define( 'MEDIATYPE_BITMAP', 'BITMAP' );
126 // some vector drawing (SVG, WMF, PS, ...) or image source (oo-draw, etc). Can scale up.
127 define( 'MEDIATYPE_DRAWING', 'DRAWING' );
128 // simple audio file (ogg, mp3, wav, midi, whatever)
129 define( 'MEDIATYPE_AUDIO', 'AUDIO' );
130 // simple video file (ogg, mpg, etc;
131 // no not include formats here that may contain executable sections or scripts!)
132 define( 'MEDIATYPE_VIDEO', 'VIDEO' );
133 // Scriptable Multimedia (flash, advanced video container formats, etc)
134 define( 'MEDIATYPE_MULTIMEDIA', 'MULTIMEDIA' );
135 // Office Documents, Spreadsheets (office formats possibly containing apples, scripts, etc)
136 define( 'MEDIATYPE_OFFICE', 'OFFICE' );
137 // Plain text (possibly containing program code or scripts)
138 define( 'MEDIATYPE_TEXT', 'TEXT' );
139 // binary executable
140 define( 'MEDIATYPE_EXECUTABLE', 'EXECUTABLE' );
141 // archive file (zip, tar, etc)
142 define( 'MEDIATYPE_ARCHIVE', 'ARCHIVE' );
148 define( 'AV_NO_VIRUS', 0 ); #scan ok, no virus found
149 define( 'AV_VIRUS_FOUND', 1 ); #virus found!
150 define( 'AV_SCAN_ABORTED', -1 ); #scan aborted, the file is probably immune
151 define( 'AV_SCAN_FAILED', false ); #scan failed (scanner not found or error in scanner)
158 define( 'ALF_PRELOAD_LINKS', 1 ); // unused
159 define( 'ALF_PRELOAD_EXISTENCE', 2 ); // unused
160 define( 'ALF_NO_LINK_LOCK', 4 );
161 define( 'ALF_NO_BLOCK_LOCK', 8 );
168 define( 'MW_DATE_DEFAULT', 'default' );
169 define( 'MW_DATE_MDY', 'mdy' );
170 define( 'MW_DATE_DMY', 'dmy' );
171 define( 'MW_DATE_YMD', 'ymd' );
172 define( 'MW_DATE_ISO', 'ISO 8601' );
178 define( 'RC_EDIT', 0 );
179 define( 'RC_NEW', 1 );
180 define( 'RC_MOVE', 2 ); // obsolete
181 define( 'RC_LOG', 3 );
182 define( 'RC_MOVE_OVER_REDIRECT', 4 ); // obsolete
183 define( 'RC_EXTERNAL', 5 );
189 define( 'EDIT_NEW', 1 );
190 define( 'EDIT_UPDATE', 2 );
191 define( 'EDIT_MINOR', 4 );
192 define( 'EDIT_SUPPRESS_RC', 8 );
193 define( 'EDIT_FORCE_BOT', 16 );
194 define( 'EDIT_DEFER_UPDATES', 32 );
195 define( 'EDIT_AUTOSUMMARY', 64 );
202 define( 'LIST_COMMA', 0 );
203 define( 'LIST_AND', 1 );
204 define( 'LIST_SET', 2 );
205 define( 'LIST_NAMES', 3 );
206 define( 'LIST_OR', 4 );
212 require_once __DIR__ . '/normal/UtfNormalDefines.php';
213 
225 
230 define( 'OT_HTML', 1 );
231 define( 'OT_WIKI', 2 );
232 define( 'OT_PREPROCESS', 3 );
233 define( 'OT_MSG', 3 ); // b/c alias for OT_PREPROCESS
234 define( 'OT_PLAIN', 4 );
240 define( 'SFH_NO_HASH', 1 );
241 define( 'SFH_OBJECT_ARGS', 2 );
247 define( 'RLH_FOR_UPDATE', 1 );
248 
253 define( 'APCOND_EDITCOUNT', 1 );
254 define( 'APCOND_AGE', 2 );
255 define( 'APCOND_EMAILCONFIRMED', 3 );
256 define( 'APCOND_INGROUPS', 4 );
257 define( 'APCOND_ISIP', 5 );
258 define( 'APCOND_IPINRANGE', 6 );
259 define( 'APCOND_AGE_FROM_EDIT', 7 );
260 define( 'APCOND_BLOCKED', 8 );
261 define( 'APCOND_ISBOT', 9 );
267 define( 'PROTO_HTTP', 'http://' );
268 define( 'PROTO_HTTPS', 'https://' );
269 define( 'PROTO_RELATIVE', '//' );
270 define( 'PROTO_CURRENT', null );
271 define( 'PROTO_CANONICAL', 1 );
272 define( 'PROTO_INTERNAL', 2 );
283 define( 'CONTENT_MODEL_WIKITEXT', 'wikitext' );
284 define( 'CONTENT_MODEL_JAVASCRIPT', 'javascript' );
285 define( 'CONTENT_MODEL_CSS', 'css' );
286 define( 'CONTENT_MODEL_TEXT', 'text' );
296 // wikitext
298 // for js pages
299 define( 'CONTENT_FORMAT_JAVASCRIPT', 'text/javascript' );
300 // for css pages
301 define( 'CONTENT_FORMAT_CSS', 'text/css' );
302 // for future use, e.g. with some plain-html messages.
303 define( 'CONTENT_FORMAT_TEXT', 'text/plain' );
304 // for future use, e.g. with some plain-html messages.
305 define( 'CONTENT_FORMAT_HTML', 'text/html' );
306 // for future use with the api and for extensions
307 define( 'CONTENT_FORMAT_SERIALIZED', 'application/vnd.php.serialized' );
308 // for future use with the api, and for use by extensions
309 define( 'CONTENT_FORMAT_JSON', 'application/json' );
310 // for future use with the api, and for use by extensions
311 define( 'CONTENT_FORMAT_XML', 'application/xml' );
OT_MSG
const OT_MSG
Definition: Defines.php:233
MW_DATE_DMY
const MW_DATE_DMY
Definition: Defines.php:170
MW_SUPPORTS_PARSERFIRSTCALLINIT
const MW_SUPPORTS_PARSERFIRSTCALLINIT
Definition: Defines.php:218
RC_EXTERNAL
const RC_EXTERNAL
Definition: Defines.php:183
DB_MASTER
const DB_MASTER
Definition: Defines.php:56
PROTO_CANONICAL
const PROTO_CANONICAL
Definition: Defines.php:271
APCOND_ISBOT
const APCOND_ISBOT
Definition: Defines.php:261
php
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
CONTENT_FORMAT_HTML
const CONTENT_FORMAT_HTML
Definition: Defines.php:305
PROTO_INTERNAL
const PROTO_INTERNAL
Definition: Defines.php:272
EDIT_FORCE_BOT
const EDIT_FORCE_BOT
Definition: Defines.php:193
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
ALF_PRELOAD_LINKS
const ALF_PRELOAD_LINKS
Definition: Defines.php:158
MW_DATE_YMD
const MW_DATE_YMD
Definition: Defines.php:171
ALF_NO_BLOCK_LOCK
const ALF_NO_BLOCK_LOCK
Definition: Defines.php:161
text
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
ALF_NO_LINK_LOCK
const ALF_NO_LINK_LOCK
Definition: Defines.php:160
CONTENT_MODEL_CSS
const CONTENT_MODEL_CSS
Definition: Defines.php:285
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
RC_MOVE_OVER_REDIRECT
const RC_MOVE_OVER_REDIRECT
Definition: Defines.php:182
RC_LOG
const RC_LOG
Definition: Defines.php:181
RC_MOVE
const RC_MOVE
Definition: Defines.php:180
ALF_PRELOAD_EXISTENCE
const ALF_PRELOAD_EXISTENCE
Definition: Defines.php:159
normal
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 and we might be restricted by PHP settings such as safe mode or open_basedir We cannot assume that the software even has read access anywhere useful Many shared hosts run all users web applications under the same so they can t rely on Unix and must forbid reads to even standard directories like tmp lest users read each others files We cannot assume that the user has the ability to install or run any programs not written as web accessible PHP scripts Since anything that works on cheap shared hosting will work if you have shell or root access MediaWiki s design is based around catering to the lowest common denominator Although we support higher end setups as the way many things work by default is tailored toward shared hosting These defaults are unconventional from the point of view of normal(non-web) applications -- they might conflict with distributors' policies
APCOND_EDITCOUNT
const APCOND_EDITCOUNT
Definition: Defines.php:253
SFH_OBJECT_ARGS
const SFH_OBJECT_ARGS
Definition: Defines.php:241
OT_PREPROCESS
const OT_PREPROCESS
Definition: Defines.php:232
NS_FILE
const NS_FILE
Definition: Defines.php:85
OT_PLAIN
const OT_PLAIN
Definition: Defines.php:234
cssjanus.usage
def usage()
Definition: cssjanus.py:520
RC_EDIT
const RC_EDIT
Definition: Defines.php:178
APCOND_AGE
const APCOND_AGE
Definition: Defines.php:254
CONTENT_FORMAT_CSS
const CONTENT_FORMAT_CSS
Definition: Defines.php:301
CONTENT_MODEL_WIKITEXT
const CONTENT_MODEL_WIKITEXT
Definition: Defines.php:283
default
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 and we might be restricted by PHP settings such as safe mode or open_basedir We cannot assume that the software even has read access anywhere useful Many shared hosts run all users web applications under the same so they can t rely on Unix and must forbid reads to even standard directories like tmp lest users read each others files We cannot assume that the user has the ability to install or run any programs not written as web accessible PHP scripts Since anything that works on cheap shared hosting will work if you have shell or root access MediaWiki s design is based around catering to the lowest common denominator Although we support higher end setups as the way many things work by default is tailored toward shared hosting These defaults are unconventional from the point of view of and they certainly aren t ideal for someone who s installing MediaWiki as MediaWiki does not conform to normal Unix filesystem layout Hopefully we ll offer direct support for standard layouts in the but for now *any change to the location of files is unsupported *Moving things and leaving symlinks will *probably *not break but it is *strongly *advised not to try any more intrusive changes to get MediaWiki to conform more closely to your filesystem hierarchy Any such attempt will almost certainly result in unnecessary bugs The standard recommended location to install relative to the web is it should be possible to enable the appropriate rewrite rules by default
Definition: distributors.txt:53
LIST_AND
const LIST_AND
Definition: Defines.php:203
file
We ve cleaned up the code here by removing clumps of infrequently used code and moving them off somewhere else It s much easier for someone working with this code to see what s _really_ going and make changes or fix bugs In we can take all the code that deals with the little used title reversing we can concentrate it all in an extension file
Definition: hooks.txt:93
CONTENT_FORMAT_XML
const CONTENT_FORMAT_XML
Definition: Defines.php:311
LIST_OR
const LIST_OR
Definition: Defines.php:206
APCOND_AGE_FROM_EDIT
const APCOND_AGE_FROM_EDIT
Definition: Defines.php:259
CONTENT_FORMAT_JSON
const CONTENT_FORMAT_JSON
Definition: Defines.php:309
APCOND_ISIP
const APCOND_ISIP
Definition: Defines.php:257
CONTENT_FORMAT_SERIALIZED
const CONTENT_FORMAT_SERIALIZED
Definition: Defines.php:307
LIST_SET
const LIST_SET
Definition: Defines.php:204
APCOND_BLOCKED
const APCOND_BLOCKED
Definition: Defines.php:260
PROTO_CURRENT
const PROTO_CURRENT
Definition: Defines.php:270
CONTENT_FORMAT_TEXT
const CONTENT_FORMAT_TEXT
Definition: Defines.php:303
MW_SUPPORTS_EDITFILTERMERGED
const MW_SUPPORTS_EDITFILTERMERGED
Unicode and normalisation related.
Definition: Defines.php:217
slave
We use the convention $dbr for read and $dbw for write to help you keep track of whether the database object is a slave(read-only) or a master(read/write). If you write to a slave
OT_WIKI
const OT_WIKI
Definition: Defines.php:231
CONTENT_FORMAT_WIKITEXT
const CONTENT_FORMAT_WIKITEXT
Definition: Defines.php:297
json
The package json
Definition: README.txt:1
PROTO_HTTPS
const PROTO_HTTPS
Definition: Defines.php:268
MW_DATE_DEFAULT
const MW_DATE_DEFAULT
Definition: Defines.php:168
LIST_COMMA
const LIST_COMMA
Definition: Defines.php:202
RLH_FOR_UPDATE
const RLH_FOR_UPDATE
Flags for Parser::replaceLinkHolders.
Definition: Defines.php:247
MW_SUPPORTS_CONTENTHANDLER
const MW_SUPPORTS_CONTENTHANDLER
Definition: Defines.php:220
EDIT_UPDATE
const EDIT_UPDATE
Definition: Defines.php:190
MW_DATE_ISO
const MW_DATE_ISO
Definition: Defines.php:172
PROTO_HTTP
const PROTO_HTTP
Definition: Defines.php:267
PROTO_RELATIVE
const PROTO_RELATIVE
Definition: Defines.php:269
EDIT_DEFER_UPDATES
const EDIT_DEFER_UPDATES
Definition: Defines.php:194
RC_NEW
const RC_NEW
Definition: Defines.php:179
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
SFH_NO_HASH
const SFH_NO_HASH
Definition: Defines.php:240
EDIT_NEW
const EDIT_NEW
Definition: Defines.php:189
APCOND_INGROUPS
const APCOND_INGROUPS
Definition: Defines.php:256
OT_HTML
const OT_HTML
Definition: Defines.php:230
MW_SUPPORTS_RESOURCE_MODULES
const MW_SUPPORTS_RESOURCE_MODULES
Support for $wgResourceModules.
Definition: Defines.php:224
EDIT_AUTOSUMMARY
const EDIT_AUTOSUMMARY
Definition: Defines.php:195
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
https
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 https
Definition: design.txt:12
from
Please log in again after you receive it</td >< td > s a saved copy from
Definition: All_system_messages.txt:3297
CONTENT_MODEL_JAVASCRIPT
const CONTENT_MODEL_JAVASCRIPT
Definition: Defines.php:284
CONTENT_FORMAT_JAVASCRIPT
const CONTENT_FORMAT_JAVASCRIPT
Definition: Defines.php:299
MW_DATE_MDY
const MW_DATE_MDY
Definition: Defines.php:169
EDIT_MINOR
const EDIT_MINOR
Definition: Defines.php:191
EDIT_SUPPRESS_RC
const EDIT_SUPPRESS_RC
Definition: Defines.php:192
LIST_NAMES
const LIST_NAMES
Definition: Defines.php:205
CONTENT_MODEL_TEXT
const CONTENT_MODEL_TEXT
Definition: Defines.php:286
NS_FILE_TALK
const NS_FILE_TALK
Definition: Defines.php:86
MW_SUPPORTS_LOCALISATIONCACHE
const MW_SUPPORTS_LOCALISATIONCACHE
Definition: Defines.php:219
server
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 and we might be restricted by PHP settings such as safe mode or open_basedir We cannot assume that the software even has read access anywhere useful Many shared hosts run all users web applications under the same so they can t rely on Unix and must forbid reads to even standard directories like tmp lest users read each others files We cannot assume that the user has the ability to install or run any programs not written as web accessible PHP scripts Since anything that works on cheap shared hosting will work if you have shell or root access MediaWiki s design is based around catering to the lowest common denominator Although we support higher end setups as the way many things work by default is tailored toward shared hosting These defaults are unconventional from the point of view of and they certainly aren t ideal for someone who s installing MediaWiki as MediaWiki does not conform to normal Unix filesystem layout Hopefully we ll offer direct support for standard layouts in the but for now *any change to the location of files is unsupported *Moving things and leaving symlinks will *probably *not break but it is *strongly *advised not to try any more intrusive changes to get MediaWiki to conform more closely to your filesystem hierarchy Any such attempt will almost certainly result in unnecessary bugs The standard recommended location to install relative to the web is it should be possible to enable the appropriate rewrite rules by if you can reconfigure the web server
Definition: distributors.txt:53
APCOND_EMAILCONFIRMED
const APCOND_EMAILCONFIRMED
Definition: Defines.php:255
APCOND_IPINRANGE
const APCOND_IPINRANGE
Definition: Defines.php:258