92 if (
$path[0] !==
'/' ) {
98 if ( strpos(
$path,
'$1' ) ===
false ) {
99 if ( substr(
$path, -1 ) !==
'/' ) {
108 if ( !isset(
$params[
'title'] ) && strpos(
$path,
'$1' ) !==
false ) {
118 foreach (
$params as $paramName => $paramData ) {
119 if ( is_string( $paramData ) ) {
120 if ( preg_match(
'/\$(\d+|key)/u', $paramData ) ) {
121 $paramArrKey =
'pattern';
125 $paramArrKey =
'value';
128 $paramArrKey => $paramData
135 foreach (
$options as $optionName => $optionData ) {
136 if ( preg_match(
'/^\$\d+$/u', $optionName ) ) {
137 if ( !is_array( $optionData ) ) {
138 $options[$optionName] = [ $optionData ];
149 $pattern->weight = self::makeWeight( $pattern );
150 $this->patterns[] = $pattern;
161 if ( is_array(
$path ) ) {
162 foreach (
$path as $key => $onePath ) {
188 foreach ( $this->patterns
as $key => $pattern ) {
189 $weights[$key] = $pattern->weight;
191 array_multisort( $weights, SORT_DESC, SORT_NUMERIC, $this->patterns );
199 # Start with a weight of 0
203 $path = explode(
'/', $pattern->path );
205 # For each level of the path
207 if ( preg_match(
'/^\$(\d+|key)$/u', $piece ) ) {
208 # For a piece that is only a $1 variable add 1 points of weight
210 } elseif ( preg_match(
'/\$(\d+|key)/u', $piece ) ) {
211 # For a piece that simply contains a $1 variable add 2 points of weight
214 # For a solid piece add a full 3 points of weight
219 foreach ( $pattern->options
as $key => $option ) {
220 if ( preg_match(
'/^\$\d+$/u', $key ) ) {
221 # Add 0.5 for restrictions to values
222 # This way given two separate "/$2/$1" patterns the
223 # one with a limited set of $2 values will dominate
224 # the one that'll match more loosely
245 foreach ( $this->patterns
as $pattern ) {
266 $regexp = preg_quote( $pattern->path,
'#' );
268 $regexp = preg_replace(
'#\\\\\$1#u',
'(?P<par1>.*)', $regexp );
270 $regexp = preg_replace(
'#\\\\\$(\d+)#u',
'(?P<par$1>.+?)', $regexp );
271 $regexp =
"#^{$regexp}$#";
277 if ( preg_match( $regexp,
$path, $m ) ) {
280 foreach ( $pattern->options
as $key => $option ) {
281 if ( preg_match(
'/^\$\d+$/u', $key ) ) {
282 $n = intval( substr( $key, 1 ) );
283 $value = rawurldecode( $m[
"par{$n}"] );
284 if ( !in_array(
$value, $option ) ) {
293 foreach ( $m
as $matchKey => $matchValue ) {
294 if ( preg_match(
'/^par\d+$/u', $matchKey ) ) {
295 $n = intval( substr( $matchKey, 3 ) );
296 $data[
'$' . $n] = rawurldecode( $matchValue );
300 if ( isset( $pattern->key ) ) {
301 $data[
'$key'] = $pattern->key;
305 foreach ( $pattern->params
as $paramName => $paramData ) {
309 if ( preg_match(
'/^data:/u', $paramName ) ) {
311 $key = substr( $paramName, 5 );
317 if ( isset( $paramData[
'value'] ) ) {
319 $value = $paramData[
'value'];
320 } elseif ( isset( $paramData[
'pattern'] ) ) {
322 $value = $paramData[
'pattern'];
324 $replacer->params = $m;
325 if ( isset( $pattern->key ) ) {
326 $replacer->key = $pattern->key;
344 if ( isset( $pattern->options[
'callback'] ) ) {
345 call_user_func_array( $pattern->options[
'callback'], [ &
$matches, $data ] );
370 $this->error =
false;
371 $value = preg_replace_callback(
'/\$(\d+|key)/u', [ $this,
'callback' ],
$value );
372 if ( $this->error ) {
383 if ( $m[1] ==
"key" ) {
384 if ( is_null( $this->
key ) ) {
391 if ( !isset( $this->params[
"par$d"] ) ) {
395 return rawurldecode( $this->params[
"par$d"] );
addStrict($path, $params=[], $options=[])
Add a new path pattern to the path router with the strict option on.
add($path, $params=[], $options=[])
Add a new path pattern to the path router.
static extractTitle($path, $pattern)
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
doAdd($path, $params, $options, $key=null)
Protected helper to do the actual bulk work of adding a single pattern.
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
this hook is for auditing only RecentChangesLinked and Watchlist RecentChangesLinked and Watchlist e g Watchlist removed from all revisions and log entries to which it was applied This gives extensions a chance to take it off their books as the deletion has already been partly carried out by this point or something similar the user will be unable to create the tag set and then return false from the hook function Ensure you consume the ChangeTagAfterDelete hook to carry out custom deletion actions as context called by AbstractContent::getParserOutput May be used to override the normal model specific rendering of page content as context as context $options
replace($value)
Replace keys inside path router patterns with text.
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
injection txt This is an overview of how MediaWiki makes use of dependency injection The design described here grew from the discussion of RFC T384 The term dependency this means that anything an object needs to operate should be injected from the the object itself should only know narrow no concrete implementation of the logic it relies on The requirement to inject everything typically results in an architecture that based on two main types of and essentially stateless service objects that use other service objects to operate on the value objects As of the beginning MediaWiki is only starting to use the DI approach Much of the code still relies on global state or direct resulting in a highly cyclical dependency which acts as the top level factory for services in MediaWiki which can be used to gain access to default instances of various services MediaWikiServices however also allows new services to be defined and default services to be redefined Services are defined or redefined by providing a callback the instantiator that will return a new instance of the service When it will create an instance of MediaWikiServices and populate it with the services defined in the files listed by thereby bootstrapping the DI framework Per $wgServiceWiringFiles lists includes ServiceWiring php
sortByWeight()
Protected helper to re-sort our patterns so that the most specific (most heavily weighted) patterns a...
parse($path)
Parse a path and return the query matches for the path.
static makeWeight($pattern)