Go to the documentation of this file.
96 $params[
'redisConfig'][
'serializer'] =
'none';
97 $this->
server = $params[
'redisServer'];
98 $this->compression = isset(
$params[
'compression'] ) ?
$params[
'compression'] :
'none';
100 $this->maximumPeriodicTaskSeconds = isset(
$params[
'maximumPeriodicTaskSeconds'] ) ?
101 $params[
'maximumPeriodicTaskSeconds'] :
null;
105 return array(
'timestamp',
'fifo' );
133 return $conn->lSize( $this->
getQueueKey(
'l-unclaimed' ) );
134 }
catch ( RedisException
$e ) {
145 if ( $this->claimTTL <= 0 ) {
150 $conn->multi( Redis::PIPELINE );
152 $conn->zSize( $this->
getQueueKey(
'z-abandoned' ) );
154 return array_sum( $conn->exec() );
155 }
catch ( RedisException
$e ) {
166 if ( !$this->checkDelay ) {
171 return $conn->zSize( $this->
getQueueKey(
'z-delayed' ) );
172 }
catch ( RedisException
$e ) {
183 if ( $this->claimTTL <= 0 ) {
188 return $conn->zSize( $this->
getQueueKey(
'z-abandoned' ) );
189 }
catch ( RedisException
$e ) {
204 foreach ( $jobs
as $job ) {
206 if ( strlen( $item[
'sha1'] ) ) {
207 $items[$item[
'sha1']] = $item;
209 $items[$item[
'uuid']] = $item;
213 if ( !count( $items ) ) {
220 if (
$flags & self::QOS_ATOMIC ) {
221 $batches =
array( $items );
223 $batches = array_chunk( $items, 500 );
227 foreach ( $batches
as $itemBatch ) {
228 $added = $this->
pushBlobs( $conn, $itemBatch );
229 if ( is_int( $added ) ) {
232 $failed += count( $itemBatch );
236 wfDebugLog(
'JobQueueRedis',
"Could not insert {$failed} {$this->type} job(s)." );
242 count( $items ) -
$failed - $pushed, $this->
wiki );
243 }
catch ( RedisException
$e ) {
258 foreach ( $items
as $item ) {
259 $args[] = (string)$item[
'uuid'];
260 $args[] = (string)$item[
'sha1'];
261 $args[] = (string)$item[
'rtimestamp'];
266 local kUnclaimed, kSha1ById, kIdBySha1, kDelayed, kData = unpack(KEYS)
267 if #ARGV % 4 ~= 0
then return redis.error_reply(
'Unmatched arguments') end
270 local id,sha1,rtimestamp,blob = ARGV[i],ARGV[i+1],ARGV[i+2],ARGV[i+3]
271 if sha1 ==
'' or redis.call(
'hExists',kIdBySha1,sha1) == 0
then
272 if 1*rtimestamp > 0
then
273 -- Insert into delayed queue (
release time
as score)
274 redis.call(
'zAdd',kDelayed,rtimestamp,
id)
276 -- Insert into unclaimed queue
277 redis.call(
'lPush',kUnclaimed,
id)
280 redis.call(
'hSet',kSha1ById,
id,sha1)
281 redis.call(
'hSet',kIdBySha1,sha1,
id)
283 redis.call(
'hSet',kData,
id,blob)
289 return $conn->
luaEval( $script,
300 5 # number
of first argument(s)
that are keys
309 protected function doPop() {
314 if ( $this->checkDelay && mt_rand( 0, 9 ) == 0 ) {
321 if ( $this->claimTTL > 0 ) {
323 if ( mt_rand( 0, 99 ) == 0 ) {
330 if (
$blob ===
false ) {
336 if ( $item ===
false ) {
337 wfDebugLog(
'JobQueueRedis',
"Could not unserialize {$this->type} job." );
344 }
catch ( RedisException
$e ) {
359 local kUnclaimed, kSha1ById, kIdBySha1, kData = unpack(KEYS)
360 -- Pop an item
off the queue
361 local
id = redis.call(
'rpop',kUnclaimed)
362 if not
id then return false end
363 -- Get the job
data and
remove it
364 local item = redis.call(
'hGet',kData,
id)
365 redis.call(
'hDel',kData,
id)
366 -- Allow
new duplicates
of this job
367 local sha1 = redis.call(
'hGet',kSha1ById,
id)
368 if sha1
then redis.call(
'hDel',kIdBySha1,sha1) end
369 redis.call(
'hDel',kSha1ById,
id)
370 -- Return the job
data
373 return $conn->
luaEval( $script,
380 4 # number
of first argument(s)
that are keys
392 local kUnclaimed, kSha1ById, kIdBySha1, kClaimed, kAttempts, kData = unpack(KEYS)
393 -- Pop an item
off the queue
394 local
id = redis.call(
'rPop',kUnclaimed)
395 if not
id then return false end
396 -- Allow
new duplicates
of this job
397 local sha1 = redis.call(
'hGet',kSha1ById,
id)
398 if sha1
then redis.call(
'hDel',kIdBySha1,sha1) end
399 redis.call(
'hDel',kSha1ById,
id)
400 -- Mark the jobs
as claimed and
return it
401 redis.call(
'zAdd',kClaimed,ARGV[1],
id)
402 redis.call(
'hIncrBy',kAttempts,
id,1)
403 return redis.call(
'hGet',kData,
id)
405 return $conn->
luaEval( $script,
413 time(), # ARGV[1] (injected to be replication-safe)
415 6 # number
of first argument(s)
that are keys
426 if ( !isset(
$job->metadata[
'uuid'] ) ) {
427 throw new MWException(
"Job of type '{$job->getType()}' has no UUID." );
429 if ( $this->claimTTL > 0 ) {
434 local kClaimed, kAttempts, kData = unpack(KEYS)
435 -- Unmark the job
as claimed
436 redis.call(
'zRem',kClaimed,ARGV[1])
437 redis.call(
'hDel',kAttempts,ARGV[1])
438 -- Delete the job
data itself
439 return redis.call(
'hDel',kData,ARGV[1])
446 $job->metadata[
'uuid'] # ARGV[1]
448 3 # number
of first argument(s)
that are keys
452 wfDebugLog(
'JobQueueRedis',
"Could not acknowledge {$this->type} job." );
456 }
catch ( RedisException
$e ) {
471 if ( !
$job->hasRootJobParams() ) {
472 throw new MWException(
"Cannot register root job; missing parameters." );
486 return $conn->set(
$key,
$params[
'rootJobTimestamp'], self::ROOTJOB_TTL );
487 }
catch ( RedisException
$e ) {
499 if ( !
$job->hasRootJobParams() ) {
508 }
catch ( RedisException
$e ) {
522 static $props =
array(
'l-unclaimed',
'z-claimed',
'z-abandoned',
523 'z-delayed',
'h-idBySha1',
'h-sha1ById',
'h-attempts',
'h-data' );
528 foreach ( $props
as $prop ) {
533 }
catch ( RedisException
$e ) {
548 $conn->lRange( $this->getQueueKey(
'l-unclaimed' ), 0, -1 ),
549 function ( $uid ) use ( $that, $conn ) {
550 return $that->getJobFromUidInternal( $uid, $conn );
553 return is_object(
$job );
556 }
catch ( RedisException
$e ) {
571 $conn->zRange( $this->getQueueKey(
'z-delayed' ), 0, -1 ),
572 function ( $uid ) use ( $that, $conn ) {
573 return $that->getJobFromUidInternal( $uid, $conn );
576 return is_object(
$job );
579 }
catch ( RedisException
$e ) {
594 $types = array_values( $types );
597 $conn->multi( Redis::PIPELINE );
599 $conn->lSize( $this->
getQueueKey(
'l-unclaimed', $type ) );
601 $res = $conn->exec();
602 if ( is_array(
$res ) ) {
604 $sizes[$types[$i]] =
$size;
607 }
catch ( RedisException
$e ) {
624 $data = $conn->hGet( $this->
getQueueKey(
'h-data' ), $uid );
625 if ( $data ===
false ) {
628 $item = $this->
unserialize( $conn->hGet( $this->getQueueKey(
'h-data' ), $uid ) );
629 if ( !is_array( $item ) ) {
630 throw new MWException(
"Could not find job with ID '$uid'." );
634 $job->metadata[
'uuid'] = $item[
'uuid'];
637 }
catch ( RedisException
$e ) {
660 local kClaimed, kAttempts, kUnclaimed, kData, kAbandoned, kDelayed = unpack(KEYS)
661 local released,abandoned,pruned,undelayed = 0,0,0,0
662 -- Get all non-dead jobs
that have an expired claim
on them.
663 -- The score
for each item
is the last claim timestamp (UNIX).
664 local staleClaims = redis.call(
'zRangeByScore',kClaimed,0,ARGV[1])
665 for k,
id in ipairs(staleClaims)
do
666 local timestamp = redis.call(
'zScore',kClaimed,
id)
667 local attempts = redis.call(
'hGet',kAttempts,
id)
668 if attempts < ARGV[3]
then
669 -- Claim expired and retries left: re-enqueue the job
670 redis.call(
'lPush',kUnclaimed,
id)
671 redis.call(
'hIncrBy',kAttempts,
id,1)
672 released = released + 1
674 -- Claim expired and no retries left: mark the job
as dead
675 redis.call(
'zAdd',kAbandoned,timestamp,
id)
676 abandoned = abandoned + 1
678 redis.call(
'zRem',kClaimed,
id)
680 -- Get all
of the dead jobs
that have been marked
as dead
for too long.
681 -- The score
for each item
is the last claim timestamp (UNIX).
682 local deadClaims = redis.call(
'zRangeByScore',kAbandoned,0,ARGV[2])
683 for k,
id in ipairs(deadClaims)
do
684 -- Stale and out
of retries:
remove any traces
of the job
685 redis.call(
'zRem',kAbandoned,
id)
686 redis.call(
'hDel',kAttempts,
id)
687 redis.call(
'hDel',kData,
id)
690 -- Get the
list of ready delayed jobs, sorted by readiness (UNIX timestamp)
691 local ids = redis.call(
'zRangeByScore',kDelayed,0,ARGV[4])
692 -- Migrate the jobs
from the
"delayed" set to the
"unclaimed" list
693 for k,
id in ipairs(ids)
do
694 redis.call(
'lPush',kUnclaimed,
id)
695 redis.call(
'zRem',kDelayed,
id)
698 return {released,abandoned,pruned,undelayed}
708 $now - $this->claimTTL, # ARGV[1]
709 $now - self::MAX_AGE_PRUNE, # ARGV[2]
710 $this->maxTries, # ARGV[3]
713 6 # number
of first argument(s)
that are keys
716 list( $released, $abandoned, $pruned, $undelayed ) =
$res;
717 $count += $released + $pruned + $undelayed;
721 }
catch ( RedisException
$e ) {
732 $periods =
array( 3600 );
733 if ( $this->claimTTL > 0 ) {
734 $periods[] = ceil( $this->claimTTL / 2 );
736 if ( $this->checkDelay ) {
739 $period = min( $periods );
740 $period = max( $period, 30 );
742 if ( $this->maximumPeriodicTaskSeconds !==
null ) {
743 $period = min( $period, $this->maximumPeriodicTaskSeconds );
746 'recyclePruneAndUndelayJobs' =>
array(
747 'callback' =>
array( $this,
'recyclePruneAndUndelayJobs' ),
760 'type' =>
$job->getType(),
761 'namespace' =>
$job->getTitle()->getNamespace(),
762 'title' =>
$job->getTitle()->getDBkey(),
763 'params' =>
$job->getParams(),
765 'rtimestamp' =>
$job->getReleaseTimestamp() ?: 0,
768 'sha1' =>
$job->ignoreDuplicates()
771 'timestamp' => time()
783 $job->metadata[
'uuid'] = $fields[
'uuid'];
797 if ( $this->compression ===
'gzip'
798 && strlen(
$blob ) >= 1024
799 && function_exists(
'gzdeflate' )
804 return ( strlen( $blobz ) < strlen(
$blob ) ) ? $blobz :
$blob;
816 if ( is_object( $fields ) ) {
817 if ( $fields->enc ===
'gzip' && function_exists(
'gzinflate' ) ) {
818 $fields =
unserialize( gzinflate( $fields->blob ) );
824 return is_array( $fields ) ? $fields :
false;
834 $conn = $this->redisPool->getConnection( $this->
server );
848 $this->redisPool->handleError( $conn,
$e );
849 throw new JobQueueError(
"Redis server error: {$e->getMessage()}\n" );
860 if ( strlen( $this->
key ) ) {
doDeduplicateRootJob(Job $job)
Convenience class for generating iterators from iterators.
static & makeTitle( $ns, $title, $fragment='', $interwiki='')
Create a new Title from a namespace index and a DB key.
globals will be eliminated from MediaWiki replaced by an application object which would be passed to constructors Whether that would be an convenient solution remains to be but certainly PHP makes such object oriented programming models easier than they were in previous versions For the time being MediaWiki programmers will have to work in an environment with some global context At the time of globals were initialised on startup by MediaWiki of these were configuration which are documented in DefaultSettings php There is no comprehensive documentation for the remaining however some of the most important ones are listed below They are typically initialised either in index php or in Setup php For a description of the see design txt $wgTitle Title object created from the request URL $wgOut OutputPage object for HTTP response $wgUser User object for the user associated with the current request $wgLang Language object selected by user preferences $wgContLang Language object associated with the wiki being viewed $wgParser Parser object Parser extensions register their hooks here $wgRequest WebRequest object
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
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
static singleton(array $options)
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
static incrStats( $key, $type, $delta=1, $wiki=null)
Call wfIncrStats() for the queue overall and for the queue type.
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
__construct(array $params)
@params include:
string $server
Server address *.
string $compression
Compression method to use *.
null int $maximumPeriodicTaskSeconds
maximum seconds between execution of periodic tasks.
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
wfDebugLog( $logGroup, $text, $dest='all')
Send a line to a supplementary debug log file, if configured, or main debug log if not.
doBatchPush(array $jobs, $flags)
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 release
doGetSiblingQueuesWithJobs(array $types)
getJobFromFields(array $fields)
wfSplitWikiID( $wiki)
Split a wiki ID into DB name and table prefix.
it s the revision text itself In either if gzip is the revision text is gzipped $flags
recyclePruneAndUndelayJobs()
Recycle or destroy any jobs that have been claimed for too long and release any ready delayed jobs in...
getJobFromUidInternal( $uid, RedisConnRef $conn)
This function should not be called outside JobQueueRedis.
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 in any and then calling but I prefer the flexibility This should also do the output encoding The system allocates a global one in $wgOut Title Represents the title of an and does all the work of translating among various forms such as plain database key
static newRawUUIDv4( $flags=0)
Return an RFC4122 compliant v4 UUID.
Class to both describe a background job and handle jobs.
getNewJobFields(IJobSpecification $job)
the array() calling protocol came about after MediaWiki 1.4rc1.
List of Api Query prop modules.
optimalOrder()
Get the default queue order to use if configuration does not specify one.
wfForeignMemcKey( $db, $prefix)
Get a cache key for a foreign DB.
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 list
processing should stop and the error should be shown to the user * false
getCoalesceLocationInternal()
Do not use this function outside of JobQueue/JobQueueGroup.
static makeTitleSafe( $ns, $title, $fragment='', $interwiki='')
Create a new Title from a namespace index and a DB key.
Helper class to manage Redis connections.
string $key
Key to prefix the queue keys with (used for testing) *.
presenting them properly to the user as errors is done by the caller $title
getConnection()
Get a connection to the server that handles all sub-queues for this queue.
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 so if you want to use a style that puts opening braces on the next that s OK too
pushBlobs(RedisConnRef $conn, array $items)
luaEval( $script, array $params, $numKeys)
supportedOrders()
Get the allowed queue orders for configuration validation.
getQueueKey( $prop, $type=null)
static factory( $command, Title $title, $params=false)
Create the appropriate object to handle a specific job.
throwRedisException(RedisConnRef $conn, $e)
Use of locking define a new flag for $wgAntiLockFlags which allows them to be turned off
=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
getRootJobCacheKey( $signature)
popAndDeleteBlob(RedisConnRef $conn)
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 but these can almost always be programmed around *Although Postgres has a true BOOLEAN type
RedisConnectionPool $redisPool
Prior to maintenance scripts were a hodgepodge of code that had no cohesion or formal method of action Beginning in
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 on
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
wfBaseConvert( $input, $sourceBase, $destBase, $pad=1, $lowercase=true, $engine='auto')
Convert an arbitrarily-long digit string from one numeric base to another, optionally zero-padding to...
supportsDelayedJobs()
Find out if delayed jobs are supported for configuration validation.
if(count( $args)< 1) $job
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 then
doIsRootJobOldDuplicate(Job $job)
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
Class to handle enqueueing and running of background jobs.
Helper class to handle automatically marking connectons as reusable (via RAII pattern)
Please log in again after you receive it</td >< td > s a saved copy from
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
doGetSiblingQueueSizes(array $types)
popAndAcquireBlob(RedisConnRef $conn)
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
Job queue task description interface.
Class to handle job queues stored in Redis.