Numinix MediaWiki Demo - Recent changes [en]

API/Edit

Admin — Sat, 25 Jul 2026 17:02:15 GMT

Seed from mediawiki.org for Seekmodo connector demo

New page

<languages/>

<translate> '''POST request''' to edit a page.</translate>

__TOC__

<translate>
== API documentation == 
</translate>

<translate>
== Example == 


The sample code in this example is in Python.</translate>
<translate> See <tvar name=1></tvar> for examples and responses in <tvar name=2></tvar>.</translate>

<translate>
=== POST request === 


Making edits, and, indeed, any POST request, is a multi-step process.
</translate>

:1. <translate> Log in, via one of the methods described in <tvar name=1></tvar>.</translate> <translate> Note that while this is required to correctly attribute the edit to its author, many wikis do allow users to edit without registering or logging into an account.</translate> 

:2. <translate> GET a :</translate>
::

:3. <translate> Send a POST request, with the CSRF token, to take action on a page:</translate>
::

<translate> The Response section below is for the final POST request, to take action on the page.</translate>
<translate> See the pages on <tvar name=1></tvar> and <tvar name=2></tvar> for the intermediary JSON responses to earlier steps.</translate>

<translate> Also note that the tokens in the queries on this page are sample values.</translate>
<translate> Actual tokens are unique to each login session and cross-site request.</translate>
<translate> They are included only to demonstrate how to properly format queries.</translate>

<translate>
=== Response === 
</translate>
<div style="width:60%;">
<syntaxhighlight lang="json">
{
"edit": {
"result": "Success",
"pageid": 94542,
"title": "Wikipedia:Sandbox",
"contentmodel": "wikitext",
"oldrevid": 371705,
"newrevid": 371707,
"newtimestamp": "2018-12-18T16:59:42Z"
}
}
</syntaxhighlight>
</div>

<translate>
== Sample code == 
</translate>



/Sample code 1}}

<translate>
== User cases == 

=== Edit conflicts === 
</translate>
<translate> The [[<tvar name=1>#Sample code</tvar>|Python sample]] is a basic implementation of an edit request by a registered user.</translate>
<translate> In real-world scenarios, care should be taken to prevent edit conflicts.</translate>
<translate> These occur when two or more users are attempting to edit the same page at the same time.</translate>

<translate> Conflicts can be prevented by retrieving the last timestamp when we request a CSRF token.</translate>
<translate> Adding <tvar name=1><code>prop=info|revisions</code></tvar> to the CSRF token request in Step 3 allows us to access the timestamp for the last revision.</translate>
<translate> This timestamp will be used as the <tvar name=1><code>basetimestamp</code></tvar> when we make our the edit request.</translate>

<translate> We also need the exact time when we start our edit.</translate>
<translate> This can be retrieved by adding <tvar name=1><code>curtimestamp</code></tvar> to the CSRF request as well.</translate>
<translate> This value will serve as our <tvar name=1><code>starttimestamp</code></tvar>.</translate>

<translate>

Finally, in the actual edit request, set the <tvar name=1><code>basetimestamp</code></tvar> and <tvar name=2><code>starttimestamp</code></tvar> parameters, like so:
</translate>

<translate>
=== Large edits === 
</translate>
<translate> POST requests containing large amounts of text content (8000+ characters) should be sent with <tvar name=1><code>Content-Type: multipart/form-data</code></tvar> indicated in the [[<tvar name=2>devmo:Web/HTTP/Headers</tvar>|header]].</translate>
<translate> Because <tvar name=1><code>multipart/form-data</code></tvar> does not need to add HTML escape characters (i.e., [[<tvar name=2>devmo:Glossary/percent-encoding</tvar>|percent encoding]]) for spaces and punctuation, the amount of data passed will subsequently be much smaller than the percent-encoded equivalent.</translate>

<translate> However, there is still some overhead added by <tvar name=1><code>multipart/form-data</code></tvar> -- roughly, 160 bytes per parameter.</translate>
<translate> For short messages that don't require adding many escape characters, this amount of overhead can be inefficient, and percent-encoding is preferred.</translate><ref>
https://stackoverflow.com/a/4073451
</ref>

<translate>

Note that in our [[<tvar name=1>#Example</tvar>|Python sample code]], the request is percent-encoded by default.
</translate>

<translate> See [[<tvar name=1>devmo:Web/HTTP/Headers/Content-Type</tvar>|the MDN web docs]] for a more technical discussion of content-type and POST requests.</translate>
<translate> See [<tvar name=url>http://docs.python-requests.org/en/master/user/quickstart/#more-complicated-post-requests</tvar> the Python Requests documentation] for how to pass <tvar name=1><code>multipart/form-data</code></tvar> using syntax similar to our Python sample code.</translate>

<translate>
=== CAPTCHAs === 
</translate>
<translate> If the wiki you are targeting uses , your request may return an error containing an ID number and a simple test, such as a question, a math problem, or a URL to an image.</translate>
<translate> In order to complete your edit, you must complete the test, then retry your request with the id and the correct answer(s) appended to the original query string, like so:</translate> <code>captchaid=sampleId&captchaword=answer</code>

<translate> Other CAPTCHA systems and extensions may use different parameters for similar use.</translate>
<translate> In general, use the field names for the ID and test questions as the parameters in your second request.</translate>

<translate>
== Possible errors == 
</translate>
{| class="wikitable sortable"
! <translate> Code</translate> !! <translate> Info</translate>
|-
| notitle ||
|-
| missingparam || appendtextundo|3}}
|-
| notoken ||
|-
| invalidsection ||
|-
| protectedpage || |en | | }}
|-
| cantcreate ||
|-
| cantcreate-anon || <translate> Anonymous users can't create new pages</translate>
|-
| articleexists ||
|-
| noimageredirect-anon ||
|-
| noimageredirect ||
|-
| spamdetected ||
|-
| abusefilter-warning || <translate> This action has been automatically identified as harmful.</translate>
|-
| abusefilter-disallowed || <translate> This action has been automatically identified as harmful, and therefore disallowed.</translate>
|-
| contenttoobig || <br />Where '''bytes''' is the value of .
|-
| noedit-anon ||
|-
| noedit ||
|-
| pagedeleted ||
|-
| emptypage ||
|-
| emptynewsection ||
|-
| editconflict ||
|-
| revwrongpage || <br /><translate> Thrown if an invalid revid is given for <tvar name=undo><code>undo</code></tvar> or <tvar name=undoafter><code>undoafter</code></tvar></translate>
|-
| undofailure ||
|-
| missingtitle || <br /><translate> (see above <tvar name=nocreate><code>nocreate</code></tvar> [[<tvar name=1>#Parameters</tvar>|parameter]])</translate>
|-
| mustbeposted ||
|-
| readapidenied ||
|-
| writeapidenied ||
|-
| noapiwrite ||
|-
| badtoken ||
|-
| missingparam ||
|-
| invalidparammix ||
|-
| invalidtitle ||
|-
| invalid-content-data || <br/><translate> occurs when trying to edit a JSON page with non-conforming data, or while trying to edit a <tvar name=1>MassMessageListContent</tvar> page</translate>
|-
| nosuchpageid ||
|-
| pagecannotexist ||
|-
| nosuchrevid ||
|-
| nosuchrevid ||
|-
| badmd5 ||
|-
| hookaborted ||
|-
| parseerror ||
|-
| summaryrequired ||
|-
| blocked ||
|-
| ratelimited ||
|-
| unknownerror ||
|-
| nosuchsection ||
|-
| sectionsnotsupported ||
|-
| editnotsupported || <translate> Editing of this type of page is not supported using the text based edit API.</translate>
|-
| appendnotsupported ||
|-
| redirect-appendonly ||
|-
| edit-invalidredirect ||
|-
| badformat ||
|-
| customcssprotected ||
|-
| customjsprotected ||
|-
| taggingnotallowed || <translate> You don't have permission to set change tags</translate>
|-
| badtags || <br /> Tag2'''}}
|-
| tpt-target-page || <br/><translate> When using <tvar name=translate></tvar>, editing of a translated subpage is not allowed.</translate>
|}

<translate>
== Parameter history == 
</translate>
* v1.35: <translate> Introduced <tvar name=1><code>baserevid</code></tvar></translate>
* v1.25: <translate> Introduced <tvar name=1><code>tags</code></tvar></translate>
* v1.21: <translate> Introduced <tvar name=1><code>contentformat</code>, <code>contentmodel</code></tvar></translate>
* v1.20: <translate> Introduced <tvar name=1><code>pageid</code></tvar></translate>
* v1.19: <translate> Introduced <tvar name=1><code>sectiontitle</code></tvar></translate>
* v1.18: <translate> Deprecated <tvar name=1><code>captchaid</code>, <code>captchaword</code></tvar></translate>
* v1.17: <translate> Introduced <tvar name=1><code>redirect</code></tvar></translate>
* v1.16: <translate> Deprecated <tvar name=1><code>watch</code>, <code>unwatch</code></tvar></translate>
* v1.16: <translate> Introduced <tvar name=1><code>watchlist</code></tvar></translate>
* v1.15: <translate> Introduced <tvar name=1><code>undo</code>, <code>undoafter</code></tvar></translate>
* v1.14: <translate> Introduced <tvar name=1><code>starttimestamp</code></tvar></translate>

<translate>
== Additional notes == 


* Log in is not strictly required by the API, but it is needed to correctly attribute the edit to its author.</translate> <translate> A successful edit from a user who is not logged in will be attributed to their IP address.</translate>
<translate>

* Bots that are not logged in may face restrictions on editing and other write requests; see for more details.</translate>
<translate>

* Users who are not logged in will always be given the empty CSRF token, <tvar name=1><code>+\</code></tvar>.</translate>
<translate>

* The process for requesting a token has changed several times across versions.</translate> <translate> See <tvar name=1></tvar> for more information.</translate>
<translate>

* <tvar name=1></tvar> provides a way to access edit tokens when running code within a wiki page.</translate>
<translate>

* You can use the same CSRF token for all edit operations across the same wiki, during a single login session.</translate>
<translate>

* It is a good practice to pass any tokens in your request at the end of the query string, or at least after the text parameter.</translate> <translate> That way, if the connection is interrupted, the token will not be passed and the edit will fail.</translate> <translate> If you are using the <tvar name=1></tvar> object to make requests, this is done automatically.</translate>
<translate>

* Although <tvar name=1><code>captchaid</code></tvar> and <tvar name=2><code>captchaword</code></tvar> have, technically, been removed from API:Edit since v1.18, <tvar name=3></tvar> extends API:Edit to work with CAPTCHAs.</translate> <translate> Thus, with ConfirmEdit installed, these parameters are still available.</translate> <translate> ConfirmEdit comes packaged with the MediaWiki software, v1.18+.</translate>

== Limitations ==
* The API does not yet support editing [[Multi-Content Revisions|content slots]] (). You can do so instead with an extension like [[Extension:WSSlots]], which enables the <code>editslot</code> API action.

<translate>
== See also == 
</translate>
* - <translate> contains useful links on editing articles.</translate>
* - <translate> describes how to log in using a simplified interface when accessing wikis via a script or application, rather than the GUI.</translate>
* - <translate> more details on using a bot to automatically edit pages.</translate>
* - <translate> provides a way to access edit tokens when running JavaScript within a MediaWiki page.</translate>
* - <translate> has more details on using tokens to log in or make POST requests.</translate>
* - <translate> a deprecated API, distinct from <tvar name=1></tvar>, for requesting tokens in earlier versions of MediaWiki.</translate>
* - <translate> allows you to diff between edits on a page.</translate>
* - <translate> alters tags on a page.</translate>
* - <translate> reverts a series of edits.</translate>
* - <translate> rolls back files to an earlier state.</translate>
* - <translate> deletes and restores revisions to a page.</translate>

<translate>

== References == 
</translate>

[[Category:MediaWiki API]]

----
''Sample content adapted from [[mediawikiwiki:API:Edit]] on mediawiki.org, licensed under [https://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA 4.0].''

API/Parsing wikitext

Admin — Sat, 25 Jul 2026 17:02:15 GMT

Seed from mediawiki.org for Seekmodo connector demo

New page

<languages/>

<translate>

'''GET/POST request''' to parse content of a page and obtain the output.

== API documentation == 
</translate>

<translate>
== Example 1: Parse content of a page == 

=== GET request === 
</translate>

<translate>
=== Response === 
</translate>
<syntaxhighlight lang="json">
{
"parse": {
"title": "Pet door",
"pageid": 3276454,
"revid": 852892138,
"text": {
"*": "<div class=\"mw-parser-output\"><div class=\"thumb tright\"><div class=\"thumbinner\" style=\"width:222px;\"><a href=\"/wiki/File:Doggy_door_exit.JPG\" class=\"image\"><img alt=\"\" src=\"//upload.wikimedia.org/wikipedia/commons/thumb/7/71/Doggy_door_exit.JPG/220px-Doggy_door_exit.JPG\" width=\"220\" height=\"165\" class=\"thumbimage\" srcset=\"//upload.wikimedia.org/wikipedia/commons/thumb/7/71/Doggy_door_exit.JPG/330px-Doggy_door_exit.JPG 1.5x,
...
}
}
}
</syntaxhighlight>

<translate>
== Sample code == 
</translate>

/Sample code 1}}

<translate>
== Example 2: Parse a section of a page and fetch its table data == 

=== GET request === 
</translate>

<translate>
=== Response === 
</translate>

<syntaxhighlight lang="json">
{
"parse": {
"title": "Wikipedia:Unusual articles/Places and infrastructure",
"pageid": 38664530,
"wikitext": {
"*": "===Antarctica===\n\n{| class=\"wikitable\"\n|-\n| '''[[Emilio Palma]]'''\n| An Argentine national who is the first person known to be born on the continent of Antarctica.\n|-\n| '''[[Scouting in the Antarctic]]'''\n| Always be prepared for glaciers and penguins.\n|}"
}
}
}
</syntaxhighlight>

<translate>
=== Sample code === 
</translate>

<syntaxhighlight lang="python3">
#!/usr/bin/python3

"""
parse_wikitable.py

MediaWiki Action API Code Samples
Demo of `Parse` module: Parse a section of a page, fetch its table data and save
it to a CSV file

MIT license
"""

import csv
import requests

S = requests.Session()

URL = "https://en.wikipedia.org/w/api.php"

TITLE = "Wikipedia:Unusual_articles/Places_and_infrastructure"

PARAMS = {
'action': "parse",
'page': TITLE,
'prop': 'wikitext',
'section': 5,
'format': "json"
}

def get_table():
""" Parse a section of a page, fetch its table data and save it to a CSV file
"""
res = S.get(url=URL, params=PARAMS)
data = res.json()
wikitext = data['parse']['wikitext']['*']
lines = wikitext.split('|-')
entries = []

for line in lines:
line = line.strip()
if line.startswith("|"):
table = line[2:].split('||')
entry = table[0].split("|")[0].strip("'''[[]]\n"), table[0].split("|")[1].strip("\n")
entries.append(entry)

file = open("places_and_infrastructure.csv", "w")
writer = csv.writer(file)
writer.writerows(entries)
file.close()

if __name__ == '__main__':
get_table()

</syntaxhighlight>

<translate>
== Possible errors == 
</translate>
{| class="wikitable"
|+
! <translate> Code</translate>
! <translate> Info</translate>
|-
|missingtitle
|
|-
|nosuchsection
|
|-
|pagecannotexist
|
|-
|invalidparammix
|<nowiki/>
*
*
*
|}

<translate>
== Parameter history == 
</translate>
* v1.45: <translate> Introduced <tvar name=1><code>parser</code></tvar></translate>
* v1.43: <translate> Introduced <tvar name=1><code>usearticle</code></tvar></translate>
* v1.38: <translate> Introduced <tvar name=1><code>showstrategykeys</code></tvar></translate>
* v1.32: <translate> Deprecated <tvar name=1><code>disabletidy</code></tvar></translate>
* v1.31: <translate> Introduced <tvar name=1><code>disablestylededuplication</code></tvar></translate>
* v1.30: <translate> Introduced <tvar name=1><code>revid</code>, <code>useskin</code>, <code>wrapoutputclass</code></tvar></translate>

<translate>
== See also == 
</translate>
*[[API:Parsing wikitext/TOCData]]
*
*
*
*
*
*

----
''Sample content adapted from [[mediawikiwiki:API:Parsing_wikitext]] on mediawiki.org, licensed under [https://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA 4.0].''

API/Query

Admin — Sat, 25 Jul 2026 17:02:14 GMT

Seed from mediawiki.org for Seekmodo connector demo

New page

<languages/>

<translate>

The <tvar name=1><code>action=query</code></tvar> module allows you to fetch information about a wiki and the data stored in it, such as the wikitext of a particular page, the links and categories of a set of pages, or the token you need to .
</translate>

<div style="overflow:auto">

</div>

<translate>
== API documentation == 
</translate>

<translate>
=== Query modules === 


The query module has three types of submodules (also called query modules):


* about the wiki and the logged-in user.</translate>
<translate>

* of pages, including page revisions and content.</translate>
<translate>

* of pages that match certain criteria.

== Examples == 
</translate>

<translate>
=== Example 1: Specifying pages === 


Unlike meta and list query modules, all property query modules work on a set of pages that can be specified in one of the following ways:


* By name using the <tvar name=1><code>titles</code></tvar> parameter, e.g. <tvar name=2><code>titles=Foo|Bar|Main_Page</code></tvar>.</translate>
<translate>

* By page ID using the <tvar name=1><code>pageids</code></tvar> parameter, e.g. <tvar name=2><code>pageids=123|456|75915</code></tvar>.</translate>
<translate>

* By revision ID using the <tvar name=1><code>revids</code></tvar> parameter, e.g. <tvar name=2><code>revids=478198|54872|54894545</code></tvar>.</translate> <translate> Most query modules will convert revision ID to the corresponding page ID.</translate> <translate> Only <tvar name=1>revisions}}</tvar> actually uses the revision ID itself.</translate>
<translate>

* Using a [[<tvar name=1>#Generators</tvar>|generator]].
</translate>

<translate>
==== GET request ==== 
</translate>
5487548945
|p3=format=json
|p4=formatversion=2
}}
<translate>
==== Response ==== 
</translate>
<syntaxhighlight lang="json">
{
"batchcomplete": true,
"query": {
"pages": [
{
"pageid": 1130,
"ns": 0,
"title": "Avicenna"
},
{
"pageid": 17412,
"ns": 0,
"title": "Klein bottle"
},
{
"pageid": 33642,
"ns": 0,
"title": "Warrant"
}
]
}
}
</syntaxhighlight>

<translate>
=== Example 2: Title normalization === 


Title normalization converts page titles to their canonical form.


This means capitalizing the first character, replacing underscores with spaces, and changing namespace to the localized form defined for that wiki.
</translate>

<translate>
==== GET request ==== 
</translate>
article_B
| p3=format=json
| p4=formatversion=2
}}
<translate>
==== Response ==== 
</translate>
<syntaxhighlight lang="json">
{
"batchcomplete": true,
"query": {
"normalized": [
{
"fromencoded": false,
"from": "Project:articleA",
"to": "Wikipedia:ArticleA"
},
{
"fromencoded": false,
"from": "article_B",
"to": "Article B"
}
],
"pages": [
{
"ns": 0,
"title": "Article B",
"missing": true
},
{
"ns": 4,
"title": "Wikipedia:ArticleA",
"missing": true
}
]
}
}
</syntaxhighlight>

<translate>
=== Example 3: Missing and invalid titles === 


Titles that don't exist or are invalid will have a <tvar name=1><code>missing</code></tvar> or <tvar name=2><code>invalid</code></tvar> attribute set in the response.


In output formats that support numeric array keys, missing and invalid titles will have negative page IDs.
</translate>

<translate> In some cases, a title can be viewed by a user but cannot be accessed by the API, such as pages that mirror content from another wiki.</translate>
<translate> These titles will have a <tvar name=1><code>known</code></tvar> attribute set in the response.</translate>

<translate>
==== GET request ==== 
</translate>
Main%20PageTalk:
|p3=format=json
|p4=formatversion=2
}}
<translate>
==== Response ==== 
</translate>
<syntaxhighlight lang="json">
{
"batchcomplete": true,
"query": {
"pages": [
{
"ns": 0,
"title": "Doesntexist",
"missing": true
},
{
"title": "Talk:",
"invalidreason": "The requested page title is empty or contains only the name of a namespace.",
"invalid": true
},
{
"pageid": 15580374,
"ns": 0,
"title": "Main Page"
}
]
}
}
</syntaxhighlight>

<translate>
=== Example 4: Continuing queries=== 


When all the data is not returned in the response of a query, there will be a <tvar name=1><code>continue</code></tvar> attribute to indicate that there is more data.
</translate>

<translate>
==== GET request ==== 
</translate>

<translate>
==== Response ==== 
</translate>
<syntaxhighlight lang="json">
{
"continue": {
"accontinue": "List_of_largest_companies_in_Sri_Lanka",
"continue": "-||"
},
"query": {
"allcategories": [
{
"category": "List of BioWare characters"
},
{
"category": "List of Harlequin Romance novels"
},
{
"category": "List of MPs elected in UK elections templates"
},
{
"category": "List of Metamorphoses characters"
},
{
"category": "List of Rockstar Games characters"
},
{
"category": "List of Star Trek awards and nominations"
},
{
"category": "List of Swedish films of the 2020s"
},
{
"category": "List of association football clubs in the Republic of Ireland templates"
},
{
"category": "List of awards and nominations received by Aleksej Pechkuroy"
},
{
"category": "List of cabinet templates"
}
]
}
}
</syntaxhighlight>

<translate>

To get further data, add its values to the original request:
</translate>

<translate>
==== GET request ==== 
</translate>

}}
<translate>
==== Response ==== 
</translate>
<syntaxhighlight lang="json">
{
"batchcomplete": true,
"query": {
"allcategories": [
{
"category": "List of largest companies in Sri Lanka"
},
{
"category": "List of longest beaches of the world"
},
{
"category": "List of ministers by ministry of Bangladesh"
},
{
"category": "List of people from Palm Beach, Florida"
},
{
"category": "List of video game characters"
}
]
}
}
</syntaxhighlight>

<translate>
=== Example 5: Batchcomplete === 


The API returns a <tvar name=1><code>batchcomplete</code></tvar> element to indicate that all data for the current batch of items has been returned.
</translate>

<translate>

In the response of the sample query below, <tvar name=1><code>batchcomplete</code></tvar> has been included to indicate that all the data for each of the three images has been returned.


The next continuation will begin returning data for the next set of 3 images.
</translate>

<translate>
==== GET request ==== 
</translate>

<translate>
===== Response ===== 
</translate>
<syntaxhighlight lang="json">
{
"batchcomplete": true,
"continue": {
"aicontinue": "20020822143445|Do_You_Want_to_Know_a_Secret_(Beatles_song_-_sample).ogg",
"continue": "-||"
},
"query": {
"allimages": [
{
"name": "Simon_and_Garfunkel_-_Mrs_Robinson.ogg",
"timestamp": "2002-08-04T19:55:17Z",
"url": "https://upload.wikimedia.org/wikipedia/en/6/64/Simon_and_Garfunkel_-_Mrs_Robinson.ogg",
"descriptionurl": "https://en.wikipedia.org/wiki/File:Simon_and_Garfunkel_-_Mrs_Robinson.ogg",
"descriptionshorturl": "https://en.wikipedia.org/w/index.php?curid=67723",
"ns": 6,
"title": "File:Simon and Garfunkel - Mrs Robinson.ogg"
},
{
"name": "Simon_and_Garfunkel_-_Scarborough_Fair.ogg",
"timestamp": "2002-08-04T20:01:36Z",
"url": "https://upload.wikimedia.org/wikipedia/en/c/c1/Simon_and_Garfunkel_-_Scarborough_Fair.ogg",
"descriptionurl": "https://en.wikipedia.org/wiki/File:Simon_and_Garfunkel_-_Scarborough_Fair.ogg",
"descriptionshorturl": "https://en.wikipedia.org/w/index.php?curid=67779",
"ns": 6,
"title": "File:Simon and Garfunkel - Scarborough Fair.ogg"
},
{
"name": "Beatles_please_me.ogg",
"timestamp": "2002-08-22T14:34:00Z",
"url": "https://upload.wikimedia.org/wikipedia/en/e/ee/Beatles_please_me.ogg",
"descriptionurl": "https://en.wikipedia.org/wiki/File:Beatles_please_me.ogg",
"descriptionshorturl": "https://en.wikipedia.org/w/index.php?curid=74826",
"ns": 6,
"title": "File:Beatles please me.ogg"
}
]
}
}
</syntaxhighlight>

<translate>
=== Example 6: Generators === 


Use generators if you want to get data about a set of pages.


For example, to get data about pages in a certain category, instead of querying <tvar name=1><code>list=categorymembers</code></tvar> and then querying again with <tvar name=2><code>pageids</code></tvar> set to all the returned pages, combine the two API calls into one by using <tvar name=3><code>generator=categorymembers</code></tvar>.


When using a list module as a generator, you don't need to specify the pages.


However, for a property module, you should [[<tvar name=1>#Specifying pages</tvar>|specify the pages]] which the generator will work on.


For example, to load all pages that are linked to from the main page, use <tvar name=1><code>generator=links&titles=Main%20Page</code></tvar>.


Parameters passed to a generator must be prefixed with a <code>g</code>. For instance, when using <code>generator=backlinks</code>, use <code>gbllimit</code> instead of <code>bllimit</code>.


The sample query below gets links and categories for the first three pages in the main namespace starting with "Ba".
</translate>

<translate>
==== GET request ==== 
</translate>
categories
|p6=format=json
|p7=formatversion=2
}}
<translate>
==== Response ==== 
</translate>
<syntaxhighlight lang="json">
{
"continue": {
"plcontinue": "14977970|0|Kirkwall_Ba_game",
"continue": "||categories"
},
"query": {
"pages": [
{
"pageid": 98178,
"ns": 0,
"title": "Ba",
"links": [
{
"ns": 0,
"title": "BA"
},
{
"ns": 4,
"title": "Wikipedia:Mainspace"
},
{
"ns": 4,
"title": "Wikipedia:Naming conventions (capitalization)"
},
{
"ns": 4,
"title": "Wikipedia:Protection policy"
},
{
"ns": 4,
"title": "Wikipedia:Redirect"
},
{
"ns": 10,
"title": "Template:R from miscapitalisation"
},
{
"ns": 10,
"title": "Template:R from modification"
},
{
"ns": 10,
"title": "Template:R to disambiguation page"
},
{
"ns": 14,
"title": "Category:Redirects from ambiguous terms"
},
{
"ns": 14,
"title": "Category:Redirects from other capitalisations"
}
],
"categories": [
{
"ns": 14,
"title": "Category:Redirects from ambiguous terms"
},
{
"ns": 14,
"title": "Category:Redirects from other capitalisations"
},
{
"ns": 14,
"title": "Category:Unprintworthy redirects"
}
]
},
{
"pageid": 14977970,
"ns": 0,
"title": "Ba'"
},
{
"pageid": 33351890,
"ns": 0,
"title": "Ba'Al Shem Tov"
}
]
}
}
</syntaxhighlight>

<translate>
== Continuing queries == 
</translate>
<translate> Queries will often have more results available than are just shown in the original query.</translate>
(Often this is because a query's result has been reached.)
<translate> In these cases, queries can be continued.</translate>
<translate> More detailed information on continuing queries can be at <tvar name=1></tvar>.</translate>

<translate>
== Possible warnings == 
</translate>
{| class="wikitable"
|+
! <translate> Warning message</translate>
! <translate> Cause</translate>
|-
| <translate> No support for special pages has been implemented.</translate>
| <translate> Thrown if a title in the Special: or Media: namespace is given. The pages in these namespaces cannot be queried.</translate>
|-
|
| <translate> Thrown if the <tvar name=1><code>redirect</code></tvar> parameter is used in a query that specifies pages using <tvar name=2><code>revids</code></tvar>.</translate>
|}

<translate>
== Parameter history == 
</translate>
* v1.34: <translate> Introduced <tvar name=1><code>exportschema</code></tvar></translate>
* v1.24: <translate> Introduced <tvar name=1><code>rawcontinue</code></tvar></translate> <translate> (note: [[<tvar name=1>Special:MyLanguage/API:Raw query continue</tvar>|raw continuation]] was the default behavior until v1.26)</translate>
* v1.21: <translate> Introduced <tvar name=1><code>continue</code></tvar></translate>

<translate>
== Additional notes == 
</translate>
* <translate> Specifying titles through <tvar name=1><code>titles</code></tvar> or <tvar name=2><code>pageids</code></tvar> is limited to 50 titles per query, or 500 for those with the <tvar name=3><code>apihighlimits</code></tvar> right.</translate>
* <translate> Use multiple query modules together to get what you need in one request, e.g. <tvar name=1><code>prop=info|revisions&list=backlinks|embeddedin|allimages&meta=userinfo</code></tvar>.</translate>
* <translate> Generators always pass page titles to the query module.</translate> <translate> Unlike lists (which may include additional data by default), generators should not output any information themselves, unless when explicitly requested via the generator module's query parameters.</translate>

<translate>
== Resolving redirects == 
</translate>
<translate> Redirects can be resolved automatically, so that the target of a redirect is returned instead of the given title.</translate>
<translate> When present, they will always contain <tvar name=1><code>from</code></tvar> and <tvar name=2><code>to</code></tvar> attributes and may contain a <tvar name=3><code>tofragment</code></tvar> attribute for those redirects that point to specific sections.</translate>

<translate> Both normalization and redirection may take place.</translate>
<translate> In the case of multiple redirects, all redirects will be resolved, and in case of a circular redirect, there might not be a page in the 'pages' section (see [[<tvar name=1>#circular_redirects</tvar>|an example request]]).</translate>
<translate> Redirect resolution cannot be used in combination with the <tvar name=1><code>revids=</code></tvar> parameter or with a generator generating revids; doing that will produce a [[<tvar name=2>#Possible warnings</tvar>|warning]] and will not resolve redirects for the specified revids.</translate>

<translate>

The examples below show how the <tvar name=1><code>redirects</code></tvar> parameter works.
</translate>

{{ApiEx
| desc=<translate> Using "<tvar name=1>redirects</tvar>" parameter.</translate> <translate> "<tvar name=1>Main page</tvar>" is a redirect to "<tvar name=2>Main Page</tvar>"</translate>
| p1=action=query
| p2=titles=Main%20page
| p3=redirects
| p4=format=json
| p5=formatversion=2
| result=<syntaxhighlight lang="json">
{
"batchcomplete": true,
"query": {
"redirects": [
{
"from": "Main page",
"to": "Main Page"
}
],
"pages": [
{
"pageid": 15580374,
"ns": 0,
"title": "Main Page"
}
]
}
}
</syntaxhighlight>
}}
{{ApiEx
| desc=<translate> Same request but without the "<tvar name=1>redirects</tvar>" parameter.</translate>
| p1=action=query
| p2=titles=Main%20page
| p3=format=json
| p4=formatversion=2
| result=<syntaxhighlight lang="json">
{
"batchcomplete": true,
"query": {
"pages": [
{
"pageid": 217225,
"ns": 0,
"title": "Main page"
}
]
}
}
</syntaxhighlight>
}}
{{ApiEx
| desc=<translate> Without "<tvar name=1>redirects</tvar>" you may want to use <tvar name=2>prop=info</tvar> to obtain redirect status.</translate>
| p1=action=query
| p2=titles=Main%20page
| p3=prop=info
| p4=formatversion=2
| result=<syntaxhighlight lang="json">
{
"batchcomplete": true,
"query": {
"pages": [
{
"pageid": 217225,
"ns": 0,
"title": "Main page",
"contentmodel": "wikitext",
"pagelanguage": "en",
"pagelanguagehtmlcode": "en",
"pagelanguagedir": "ltr",
"touched": "2017-12-17T02:02:05Z",
"lastrevid": 777924062,
"length": 170,
"redirect": true
}
]
}
}
</syntaxhighlight>
}}
{{ApiEx
| desc=<translate> Request with a section link.</translate> <translate> "<tvar name=1>Wikipedia:!--</tvar>" is a redirect to "<tvar name=2>Wikipedia:Manual of Style#Invisible comments</tvar>"</translate>
| p1=action=query
| p2=titles=Wikipedia:!--
| p3=redirects
| p4=format=json
| p5=formatversion=2
| result=<syntaxhighlight lang="json">
{
"batchcomplete": true,
"query": {
"redirects": [
{
"from": "Wikipedia:!--",
"to": "Wikipedia:Manual of Style",
"tofragment": "Invisible comments"
}
],
"pages": [
{
"pageid": 33697,
"ns": 4,
"title": "Wikipedia:Manual of Style"
}
]
}
}
</syntaxhighlight>
}}
<translate> Here is a case of a circular redirect: <tvar name=1>Page1 → Page2 → Page3 → Page1</tvar>.</translate> <translate> Also, in this example a non-normalized name <tvar name=1>'page1'</tvar> is used.</translate>
|p1=action=query
|p2=titles=page1
|p3=redirects
|p4=format=json
|p5=formatversion=2
|result=<syntaxhighlight lang="json">
{
"batchcomplete": true,
"query": {
"normalized": [
{
"fromencoded": false,
"from": "page1",
"to": "Page1"
}
],
"redirects": [
{
"from": "Page1",
"to": "Page2"
},
{
"from": "Page2",
"to": "Page3"
},
{
"from": "Page3",
"to": "Page1"
}
],
"pages": [
{
"ns": 0,
"title": "Page1",
"missing": true
}
]
}
}
</syntaxhighlight>}}

<translate>

== See also == 
</translate>
* - <translate> The quick start guide.</translate>
* - <translate> Contains information on how to use the <tvar name=1><code>rawcontinue</code></tvar> parameter.</translate>

----
''Sample content adapted from [[mediawikiwiki:API:Query]] on mediawiki.org, licensed under [https://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA 4.0].''

API/Search

Admin — Sat, 25 Jul 2026 17:02:14 GMT

Seed from mediawiki.org for Seekmodo connector demo

New page

<languages/>

<translate>

'''GET request''' to perform an advanced search for wiki pages by title or content text match.

== API documentation == 
</translate>

<translate>
=== GET request === 
</translate>

{{Note|1=<translate> Default search results are without UTF8 encoding.</translate> <translate> Replace <tvar name=1><code>utf8</code></tvar> in the get request above to see the difference.</translate>}}

<translate>
=== Response === 
</translate>
<syntaxhighlight lang="python3">
{
"batchcomplete": "",
"continue": {
"sroffset": 10,
"continue": "-||"
},
"query": {
"searchinfo": {
"totalhits": 5060
},
"search": [
{
"ns": 0,
"title": "Nelson Mandela",
"pageid": 21492751,
"size": 196026,
"wordcount": 23664,
"snippet": "<span class=\"searchmatch\">Nelson</span> Rolihlahla <span class=\"searchmatch\">Mandela</span> (/mænˈdɛlə/, Xhosa: [xoliɬaˈɬa <span class=\"searchmatch\">manˈdɛla</span>]; 18 July 1918 – 5 December 2013) was a South African anti-apartheid revolutionary,",
"timestamp": "2018-07-23T07:59:43Z"
},
{
"ns": 0,
"title": "Death of Nelson Mandela",
"pageid": 41284488,
"size": 133513,
"wordcount": 13512,
"snippet": "On December 5, 2013, <span class=\"searchmatch\">Nelson</span> <span class=\"searchmatch\">Mandela</span>, the first President of South Africa to be elected in a fully representative democratic election, as well as the country's",
"timestamp": "2018-07-19T17:30:59Z"
}
...
]
}
}
</syntaxhighlight>

<translate>
=== Sample code === 
</translate>


/Sample code 1}}

<translate>
== Possible errors == 
</translate>
{| class="wikitable"
|+
! <translate> Code</translate>
! <translate> Info</translate>
|-
| nosrsearch
|
|-
| search-text-disabled
|
|-
| search-title-disabled
|
|-
| search-error
| <translate> search error has occurred</translate>
|}

<translate>
== Parameter history == 
</translate>
* v1.24: <translate> Deprecated <tvar name=1><code>score</code>,<code>hasrelated</code></tvar></translate>
* v1.23:
** <translate> Removed <tvar name=1><code>srredirects</code></tvar>.</translate> <translate> Redirects are always included.</translate>
** <translate> Introduced <tvar name=1><code>srinterwiki</code></tvar></translate>
* v1.22: <translate> Introduced <tvar name=1><code>srbackend</code></tvar></translate>
* v1.17: <translate> Introduced <tvar name=1><code>nearmatch</code>, <code>score</code>, <code>titlesnippet</code>, <code>redirecttitle</code>, <code>redirectsnippet</code>, <code>sectiontitle</code>, <code>sectionsnippet</code>, <code>hasrelated</code></tvar></translate>
* v1.16: <translate> Introduced <tvar name=1><code>srinfo</code>, <code>srprop</code></tvar></translate>

<translate>
== Additional notes == 


* Depending on which search backend is in use, how <tvar name=1><code>srsearch</code></tvar> is interpreted may vary.</translate> <translate> On Wikimedia wikis which use CirrusSearch, see <tvar name=1></tvar> for information about the search syntax.</translate>

<translate>
== See also == 
</translate>
*
*

[[Category:MediaWiki API query lists|MediaWiki API query lists]]

----
''Sample content adapted from [[mediawikiwiki:API:Search]] on mediawiki.org, licensed under [https://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA 4.0].''

Manual/Purge

Admin — Sat, 25 Jul 2026 17:02:13 GMT

Seed from mediawiki.org for Seekmodo connector demo

New page

<languages />
<translate> '''Purging''' forces MediaWiki to clear the cached version of a given page, forcing the page to be redisplayed from its source or scripts to restart.</translate>
<translate> It is used to ensure that recent changes are made immediately visible.</translate>

<translate> One way to purge a MediaWiki page is to click a page's <tvar name=1></tvar> tab, then in your browser's location field delete just the word <tvar name=2><code>history</code></tvar> off the end of the URL, type <tvar name=3><code>purge</code></tvar> (after the <tvar name=4><code>=</code></tvar>) on the end of the URL, and hit <tvar name=5></tvar>.</translate>
<translate> Your URL should look something like one of the ones below.</translate>

<translate>
==Examples== 


* To purge a page, add <tvar name=purge><code>?action=purge</code></tvar> to the URL of the page you are viewing.</translate> <translate> For example:</translate>

: <code><nowiki>http://example.org/wiki/Main_Page</nowiki>'''?action=purge'''</code>

<translate>

* If the URL has other parameters in its query string, add the purge action to the query string with an ampersand (<tvar name=1>&</tvar>).</translate> <translate> For example:</translate>

: <code><nowiki>http://example.org/wiki/index.php?title=Main_Page</nowiki>'''&action=purge'''</code>

<translate>
== Requests must be confirmed== 
</translate>
<translate> Purge requests made via POST are automatically filled.</translate>
<translate> Users making purge requests via a query string will be presented with a confirmation form.</translate><ref>[[gerrit:304157]]</ref>
<translate> This form must be submitted before the purge request will be completed.</translate>
<translate> This behavior is a precaution to keep web spiders from accidentally purging pages when following links.</translate>

<translate>
==Purge and image thumbnails== 


If purge is run on an image description page, the cached thumbnails for the image will be purged.

==Categories== 
</translate>

<translate>

If purge is run on a category with less than 5000 members, the category will be recounted from scratch (<tvar name=1>[[phab:T85696|T85696]]</tvar>).

==Null edits== 
</translate>

<translate> Purging will only update the rendering of the page, it won't update the link tables.</translate>
<translate> These tables control lists that the page is listed in (for example, pages listed on category pages, <tvar name=1>[[Special:Whatlinkshere]]</tvar>, along with several other <tvar name=2><code>query</code></tvar> special pages).</translate>
<translate> In order to force an update of the link tables, you can do what is called a '''null edit''' (or '''purge edit''').</translate>
<translate> Click on <tvar name=1><code></code></tvar> and save without changing anything.</translate>
<translate> No entry in the page's history will appear, but all link tables and other derived data should be refreshed.</translate>

<translate> An alternative way to update the links table is to use the API's <tvar name=purge></tvar> module with the <tvar name=force><code>forcelinkupdate</code></tvar> option.</translate>
<translate> This however may not update other derived data, such as the search index or resource loader module cache.</translate>

{{Note|1=<translate> This option only applies to the API.</translate> <translate> Adding <tvar name=1><code>forcelinkupdate</code></tvar> to an <tvar name=2><code>index.php</code></tvar> URL has no effect.</translate>}}

'' which are created automatically to represent loggable actions in the page history.</translate> <translate> Dummy revisions are sometimes called "null revisions", but that should be avoided to prevent confusion.</translate>}}

<translate>
==See also== 
</translate>
* - <translate> a command-line [[<tvar name=1>Special:MyLanguage/Manual:Maintenance scripts</tvar>|maintenance script]] that allows batch purging of articles.</translate>
*
*
*
*
* [[gerrit:q/c2ce6a1b,n,z|Require POST in ?action=purge]]
*

<translate>
==References== 
</translate>
<references/>

[[Category:Cache|Cache]]

----
''Sample content adapted from [[mediawikiwiki:Manual:Purge]] on mediawiki.org, licensed under [https://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA 4.0].''

API/Main page

Admin — Sat, 25 Jul 2026 17:02:13 GMT

Seed from mediawiki.org for Seekmodo connector demo

New page

#REDIRECT [[API:Action API]]

----
''Sample content adapted from [[mediawikiwiki:API:Main_page]] on mediawiki.org, licensed under [https://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA 4.0].''

Manual/Job queue

Admin — Sat, 25 Jul 2026 17:02:12 GMT

Seed from mediawiki.org for Seekmodo connector demo

New page

<languages/>
<translate> The '''job queue''' is designed to hold many short tasks using [[w:batch processing|batch processing]].</translate>
It is commonly used to perform long-running tasks asynchronously, although a synchronous mode is available, too.

<translate>
== Set up == 
</translate>
<translate> It is recommended that you schedule the running of jobs completely in the background, via the command line.</translate>
If you do not have access to the command line but your hosting plan comes with a web control panel, it may well include a cronjob scheduler.

<translate> By default, jobs are run at the end of a web request. Disable this default behaviour by setting <tvar name=1></tvar> to <tvar name=2><code>0</code></tvar>.</translate>

{{note|1=<translate> You should run <tvar name=1><code>runJobs.php</code></tvar> as the same user as the web server runs as, to ensure that permissions to the filesystem are correctly accounted for if jobs touch uploaded files.</translate>}}

<translate>
=== Cron === 


You could use [[w:Cron|cron]] to run the jobs every hour. For instance, add the following to your crontab file:
</translate>

<syntaxhighlight lang="bash">
0 * * * * /usr/bin/php /var/www/wiki/maintenance/runJobs.php --maxtime=3600 > /var/log/runJobs.log 2>&1
</syntaxhighlight>

<translate>

Using Cron makes it easy to get started, but can make email notifications and cascading template feel slow (to wait up to an hour). Consider using one of the below approaches to set up a continuous job runner instead.

=== Continuous service === 


If you have shell access and the possibility to create init scripts, you can create a simple service to run jobs as they become available, and also throttle them to prevent the job runner from monopolising the CPU resources of the server:


Create a bash script, for example at <tvar name=1><code>/usr/local/bin/mwjobrunner</code></tvar>:

==== Create script ==== 
</translate>
<syntaxhighlight lang="bash">
#!/bin/bash
# <translate nowrap> Put the MediaWiki installation path on the line below</translate>
MW_INSTALL_PATH="/home/www/www.mywikisite.example/mediawiki"
RUN_JOBS="$MW_INSTALL_PATH/maintenance/runJobs.php --maxtime=3600"
echo <translate nowrap> Starting job service...</translate>
# <translate nowrap> Wait a minute after the server starts up to give other processes time to get started</translate>
sleep 60
echo <translate nowrap> Started.</translate>
while true; do
# <translate nowrap> Job types that need to be run ASAP no matter how many of them are in the queue</translate>
# <translate nowrap> Those jobs should be very "cheap" to run</translate>
php $RUN_JOBS --type="enotifNotify"
# <translate nowrap> Everything else, limit the number of jobs on each batch</translate>
# <translate nowrap> The <tvar name=1>--wait</tvar> parameter will pause the execution here until new jobs are added, to avoid running the loop without anything to do</translate>
php $RUN_JOBS --wait --maxjobs=20
# <translate nowrap> Wait some seconds to let the CPU do other things, like handling web requests, etc</translate>
echo <translate nowrap> Waiting for 10 seconds...</translate>
sleep 10
done
</syntaxhighlight>

<translate>

Depending on how fast the server is and the load it handles, you can adapt the number of jobs to run on each cycle and the number of seconds to wait on each cycle.


Make the script executable (<tvar name=1><code>chmod 755</code></tvar>).

==== Create service ==== 
</translate>
<translate> If using systemd, create a new service unit by creating the file <tvar name=1><code>/etc/systemd/system/mw-jobqueue.service</code></tvar>.</translate>
<translate> Change the <tvar name=1><code>User</code></tvar> parameter to the user that runs PHP on your web server:</translate>

<syntaxhighlight lang="ini">
[Unit]
Description=MediaWiki Job runner

[Service]
ExecStart=/usr/local/bin/mwjobrunner
Nice=10
ProtectSystem=full
User=php-fpm
OOMScoreAdjust=200
StandardOutput=journal

[Install]
WantedBy=multi-user.target
</syntaxhighlight>

<translate> Enable it and start it with those commands:</translate>

<syntaxhighlight lang="bash">
sudo systemctl enable mw-jobqueue
sudo systemctl start mw-jobqueue
sudo systemctl status mw-jobqueue
</syntaxhighlight>

<translate>
== Job execution on page requests == 
</translate>
<translate> By default, at the end of each web request, one job is taken from the job queue and executed.</translate>
<translate> This behaviour is controlled by the <tvar name=JobRunRate></tvar> configuration variable.</translate>
<translate> Setting this variable to <tvar name=1><code>1</code></tvar>, will run a job on each request.</translate>
<translate> Setting this variable to <tvar name=1><code>0</code></tvar> will disable the execution of jobs during web requests completely, so that you can instead run <tvar name=runJobs></tvar> manually or periodically from the command line.</translate>

<translate> When enabled, jobs will be executed by opening a socket and making an internal HTTP request to an unlisted [[<tvar name=man>Special:MyLanguage/Manual:Special pages</tvar>|special page]]: <tvar name=1>Special:RunJobs</tvar>.</translate>
<translate> See also the [[<tvar name=1>#Asynchronous</tvar>|asynchronous section]].</translate>

<translate>
=== Performance issue === 
</translate>
<translate> If the performance burden of running jobs on every web request is too great but you are unable to run jobs from the command line, you can reduce <tvar name=JobRunRate></tvar> to a number between <tvar name=1><code>1</code></tvar> and <tvar name=2><code>0</code></tvar>.</translate>
<translate> This means a job will execute ''on average'' every <tvar name=code><code>1 / $wgJobRunRate</code></tvar> requests.</translate>

<syntaxhighlight lang="php">
$wgJobRunRate = 0.01;
</syntaxhighlight>

<translate>
=== Manual usage === 
</translate>
<translate> There is also a way to empty the job queue manually, for example after changing a template that's present on many pages.</translate>
<translate> Simply run the <tvar name=RunJobs><code></code></tvar> maintenance script.</translate>
<translate> For example:</translate>

<syntaxhighlight lang="bash">
/path-to-my-wiki/maintenance$ php ./runJobs.php
</syntaxhighlight>

<translate>
== Abandoned jobs == 


A job can fail for some reasons. To understand why, you have to inspect the related log file.


In any case, if a job fails <tvar name=1>3</tvar> times (so if the system has done that number of attempts), the job is then considered "abandoned" and it's not executed again.


Relevant source code:
</translate>

https://doc.wikimedia.org/mediawiki-core/master/php/JobQueue_8php_source.html#l00085

<translate>

An abandoned job is:
</translate>

* <translate> not executed anymore from <tvar name=1></tvar></translate>
* <translate> not counted from <tvar name=1></tvar></translate>
* <translate> not automatically removed from the database</translate>
* <translate> but are included in the count of <tvar name=2>[[#Statistics|the statistics API module]]</tvar></translate>

<translate>
== Job examples == 

=== Updating links tables when a template changes === 
</translate>
<translate> When a template changes, MediaWiki adds a job to the job queue for each article transcluding that template.</translate>
<translate> Each job is a command to read an article, expand any templates, and update the link table accordingly.</translate>
<translate> Previously, the host articles would remain outdated until either their parser cache expires or until a user edits the article.</translate>

<translate>
=== HTML cache invalidation === 


A wider class of operations can result in invalidation of the HTML cache for a large number of pages:


*Changing an image (all the thumbnails have to be re-rendered, and their sizes recalculated)</translate>
<translate>

*Deleting a page (all the links to it from other pages need to change from blue to red)</translate>
<translate>

*Creating or undeleting a page (like above, but from red to blue)</translate>
<translate>

*Changing a template (all the pages that transclude the template need updating)
</translate>

<translate> Except for template changes, these operations do not invalidate the links tables, but they do invalidate the HTML cache of all pages linking to that page, or using that image.</translate>
<translate> Invalidating the cache of a page is a short operation; it only requires updating a single database field and sending a multicast packet to clear the caches.</translate>
<translate> But if there are more than about 1000 to do, it takes a long time. By default, one job is added per '''300''' operations (see <tvar name=1></tvar>)</translate>

<translate> Note, however, that even if purging the cache of a page is a short operation, reparsing a complex page that is not in the cache may be expensive, especially if a highly used template is edited and causes lots of pages to be purged in a short period of time and your wiki has lots of concurrent visitors loading a wide spread of pages.</translate>
<translate> This can be mitigated by reducing the number of pages purged in a short period of time, by reducing <tvar name=1></tvar> to a small number (20, for example) and also set <tvar name=2></tvar> for <tvar name=3><code>htmlCacheUpdate</code></tvar> to a low number (5, for example).</translate>

<translate>
=== Audio and video transcoding === 


When using <tvar name=1></tvar> to process local uploads of audio and video files, the job queue is used to run the potentially very slow creation of derivative transcodes at various resolutions/formats.


These are '''not suitable''' for running on web requests -- you will need a background runner.


It's recommended to set up separate runners for the <tvar name=1><code>webVideoTranscode</code></tvar> and <tvar name=2><code>webVideoTranscodePrioritized</code></tvar> job types if possible. These two queues process different subsets of files -- the first for high resolution HD videos, and the second for lower-resolution videos and audio files which process more quickly.

== Typical values == 
</translate>
<translate> During a period of low load, the job queue might be zero.</translate>
<translate> At Wikimedia, the job queue is, in practice, almost never zero.</translate>
<translate> In off-peak hours, it might be a few hundred to a thousand.</translate>
<translate> During a busy day, it might be a few million, but it can quickly fluctuate by 10% or more.</translate>
<sup>[https://brionv.com/log/2008/04/22/so-whats-in-the-job-queue-anyway/]</sup>

<translate>
== Statistics == 


The value of the job queue can be retrieved from <tvar name=1></tvar>:
</translate>

<translate> The number of jobs returned in the API result may be slightly inaccurate when using MySQL, which estimates the number of jobs in the database.</translate>
<translate> This number can fluctuate based on the number of jobs that have recently been added or deleted.</translate>
<translate> For other databases that do not support fast result-size estimation, the actual number of jobs is given.</translate>

<translate>
== For developers and maintainers == 
</translate>
*

<translate>
=== Code stewardship === 
</translate>

<translate>
== History == 

=== Asynchronous === 


The configuration variable <tvar name=RunJobsAsync></tvar> has been added to force the execution of jobs synchronously, in scenarios where making an internal HTTP request for job execution is not wanted.
</translate>

<translate> When running jobs asynchronously, it will open an internal HTTP connection for handling the execution of jobs, and will return the contents of the page immediately to the client without waiting for the job to complete.</translate>
<translate> Otherwise, the job will be executed in the same process and the client will have to wait until the job is completed.</translate>
<translate> When the job does not run asynchronously, if a fatal error occurs during job execution, it will propagate to the client, aborting the load of the page.</translate>

<translate> Note that even if $wgRunJobsAsync is set to true, if PHP can't open a socket to make the internal HTTP request, it will fall back to the synchronous job execution.</translate>
<translate> However, there are a variety of situations where this internal request may fail, and jobs won't be run, without falling back to the synchronous job execution.</translate>
<translate> Starting with MediaWiki 1.28.1 and 1.27.2, $wgRunJobsAsync now defaults to false.</translate>

<translate>
=== Deferred updates === 
</translate>
<translate> The ''deferred updates'' mechanism allows the execution of code to be scheduled for the end of the request, after all content has been sent to the browser.</translate>
<translate> This is similar to queuing a job, except that it runs immediately instead of upto several minutes/hours in the future.</translate>

<translate> <tvar name=1><code>DeferredUpdates</code></tvar> was introduced in MediaWiki 1.23 and received major changes during MediaWiki 1.27 and 1.28.</translate>
<translate> The goal of this mechanism is speed up the web responses by doing less work, as well as to prioritise some work that would previously be a job to run as soon as possible after the end of the response.</translate>

<translate> A deferrable update can implement <tvar name=1><code>EnqueueableDataUpdate</code></tvar> in order to be queueable as a Job as well.</translate>
<translate> This is used by <tvar name=1><code>RefreshSecondaryDataUpdate</code></tvar> in core, for example, which means if the update fails for any reason, MediaWiki will fallback to queuing as a job and try again later as to fulfil the contract in question.</translate>

<translate>
=== Changes in MediaWiki 1.22 === 
</translate>
<translate> In <tvar name=mw></tvar>, the job queue execution on each page request was changed (<tvar name=gerrit></tvar>) so, instead of executing the job inside the same PHP process that's rendering the page, a new PHP CLI command is spawned to execute <tvar name=runJobs></tvar> in the background.</translate>
<translate> It will only work if <tvar name=PhpCli></tvar> is set to an actual path or safe mode is off, otherwise, the old method will be used.</translate>

<translate>

This new execution method could cause some problems:


* If <tvar name=PhpCli></tvar> is set to an incompatible version of PHP (e.g.: an outdated version) jobs may fail to run (fixed in 1.23).</translate>
<translate>

* PHP <tvar name=1><code>open_basedir</code></tvar> restrictions are in effect, and <tvar name=PhpCli></tvar> is disallowed (<tvar name=task></tvar>, fixed in 1.23).</translate>
<translate>

* Performance: even if the job queue is empty, the new PHP process is started anyway (<tvar name=task></tvar>, fixed in 1.23).</translate>
<translate>

* Sometimes the spawning PHP process cause the server or only the CLI process to hang due to <tvar name=1>stdout</tvar> and <tvar name=2>stderr</tvar> descriptors not properly redirected (<tvar name=task></tvar>, fixed in 1.22)</translate>
<translate>

* It does not work for shared code (wiki farms), because it doesn't pass additional required parameters to <tvar name=1>runJobs.php</tvar> to identify the wiki that's running the job (<tvar name=task></tvar>, fixed in 1.23)</translate>
<translate>

* Normal shell limits like <tvar name=1>, , </tvar> are enforced on the <tvar name=2>runJobs.php</tvar> process that's being executed in the background.
</translate>

<translate> There's no way to revert to the old on-request job queue handling, besides setting <tvar name=PhpCli></tvar> to <tvar name=1><code>false</code></tvar>, for example, which may cause other problems (<tvar name=task></tvar>).</translate>
<translate> It can be disabled completely by setting <tvar name=code> 0;}}</tvar>, but jobs will no longer run on page requests, and you must explicitly run <tvar name=1>runJobs.php</tvar> to periodically run pending jobs.</translate>

<translate>
=== Changes in MediaWiki 1.23 === 


In MediaWiki 1.23, the 1.22 execution method is abandoned, and jobs are triggered by MediaWiki making an HTTP connection to itself.


It was first designed as an [[<tvar name=man>Special:MyLanguage/Manual:API</tvar>|API]] entry point (<tvar name=gerrit1></tvar>) but later changed to be the unlisted special page <tvar name=1>[[Special:RunJobs]]</tvar> (<tvar name=gerrit2></tvar>).


While it solves various bugs introduced in 1.22, it still requires loading a lot of PHP classes in memory on a new process to execute a job, and also makes a new HTTP request that the server must handle.

=== Changes in MediaWiki 1.27 === 


In MediaWiki 1.25 and MediaWiki 1.26, use of <tvar name=1></tvar> would sometimes cause jobs not to get run if the wiki has custom <tvar name=2></tvar> configuration. This was fixed in MediaWiki 1.27.
</translate>

<translate>
=== Changes in MediaWiki 1.28 === 


Between MediaWiki 1.23 and MediaWiki 1.27, use of <tvar name=1></tvar> would cause jobs not to get run on if MediaWiki requests are for a server name or protocol that does not match the currently configured server name one (e.g. when supporting both HTTP and HTTPS, or when MediaWiki is behind a reverse proxy that redirects to HTTPS). This was fixed in MediaWiki 1.28.
</translate>

<translate>
=== Changes in MediaWiki 1.29 === 


In MediaWiki 1.27.0 to 1.27.3 and 1.28.0 to 1.28.2, when <tvar name=1></tvar> is set to a value greater than 0, an error like the one below may appear in error logs, or on the page:
</translate>

<pre>
PHP Notice: JobQueueGroup::__destruct: 1 buffered job(s) never inserted
</pre>

<translate> As a result of this error, certain updates may fail in some cases, like category members not being updated on category pages, or recent changes displaying edits of deleted pages - even if you manually run <tvar name=runJobs></tvar> to clear the job queue.</translate>
<translate> It has been reported as a bug (<tvar name=bug></tvar>) and was solved in 1.27.4 and 1.28.3.</translate>

=== Changes in MediaWiki 1.17 ===
<translate> Up to MediaWiki 1.16, the job queue value was shown on <tvar name=1>[[Special:Statistics]]</tvar>.</translate>
<translate> Since 1.17 (<tvar name=rev>[[rev:75272]]</tvar>) it's been removed, and can be seen now with <tvar name=api></tvar>:</translate>

=== MediaWiki 1.6 ===
<translate>

In 2009 ([[<tvar name=1>Special:MyLanguage/Release notes/1.6</tvar>|MediaWiki 1.6]]) the '''job queue''' was introduced to perform long-running tasks asynchronously.

== See also == 
</translate>
*
*
*
*
*

[[Category:Job queue| ]]
[[Category:Installation]]
[[Category:MediaWiki concepts]]

----
''Sample content adapted from [[mediawikiwiki:Manual:Job_queue]] on mediawiki.org, licensed under [https://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA 4.0].''

Manual/Importing XML dumps

Admin — Sat, 25 Jul 2026 17:02:12 GMT

Seed from mediawiki.org for Seekmodo connector demo

New page

<languages/>

<translate> This page describes methods to '''import XML dumps'''.</translate>
<translate> XML Dumps contain the content of a wiki (wiki pages with all their revisions), without the site-related data.</translate>
<translate> A XML dump does not create a full backup of the wiki database, the dump does not contain user accounts, images, edit logs, etc.</translate>

<translate> The <tvar name=1>[[Special:Export]]</tvar> page of any MediaWiki site, including any Wikimedia site and Wikipedia, creates an XML file (content dump).</translate>
<translate> See [[<tvar name=2>m:Special:MyLanguage/Data dumps</tvar>|meta:Data dumps]] and <tvar name=3></tvar>.</translate>
<translate> XML files are explained more on [[<tvar name=4>Special:MyLanguage/Help:Export#Export format</tvar>|Help:Export]].</translate>

<translate>
==How to import?== 


There are several methods for importing these XML dumps.

===Using Special:Import=== 


<tvar name=1>[[Special:Import]]</tvar> can be used by wiki users with <tvar name=2><code>import</code></tvar> permission (by default this is users in the <tvar name=3><code>sysop</code></tvar> group) to import a small number of pages (about 100 should be safe).


''Trying to import large dumps this way may result in timeouts or connection failures''.
</translate>

* <translate> See <tvar name=1></tvar> for a basic description of how the importing process works.</translate><ref><translate> See <tvar name=1></tvar> for a C# code sample that manipulates an XML import file.</translate></ref>

<translate> You are asked to give an interwiki prefix.</translate>
<translate> For instance, if you exported from the English Wikipedia, you have to type 'en'.</translate>
<translate> XML importing requires the <tvar name="1"><code>import</code></tvar> and <tvar name="2"><code>importupload</code></tvar> permissions.</translate>
<translate> See <tvar name=1></tvar>.</translate>

<translate>
=== Large XML uploads === 


Large XML uploads might be rejected because they exceed the PHP upload limit set in the <tvar name="1"><code>php.ini</code></tvar> file.
</translate>

<syntaxhighlight lang="ini">
; <translate nowrap> Maximum allowed size for uploaded files.</translate>
upload_max_filesize = 20M
</syntaxhighlight>
<translate>

Try changing these four settings in <tvar name="1"><code>php.ini</code></tvar>:
</translate>
<syntaxhighlight lang="ini">
; <translate nowrap> Maximum size of POST data that PHP will accept.</translate>
post_max_size = 20M

max_execution_time = 1000 ; <translate nowrap> Maximum execution time of each script, in seconds</translate>
max_input_time = 2000 ; <translate nowrap> Maximum amount of time each script may spend parsing request data</translate>

; <translate nowrap> Default timeout for socket based streams (seconds)</translate>
default_socket_timeout = 2000
</syntaxhighlight>

<translate>
===Using <tvar name=1>importDump.php</tvar>, if you have shell access=== 
</translate>
:<translate> ''Recommended method for general use, but slow for very big data sets.''</translate>
: <translate> ''See: <tvar name=1></tvar>, including tips on how to use it for large wikis.''</translate>

<translate>
===Using <tvar name=1>importTextFiles.php</tvar> maintenance Script=== 
</translate>

<translate> If you have a lot of content converted from another source (several word processor files, content from another wiki, etc), you may have several files that you would like to import into your wiki.</translate>
<translate> In MediaWiki 1.27 and later, you can use the <tvar name=2></tvar> maintenance script.</translate>

<translate>

You can also use the <tvar name=2></tvar> maintenance script for this purpose.
</translate>

===rebuildall.php===
<translate> For large XML dumps, you can run <tvar name=1><code>[[Special:MyLanguage/Manual:rebuildall.php|rebuildall.php]]</code></tvar>, but, it will take a ''long'' time, because it has to parse all pages.</translate>
<translate> This is not recommended for large data sets.</translate>

<translate>
=== Using pywikibot, <tvar name=1>pagefromfile.py</tvar> and Nokogiri === 
</translate>
<translate> <tvar name=1></tvar> is a collection of tools written in python that automate work on Wikipedia or other MediaWiki sites.</translate>
<translate> Once installed on your computer, you can use the specific tool <tvar name=3></tvar> which lets you upload a wiki file on Wikipedia or MediaWiki sites.</translate>
<translate> The xml file created by <tvar name=1>dumpBackup.php</tvar> can be transformed into a wiki file suitable to be processed by <tvar name=2>pagefromfile.py</tvar> using a simple script similar to the following (here the program will transform all xml files which are on the current directory which is needed if your MediaWiki site is a family):</translate>

<translate>
==== On Python ==== 
</translate>
<syntaxhighlight lang="python">
from pathlib import Path
from lxml import etree
import re
from pywikibot import Link, Site

""" The exported XML preserves local namespace names. To import into a project in another language,
you need to convert them to canonical names. Otherwise the pages will be imported as originals
without recognizing their namespace.
XML contains namespace numbers, but mapping them can be problematic. Because they can differ between projects.
For example, in ru.wikisource NS Page is number 104, while in uk.wikisource it is 252.
To solve these, the Link() class from pywikibot is used.

The Link() required the language code and family of project. XML does not contain these as separate
values. Instead, they are in another format, like `enwikisource` or 'commonswiki', which needs to be parsed.
"""

xml_folder = 'PATH_TO_XML_DUMP'
for xml_file in Path(xml_folder).glob('*.xml'):
root = etree.parse(xml_file).getroot()
ns = {'': root.nsmap[None]} # xml namespace

# Parsing language code and family of the project
dbname = root.find('.//siteinfo/dbname', ns).text
m = re.search(r'^(\w+?)(wiki|wikisource|wikiquote|wikinews|wikibooks)$', dbname)
if m:
site = Site(code=m.group(1), fam=m.group(2))
elif 'commons' in dbname:
site = Site('commons')
elif 'mediawikiwiki' in dbname:
site = Site('mediawiki')
else:
print("Site didn't recognized.")
break

wiki = []
for page in root.findall('.//page', ns):
title_source = page.find('title', ns).text
title = Link(title_source, site).ns_title().replace(' ', '_')
revision_id = page.find('.//revision/id', ns).text
print(f'{title}, revision id: {revision_id}')
text = page.find('.//revision/text', ns).text
wiki.append("\n'''%s'''\n%s\n" % (title, text))
Path(f'out_{xml_file.stem}.wiki').write_text('\n'.join(wiki))
</syntaxhighlight>

<translate>
==== On Ruby ==== 
</translate>

<syntaxhighlight lang="ruby">
# -*- coding: utf-8 -*-
# dumpxml2wiki.rb

require 'rubygems'
require 'nokogiri'

# <translate nowrap> This program <tvar name=1>dumpxml2wiki</tvar> reads MediaWiki xml files dumped by <tvar name=2>dumpBackup.php</tvar> on the current directory and transforms them into wiki files which can then be modified and uploaded again by <tvar name=3>pywikipediabot</tvar> using <tvar name=4>pagefromfile.py</tvar> on a MediaWiki family site.</translate>
# <translate nowrap> The text of each page is searched with xpath and its title is added on the first line as an html comment: this is required by <tvar name=1>pagefromfile.py</tvar>.</translate>
#
Dir.glob("*.xml").each do |filename|
input = Nokogiri::XML(File.new(filename), nil, 'UTF-8')

puts filename.to_s # prints the name of each .xml file

File.open("out_" + filename + ".wiki", 'w') {|f|
input.xpath("//xmlns:text").each {|n|
pptitle = n.parent.parent.at_css "title" # searching for the title
title = pptitle.content
f.puts "\n" << n.content << "\n"
}
}
end
</syntaxhighlight>

<translate>

For example, here is an excerpt of a wiki file output by the command 'ruby dumpxml2wiki.rb' (two pages can then be uploaded by pagefromfile.py, a Template and a second page which is a redirect):
</translate>

<syntaxhighlight lang="html4strict">
<includeonly>Tłumaczenie</includeonly>

#REDIRECT[[badania demograficzne]]
<noinclude>
[[Category:Termin wielojęzycznego słownika demograficznego (pierwsze wydanie)|ilościowa demografia]]
[[Category:Termin wielojęzycznego słownika demograficznego (pierwsze wydanie) (redirect)]]
[[Category:10]]</noinclude>

</syntaxhighlight>

<translate> The program accesses each xml file, extracts the texts within <tvar name=1><nowiki><text> </text></nowiki></tvar> markups of each page, searches the corresponding title as a parent and enclosed it with the paired <nowiki> </nowiki> commands used by 'pagefromfile' to create or update a page.</translate>
<translate> The name of the page is in an html comment and separated by three quotes on the same first start line.</translate>
<translate> Please notice that the name of the page can be written in Unicode.</translate>
<translate> Sometimes it is important that the page starts directly with the command, like for a <tvar name=2><nowiki>#REDIRECT</nowiki></tvar>; thus the comment giving the name of the page must be ''after'' the command but still on the first line.</translate>

<translate>

Please remark that the xml dump files produced by <tvar name=1>dumpBackup.php</tvar> are prefixed by a namespace:
</translate>

<syntaxhighlight lang="html4strict"><mediawiki xmlns="http://www.mediawiki.org/xml/export-0.4/"></syntaxhighlight>

<translate>

In order to access the text node using Nokogiri, you need to prefix your path with 'xmlns':
</translate>

<syntaxhighlight lang="html4strict">input.xpath("//xmlns:text")</syntaxhighlight>

<translate>

Nokogiri is an HTML, XML, SAX, & Reader parser with the ability to search documents via XPath or CSS3 selectors from the last generation of XML parsers using Ruby.


Example of the use of 'pagefromfile' to upload the output wiki text file:
</translate>

<syntaxhighlight lang="bash">
python pagefromfile.py -file:out_filename.wiki -summary:"Reason for changes" -lang:pl -putthrottle:01
</syntaxhighlight>

<translate>

=== How to import logs? === 


Exporting and importing logs with the standard MediaWiki scripts often proves very hard; an alternative for import is the script <tvar name=1><code>pages_logging.py</code></tvar> in the [<tvar name=2>https://github.com/glimmerphoenix/WikiDAT</tvar> WikiDAT tool], as [[<tvar name=3>mailarchive:xmldatadumps-l/2013-July/000876.html</tvar>|suggested by Felipe Ortega]].

== Troubleshooting == 

=== Merging histories, revision conflict, edit summaries, and other complications === 
</translate>
<translate> When importing a page with history information, if the user name already exists in the target project, change the user name in the XML file to avoid confusion.</translate>
<translate> If the user name is new to the target project, the contributions will still be available, but no account will be created automatically.</translate>

<translate> When a page is referenced through a link or a URL, generic namespace names are converted automatically.</translate>
<translate> If the prefix is not a recognized namespace name, the page will default to the main namespace.</translate>
<translate> However, prefixes like <tvar name=1><code>mw:</code></tvar> might be ignored on projects that use them for interwiki linking.</translate>
<translate> In such cases, it might be beneficial to change the prefix to "Project:" in the XML file before importing.</translate>

<translate> If a page with the same name already exists, importing revisions will combine their histories.</translate>
<translate> Adding a revision between two existing ones can make the next user's changes appear different.</translate>
<translate> To see the actual change, compare the two original revisions, not the inserted one.</translate>
<translate> So, only insert revisions to properly rebuild the page history.</translate>

<translate> A revision won't be imported if there's already a revision with the same date and time.</translate>
<translate> This usually happens if it's been imported before, either to the current, a previous wiki, or both, possibly from a third site.</translate>

<translate> An edit summary might reference or link to another page, which can be confusing if the page being linked to has not been imported, even though the referencing page has been.</translate>

<translate> The edit summary doesn't automatically indicate whether the page has been imported, but in the case of an upload import, you can add this information to the edit summaries in the XML file before the import.</translate>
<translate> This can help prevent confusion. When modifying the XML file with find/replace, keep in mind that adding text to the edit summaries requires differentiating between edits with and without an edit summary.</translate>
<translate> If there are multiple comment tags in the XML file, only the last set will be applied.</translate>

<translate>
=== Interwikis === 
</translate>
</tvar> linking.</translate>
|1=
}}
<translate> For example, ones with a prefix of 'Meta:' would conflict with the interwiki prefix <tvar name=2><code>meta:</code></tvar> which by default links to <tvar name=3><nowiki>https://meta.wikimedia.org</nowiki></tvar>.</translate>

<translate>

You can do any of the following.
</translate>

*<translate> Remove the prefix from the <tvar name=2></tvar> table.</translate> <translate> This will preserve page titles, but prevent interwiki linking through that prefix.</translate>
*:<translate> Example: you will preserve page titles 'Meta:Blah blah' but will not be able to use the prefix 'meta:' to link to meta.wikimedia.org (although it will be possible through a different prefix).</translate>
*:<translate> How to do it: before importing the dump, run the query <tvar name=1><code>DELETE FROM interwiki WHERE iw_prefix='prefix'</code></tvar> (note: do not include the colon in the <code>prefix</code>).</translate> <translate> Alternatively, if you have [[<tvar name=2>Special:MyLanguage/Manual:Guide to setting up interwiki linking</tvar>|enabled editing the interwiki table]], you can simply go to <tvar name=3>[[Special:Interwiki]]</tvar> and click the 'Delete' link on the right side of the row belonging to that prefix.</translate>
*<translate> Replace the unwanted prefix in the XML file with "Project:" before importing. This will preserve the functionality of the prefix as an interlink, but will replace the prefix in the page titles with the name of the wiki where they're imported into, and might be quite a pain to do on large dumps.</translate>
*:<translate> Example: replace all 'Meta:' with 'Project:' in the XML file. MediaWiki will then replace 'Project:' with the name of your wiki during importing.</translate>

<translate>
==See also== 
</translate>
*
* [[meta:Special:MyLanguage/Data dumps/Other tools|meta:Data dumps/Other tools]]
*
* – <translate> May come in handy if you are doing massive imports</translate>
* – <translate> Settings that may need to be changed if you are doing massive imports</translate>
* – <translate> for importing images.</translate>
*
*

<translate>
==References== 
</translate>
<references/>

[[Category:Import/Export|Import/Export]]

----
''Sample content adapted from [[mediawikiwiki:Manual:Importing_XML_dumps]] on mediawiki.org, licensed under [https://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA 4.0].''

Manual/User rights

Admin — Sat, 25 Jul 2026 17:02:11 GMT

Seed from mediawiki.org for Seekmodo connector demo

Show changes

Manual/Extensions

Admin — Sat, 25 Jul 2026 17:02:11 GMT

Seed from mediawiki.org for Seekmodo connector demo

New page

<languages/>

<translate>

An '''extension''' lets you customise how MediaWiki looks and works.
</translate>

* <translate> System administrators can [[<tvar name=1>#Installing an extension</tvar>|install]] (or remove) extensions on the MediaWiki installations that they manage.</translate>
* <translate> Developers can [[<tvar name=1>#Developing extensions</tvar>|write new extensions]] or contribute to existing extensions.</translate>

{{Note|inline=0|type=info
|1=<translate> While some extensions are maintained by MediaWiki developers, others are developed by third parties and may be unmaintained.</translate> <translate> As a result, many extensions may contain bugs—including, in some cases, security vulnerabilities.</translate> <translate> Not all extensions are compatible with every version of MediaWiki, and they may not function reliably when used together.</translate>

<translate> Use extensions at your own risk, particularly those tagged as insecure.</translate> <translate> If an extension requires patches to the core software, make sure to back up your database beforehand to minimize the risk of breaking your wiki.</translate>
}}

<translate>
== Selecting extensions == 

=== Bundled extensions === 


Several extensions are as standard.
</translate>

<translate> These extensions should generally be of high utility, perform efficiently, be stable, be well-written, and have no known major security issues.</translate>
<translate> They should also be compatible with the latest versions of MediaWiki, and with each other (i.e. one extension shouldn't block the functions of another).</translate>
<translate> A bundled extension may have a dependency on one or more other extensions, as long as those are also bundled.</translate>

<translate> Site admins get these automatically when installing or upgrading MediaWiki.</translate>
<translate> When upgrading MediaWiki, any extension upgrades will be automatically applied as well.</translate>
<translate> Site admins may choose to uninstall any of these, if they wish.</translate>

<translate> There are open, ongoing discussions about which extensions should be part of this group.</translate>
<translate> You can .</translate>
<translate> Extensions will be bundled once the developers reach a consensus to do so.</translate>

<translate>

An extension may be removed from bundling if its functionality is merged into , it is replaced by an alternative, or in the unlikely event of any unsolvable major security vulnerabilities being discovered.

=== Browsing extensions === 


Browse <tvar name=1></tvar>, or <tvar name=2></tvar> to see the full range of extensions that are available.

=== Checking installed extensions === 
</translate>
<translate> Which extensions are active on an instance of MediaWiki can be checked by accessing the <tvar name=1>[[Special:Version]]</tvar> page, and scrolling down to the heading ''Installed extensions'' (anchor <tvar name=2><code>#mw-version-ext</code></tvar>).</translate>
<translate> For example, [[<tvar name=1>Special:Version#mw-version-ext</tvar>|these extensions]] are installed on this wiki, and [[<tvar name=2>W:Special:Version#mw-version-ext</tvar>|these extensions]] are active in the English Wikipedia.</translate>

<translate>
=== Popular extensions === 
</translate>
<translate> <tvar name="1"></tvar> counts wikis that extensions are installed on.</translate>
<translate> This represents actual installations and not just downloads (i.e. it queries the wiki's APIs), but it is also (as of 2023) not completely up-to-date.</translate>
<translate> It also doesn't count installations on private wikis.</translate>

<translate>
== Installing an extension == 
</translate>
: ''<translate> For further guidance, see also <tvar name=1></tvar></translate>''

<translate> MediaWiki is ready to accept extensions just after [[<tvar name=man>Special:MyLanguage/Manual:Installation</tvar>|installation]] is finished.</translate>
<translate> To add an extension follow these steps:</translate>

# '''<translate> Before you start</translate>'''
#: <translate> Many extensions provide instructions designed for installation using Unix commands.</translate> <translate> You require shell access (SSH) to enter these commands listed on the extension help pages.</translate>
# '''<translate> Download your extension</translate>'''
#: <translate> [[<tvar name=special>Special:ExtensionDistributor</tvar>|Extension Distributor]] helps you to select and download most of the popular extensions.</translate>
#: <translate> Extensions are usually distributed as modular packages.</translate> <translate> They generally go in their own subdirectory of <tvar name=IP><code>/extensions/</code></tvar>.</translate> <translate> A list of extensions stored in the Wikimedia [[<tvar name=gerrit>Special:MyLanguage/Gerrit</tvar>|Git repository]] is located at <tvar name=extensions>[[phab:diffusion/MEXT/browse/master/|git:mediawiki/extensions]]</tvar>.</translate> <translate> Some extensions [[<tvar name=cat>Special:MyLanguage/Category:Extensions which host their code in-wiki</tvar>|don't use version control]] and are not recommended.</translate>
#: <translate> Some extensions are also available in [[<tvar name=1>Special:MyLanguage/Software bundles</tvar>|bundles]], <tvar name=composer></tvar> or [[<tvar name=2>Special:MyLanguage/Comparison of extensions in distributions</tvar>|package repositories]].</translate>
#: <translate> It's recommended to read the <tvar name=1>README</tvar> file before installation.</translate> <translate> It usually contains important info about configuration.</translate>
# '''<translate> Install your extension</translate>'''
#: <translate> At the end of the <tvar name=LocalSettings><code></code></tvar> file, add:</translate>
#: <syntaxhighlight lang="php">
wfLoadExtension( 'ExtensionName' );
</syntaxhighlight>
#: <translate> This line forces the PHP interpreter to read the extension file, and thereby make it accessible to MediaWiki.</translate>
#: <translate> Some extensions can conflict with maintenance scripts, for example if they directly access <tvar name=1><code>$_SERVER</code></tvar> (not recommended).</translate> <translate> In this case, they can be wrapped in the conditional so maintenance scripts can still run.</translate>
#: <syntaxhighlight lang="php">
if ( !$wgCommandLineMode ) {
wfLoadExtension ( 'ExtensionName' );
}
</syntaxhighlight>
#: <translate> The maintenance script <tvar name=ImportDump></tvar> will fail for any extension which requires customised namespaces which is ''included'' inside the conditional above such as <tvar name=1></tvar>, <tvar name=2></tvar>.</translate>

:
: {{Note|1=<translate> While this installation procedure is sufficient for most extensions, some require a different installation procedure.</translate> <translate> Check your extension's documentation for details.</translate>}}
: {{Note|1=<translate> If you want to alter configuration variables in <tvar name=1><code>LocalSettings.php</code></tvar>, you have to do this typically '''after''' including the extension.</translate> <translate> Otherwise defaults defined in the extension will overwrite your settings.</translate>}}

<translate>
=== Upgrading an extension === 
</translate>
<translate> Some extensions require to be updated whenever you update MediaWiki, while others work with multiple versions.</translate>
<translate> To upgrade to a new version of an extension:</translate>

# <translate> Download the new version of the extension</translate>
# <translate> Replace all the extension files in the <tvar name=1><code>extensions/ExtensionName</code></tvar> directory with the new files.</translate> <translate> Do not remove the extension configuration present in <tvar name=1><code>LocalSettings.php</code></tvar></translate>
# <translate> If the extension requires changes to the MediaWiki database, you will need to run the <tvar name=1></tvar> maintenance script.</translate> <translate> Most extensions will mention if this script needs to be run or not.</translate> <translate> (Perform backup of your data before executing the script).</translate> <translate> If you don't have command line access, you can also use the [[<tvar name=man>Special:MyLanguage/Manual:Upgrading#Web_updater</tvar>|web updater]].</translate>

{{Note|1=<translate> These instructions cover 99% of extensions.</translate> <translate> If the specific extension you are upgrading has instructions that differ from these, you should probably follow the specific extension's instructions</translate>}}

<translate>
=== Uninstalling an extension === 


Remove the line from <tvar name=1><code>LocalSettings.php</code></tvar> with the extension name to uninstall it:
</translate>

<syntaxhighlight lang="php">
wfLoadExtension( 'ExtensionName' );
</syntaxhighlight>

<translate>

* You must also remove any lines pertaining to the configuration of the extension.

== Developing extensions == 
</translate>
<translate> MediaWiki core provides several ways for extensions to change the behavior and appearance of a wiki.</translate>
<translate> Various give extensions flexibility to add features and functionality, such as displaying a special page or defining an API module.</translate>
<translate> To get started, see the .</translate>
<translate> Before writing a new extension, consider contributing to an or helping with an .</translate>

<translate> Users can also make a general request on Phabricator, and hope that your good idea is picked up by a developer.</translate>
<translate> See <tvar name=1>https://phabricator.wikimedia.org/tag/mediawiki-extension-requests/</tvar></translate>

<translate>
== See also == 
</translate>

*
*
*
* – <translate> Information about translating extensions.</translate>
* [[Special:ExtensionDistributor]] – <translate> Includes a list of the 15 most downloaded extensions in Wikimedia version control</translate>
* [https://extloc.toolforge.org/ extloc] – <translate> Where are MediaWiki extensions deployed in Wikimedia production?</translate>
* [[API:Siteinfo#Extensions]]
*
*
*
*

[[Category:Customization techniques|Customization techniques]]
[[Category:Extension creation]]

----
''Sample content adapted from [[mediawikiwiki:Manual:Extensions]] on mediawiki.org, licensed under [https://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA 4.0].''

Manual/Upgrading

Admin — Sat, 25 Jul 2026 17:02:10 GMT

Seed from mediawiki.org for Seekmodo connector demo

Show changes

Manual/Short URL

Admin — Sat, 25 Jul 2026 17:02:10 GMT

Seed from mediawiki.org for Seekmodo connector demo

New page

<languages/>
</tvar>.</translate>}}

<translate> '''Short URLs''' or '''URL Rewrites''' hide php file extensions from the page address.</translate>
<translate> Please take a few minutes to devise a stable URL structure for your website before getting started, to reduce problems later.</translate>

<translate>
== Introduction == 

=== Goal === 


The default MediaWiki installation path looks like this:
</translate>

: <code>/var/www/html/mediawiki</code> ''<translate> (installed as root user)</translate>''
: <code>/home/johndoe/public_html/mediawiki</code> ''<translate> (installed with a shared hosting provider)</translate>''

<translate>

MediaWiki's default page addresses looks like these examples:
</translate>

: <code><nowiki>https://example.org/w/index.php/Page_title</nowiki></code> ''<translate> (recent versions of MediaWiki, without [[w:Common Gateway Interface|CGI]] support)</translate>''
: <code><nowiki>https://example.org/w/index.php?title=Page_title</nowiki></code> ''<translate> (recent versions of MediaWiki, with CGI support)</translate>''

<translate>

Using the methods outlined on this page, we can configure something like this:
</translate>

: <code><nowiki>https://example.org/wiki/Page_title</nowiki></code> <translate> This is the most common configuration, same as on Wikipedia, though not the default because it requires server-side modifications</translate>
: <code><nowiki>https://example.org/view/Page_title</nowiki></code>
: <code><nowiki>https://wiki.example.org/view/Page_title</nowiki></code>
: <code><nowiki>https://example.org/Page_title</nowiki></code>
: <code><nowiki>https://wiki.example.org/Page_title</nowiki></code>

<translate> Some people do not recommend the last two configurations.</translate>
<translate> See <tvar name=1></tvar> for potential problems and solutions.</translate>

<translate>
=== Advantages & disadvantages === 


* '''Advantage''': Short URLs hide some technical details from end-users, which can be desirable for site owners. Among other things, this means they can be kept stable when the underlying software changes.</translate> <translate> (See above for the difference between MediaWiki's default URL structure with CGI enabled vs without.)</translate> <translate> They are also easier to read, remember, and manipulate for visitors.</translate> <translate> Additionally, short URLs offer an advantage over the default URLs for [[w:Search engine optimization|Search engine optimization]], as URLs containing <tvar name=1><code>?</code></tvar> can be treated less favorably by search engines when calculating page rank.</translate>
<translate>

* '''Disadvantage''': Requires configuration, so, depending on the hosting environment you are using, it might be difficult to recreate.</translate> <translate> However, as every widely used webserver is capable of being configured to use short URLs, most paid web hosting services should support this feature. Any host that doesn't offer you this feature is not worth your money.</translate>

<translate>
== Guides == 
</translate>
<translate> Our official guides for short URL configuration for different web servers.</translate>
<translate> Pick your web server's configuration from this list.</translate>
<translate> If you don't know what server software you are using, then it is most likely Apache.</translate>

* (<translate> or</translate> LiteSpeed)
*
*

<translate>
== Other how-to mini-guides == 
</translate>
{{note|text=<translate> These guides are old and are almost entirely bad advice.</translate> <translate> These will eventually be deleted one by one as our official guides above are created for different webservers.</translate>}}
<translate> Anyone is welcome to create a how-to solution page and list it below.</translate>
<translate> Please use a sensible name for the page, one that fits in with the below names.</translate>
<translate> When each unique solution has its own page, readers can skip complexity they do not want.</translate>
<translate> Keep it simple, readable, short, with a separate page per separate solution.</translate>

<translate>

'''To help others find out which Short URL methods really work, after trying each method please edit the page and increase the "worked" or "didn't_work" numbers for that guide and make a brief (or long, your choice) description on what went wrong by clicking the link on your number.'''

=== URL like - example.com/wiki/Page_title === 
</translate>

</tvar> are defined.</translate>}}

<translate>
==== Root access ==== 
</translate>
<translate> These methods require that you have access to the server configuration.</translate>
<translate> If you are on a shared host, you most likely don't.</translate>
<translate> In this case you will be required to use a method that requires "no root access".</translate>
<translate> You can jump directly to the [<tvar name=url>https://shorturls.redwerks.org/</tvar> MediaWiki ShortURL Builder tool] and follow the on-screen instructions.</translate>
<translate> Select "I don't have root access" after entering your wiki's URL.</translate>

<translate>

(for Apache guidance, see the link in the [[<tvar name=guides>#Guides</tvar>|Guides]] section).
</translate>

<translate>
=== URL like - example.com/Page_title === 
</translate>

<translate>

How to create <code>example.com/Page_title</code> URLs:
</translate>

{{guide |name=Page title - nginx, Root Access, PHP as a CGI module |show=<translate nowrap> Page title - nginx, Root Access, PHP as a CGI module</translate> |worked=6 |didn't_work=}}
{{guide |name=Page title -- Windows & Apache without 403 on Special Pages |show=<translate nowrap> Page title -- Windows & Apache without 403 on Special Pages</translate> |worked=3 |didn't_work=}}

<translate>
=== URL like - wiki.example.com/Page_title === 
</translate>

<translate>

How to create <code>wiki.example.com/Page_title</code> URLs:
</translate>

<translate>
== Troubleshooting == 

=== Ampersand (<tvar name=1>&</tvar>) problem === 
</translate>
<translate> The ampersand problem shows up when you have page titles with symbols in them (such as <tvar name=1></tvar>) which, despite being correctly encoded in the link, are not being passed correctly from <tvar name=2>mod_rewrite</tvar> to the script.</translate>
<translate> This manifests in 404 page-not-found errors, because the title gets cut off at the special character.</translate>
<translate> For example, clicking on a link to "John & Maria's page" gets a 404, because MediaWiki is looking for a page named "John ".</translate>

<translate> This is because ampersands in long-form names are treated as [[w:Query string|query string]] separators, and would never reach the PHP [[w:Run time (program lifecycle phase)|runtime environment]].</translate>
<translate> This is caused by an old and problematic <tvar name=1>mod_rewrite</tvar> bug.</translate><ref><translate> [<tvar name=url>https://bz.apache.org/bugzilla/show_bug.cgi?id=34602</tvar> Bugzilla <tvar name=1>mod_rewrite</tvar> for ampersand bug], partially resolved for some users, but only after 13 years</translate></ref>

<translate>

'''Solution:'''
</translate>

<translate> This issue is caused by the <tvar name=1><code>?title=$1</code></tvar> portion of rewrite rules like <tvar name=2><code>/index.php?title=$1</code></tvar> which is completely unnecessary and harmful.</translate>
<translate> MediaWiki parses paths directly from the <tvar name=1>REQUEST_URI</tvar>, so rewrite everything to <tvar name=2>/index.php</tvar>.</translate>

<translate>
=== Purging cache === 


If you notice that your changes to <tvar name=1><code></code></tvar> in <tvar name=2><code>LocalSettings.php</code></tvar> are not being reflected in <tvar name=3><code>example.com/wiki/Main_Page</code></tvar>, it may be due to MediaWiki's caching of the links according to previous settings.


Go to <tvar name=1><code>example.com/wiki/Main_Page?action=purge</code></tvar> to force MediaWiki to regenerate the cached links.


Also you can:
</translate>

# <translate> execute the MySQL query <tvar name=1><code>TRUNCATE objectcache;</code></tvar>, or</translate>
# <translate> Ensure <tvar name=2></tvar> is updated (if <tvar name=3></tvar> is enabled, all you have to do is edit <tvar name=1></tvar> to purge it)</translate>

<translate>
== Redirect visitor of your domain to your wiki == 


Our official guides for short url configuration include recommendations on how to point the root of your site to your wiki using your short url config.


For example our [[<tvar name=1>Special:MyLanguage/Manual:Short URL/Apache</tvar>|Apache guide]] recommends using this to point your site root to your wiki:
</translate>

<syntaxhighlight lang="apache">
RewriteRule ^/*$ %{DOCUMENT_ROOT}/w/index.php [L]
</syntaxhighlight>

<translate> Note that we do '''not''' recommend doing a HTTP redirect to your wiki path or main page directly.</translate>
<translate> As redirecting to the main page directly will hard-code variable parts of your wiki's page setup into your server config.</translate>
<translate> And redirecting to the wiki path will result in two redirects.</translate>
<translate> Simply rewrite the root path to MediaWiki and it will take care of the 301 redirect to the main page itself.</translate>

<translate>

If using VirtualHosts, place the rewrite rules into the virtual host declaration!

== Moving a wiki from <tvar name=1>/wiki</tvar> to <tvar name=2>/w</tvar> == 
</translate>
<translate> A common beginner's mistake is to install MediaWiki itself (the source code, not the short URL) in <tvar name=1><code>/wiki</code></tvar> instead of <tvar name=2><code>/w</code></tvar>.</translate>
<translate> Once installed they would realize the mistake when trying to configure Short URLs (which would become difficult as the virtual path then conflicts with the real path).</translate>

<translate>

There is a manual for [[<tvar name=1>Special:MyLanguage/Manual:Moving a wiki</tvar>|moving a wiki]] in general, however that is too complicated if all you need is to change the installation directory (and stay on the same server, same database and same hostname).


Here is what you have to do:


* Backup <tvar name=1><code>LocalSettings.php</code></tvar> and any other config files you may have created (such as your <tvar name=2><code>.htaccess</code></tvar>).</translate>
<translate>

* Rename the installation directory of MediaWiki on your server from <tvar name=1><code>/wiki</code></tvar> to <tvar name=2><code>/w</code></tvar>.</translate>
<translate>

* Set <tvar name=1><code></code></tvar> in <tvar name=2><code>LocalSettings.php</code></tvar> to <tvar name=3><code>"/w"</code></tvar> and remove (or comment out) any definition of <tvar name=4><code>$wgArticlePath</code></tvar> (this variable will be changed again when setting up Short URLs, further on)</translate>
<translate>

* At this point your wiki should be working normally at <tvar name=1><code>example.org/w</code></tvar></translate>
<translate>

* Now go through [[<tvar name=guides>#Guides</tvar>|the regular guide]] to set up short URLs</translate>
<translate>

* Perform a few tests on your wiki to make sure nothing is broken.</translate> <translate> Edit a page, visit a few different pages, etc.</translate> <translate> If anything seems abnormal, revert the changes by restoring your backup of <tvar name=1><code>LocalSettings.php</code></tvar> and other relevant files you might have changed during configuration of short URLs and rename your folder back to <tvar name=2><code>/wiki</code></tvar>.</translate>

<translate> '''Note for shared hosting users:''' Many shared hosting plans offer an application manager to automatically Install, Update and Backup applications such as MediaWiki.</translate>
<translate> If your plan has this and if you want to keep using these features, you should contact their tech support and let them know you just manually changed your MediaWiki installation directory.</translate>

<translate>
== Tricks == 
</translate>

<translate>
== See also == 


*[[w:Common Gateway Interface#Workarounds for scripting languages|Explanation of what CGI modules are]]
</translate>
* - <translate> configuration setting that defines whether to use 'pretty' URLs or not</translate>
<translate>

*[[<tvar name=1>Special:MyLanguage/Manual:Wiki in site root directory</tvar>|Notes on placing your wiki installation in site root directory]]</translate>
* - <translate> configuration setting that you can use to define 'pretty' URLs for other actions, like edit or history</translate>
<translate>

* [[<tvar name=1>Special:MyLanguage/Requests for comment/Clean up URLs</tvar>|Clean up URLs RFC]] - proposes "cleaner URLs for editing, previewing skins, etc."

== External links == 


*[<tvar name=url>https://httpd.apache.org/docs/current/mod/mod_rewrite.html</tvar> Apache Module <tvar name=1>mod_rewrite</tvar>] - rewrite requested URLs on the fly</translate>
<translate>

*[<tvar name=url>https://shorturls.redwerks.org/</tvar> MediaWiki Short URL Builder Tool] - ''A tool that can automatically generate a short url configuration more reliably than the configurations in these manual pages.''</translate>
<translate>

* [<tvar name=url>https://www.nngroup.com/articles/url-as-ui/</tvar> URL as UI] by [[w:Jakob Nielsen (usability consultant)|Jakob Nielsen]] on the importance of persistent, usable URLs.

== References == 
</translate>
<references/>


[[Category:Configure|Configure]]
[[Category:Wiki page URLs|Wiki page URLs]]

----
''Sample content adapted from [[mediawikiwiki:Manual:Short_URL]] on mediawiki.org, licensed under [https://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA 4.0].''

Manual/Installation guide

Admin — Sat, 25 Jul 2026 17:02:09 GMT

Seed from mediawiki.org for Seekmodo connector demo

New page

#REDIRECT [[Manual:Installing MediaWiki]]

----
''Sample content adapted from [[mediawikiwiki:Manual:Installation_guide]] on mediawiki.org, licensed under [https://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA 4.0].''

Manual/Config script

Admin — Sat, 25 Jul 2026 17:02:09 GMT

Seed from mediawiki.org for Seekmodo connector demo

New page

<languages/>

<translate> After downloading and extracting MediaWiki on your web server, complete the basic setup by running the configuration script. This script allows you to tell MediaWiki the information it needs in order to get the wiki up and running.</translate>
<translate> The following steps describe how to complete basic setup:</translate>

<translate>
== Running the MediaWiki configuration script in the web browser == 
</translate>
[[File:MediaWiki_1.38.2_Config_script_2.png|thumb||left|right}}|250px|<translate> MediaWiki 1.38 web installer</translate>]]
<translate> In the following examples, it is assumed that your website is located at <tvar name=1><code><nowiki>http://www.example.com/</nowiki></code></tvar>.</translate>
<translate> The physical location on your server depends on your web server software configuration.</translate>
<translate> Adjust the examples as needed.</translate>

# <translate> Open a web browser and browse to the website address or path that you configured for MediaWiki in the web server software.</translate>
# <translate> You will see the version of MediaWiki which you extracted and a link to "Please set up the wiki first."</translate> <translate> Click on the link to begin the configuration script.</translate><br/><translate> For reference (in case you want to go there directly), this is located in MediaWiki's <tvar name=1><code>mw-config</code></tvar> directory (so using the example above you would go to <tvar name=2><code><nowiki>http://www.example.com/mw-config/</nowiki></code></tvar>, or on a local machine <tvar name=localhost><code><nowiki>http://localhost/mw-config/</nowiki></code></tvar>).</translate>
# <translate> After selecting the language, the configuration script performs some environmental checks.</translate>
# <translate> Follow the instructions on the pages to connect to the database, create the MediaWiki administrator account, and to set further settings such as the logo or skin.</translate></code></tvar> stores the database user's ''password in plain text'', it is strongly suggested that you create a wiki specific database account (i.e. not root).</translate>}}
# <translate> The script will populate the database and write a configuration file.</translate>
# <translate> After the configuration script has finished, download the generated configuration file <tvar name=1><code></code></tvar> and place the file in the base directory of your MediaWiki installation.</translate>
<translate> <tvar name=1><code></code></tvar> contains all the information needed by MediaWiki to run.</translate>
{{Note|type=warning|1=<translate> Set stringent file permissions which system users can read and write the <tvar name=1><code>LocalSettings.php</code></tvar> file.</translate><br/><translate> For example, set <code>[[w:chmod|chmod 600]]</code> and <code>[[w:chown|chown]] <webserver owner></code> (Owner read and write, no other permissions).</translate>}}

<translate>

Your wiki should now be ready to use. Browse to the address that you installed MediaWiki to.


Continue with more advanced configuration on <tvar name=1></tvar>.

== Command-line alternative == 


Alternatively, you can run a command-line installer instead of the configuration script in the web browser.


There are several installers available which you can use based on your needs:
</translate>

* <code>php ./maintenance/run.php </code> – <translate> Creates a new <tvar name=1><code>LocalSettings.php</code></tvar> using CLI parameters.</translate>
* <code>php ./maintenance/run.php </code> – <translate> Uses an existing <tvar name=1><code>LocalSettings.php</code></tvar> file to retrieve configuration.</translate> <translate> Useful for wiki farms and docker setups.</translate>

[[Category:Installation|Installation]]

----
''Sample content adapted from [[mediawikiwiki:Manual:Config_script]] on mediawiki.org, licensed under [https://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA 4.0].''

Help/Watchlist

Admin — Sat, 25 Jul 2026 17:02:08 GMT

Seed from mediawiki.org for Seekmodo connector demo

New page

<languages />

<translate> Your '''watchlist''' is a display for [[<tvar name=1>Special:MyLanguage/Help:Tracking changes</tvar>|tracking changes]], similar to the <tvar name=rc>}}</tvar> display, but limited to showing changes only across your set of "watched" pages.</translate>
<translate> You can see your watchlist by following the "<tvar name=watchlist>''''</tvar>" link in your account menu (on the top right).</translate>
<translate> This feature is only available to users who have registered and logged in.</translate>

<translate>
== Add pages to watchlist == 
</translate>
<translate> Before you see anything interesting here, you have to actually add some pages to your watchlist.</translate>
<translate> Do so by navigating to a page that interests you, and click the star icon <tvar name=star>[[File:OOjs_UI_icon_star.svg|16px|link=|class=skin-invert|]]</tvar> (or the <tvar name=watch><code></code></tvar> tab).</translate>

<translate>

A page already in your watchlist will be marked with a star <tvar name=star>[[File:OOjs_UI_icon_unStar.svg|16px|link=|class=skin-invert|]]</tvar> (or an <tvar name=watch><code></code></tvar> tab).


If you want to remove pages from your watchlist, click on the star icon <tvar name=star>[[File:OOjs_UI_icon_unStar.svg|16px|link=|class=skin-invert|]]</tvar> (or the <tvar name=watch><code></code></tvar> tab).

=== Watchlist expiry === 
</translate>
<translate> You can optionally select to watch a page for a temporary period of time.</translate>
<translate> Once the watch period has expired, the page will be automatically removed from your watchlist.</translate>
<translate> You can update the watch period at any time, including switching from temporary to permanent status.</translate>
<translate> Temporarily watched pages are usually represented by a half star (as opposed to a full star, which represents permanently watched pages).</translate>
<translate> For documentation on how to use the feature, please visit <tvar name=1></tvar>.</translate>

<translate>
== Why a watchlist == 
</translate>
<translate> The watchlist feature is mainly useful on a very busy wiki where the <tvar name=rc><code></code></tvar> display becomes too overwhelming with many changes you don't want to follow.</translate>
<translate> On a typical low traffic wiki, you can normally see all of the editing activity across the whole wiki without feeling overwhelmed.</translate>
<translate> On a more busy wiki you will find that many edits are taking place on pages which you personally find less interesting.</translate>
<translate> To help track changes which are more interesting, start !</translate>

<translate> Typically you would watch pages related to your interest areas, and also pages where you care most about the content.</translate>
<translate> If you make a significant edit to a page, you might want to watch the page (so you know when there are any follow-up edits).</translate>
<translate> Note that there is a also a checkbox on the edit screen ("<tvar name=watch>''''</tvar>") for this purpose.</translate>

<translate> Your watchlist is personal.</translate>
<translate> You can watch any page you want.</translate>
<translate> That choice will remain private.</translate>

<translate>
== Use your watchlist == 
</translate>
<translate> On the watchlist page, some page names appear in bold.</translate>
<translate> This indicates whether or not you have visited the page to see the change.</translate>
<translate> It's a bit like read/unread emails in an email inbox.</translate>
<translate> The <tvar name=rc></tvar> page will also have some new bold highlighting, but for a different reason.</translate>
<translate> Here bold is indicating edits to pages on your watchlist.</translate>

<translate>

[[<tvar name=1>Special:MyLanguage/Help:New_filters_for_edit_review</tvar>|You can combine different kinds of filters]] to display the results you want.
</translate>

<translate> To improve the filtering, you can also add private labels to your watchlist pages.</translate>
<translate> See <tvar name=1></tvar> for more information about this feature.</translate>

<translate>
== Email notifications == 
</translate>
<translate> According to the relevant <tvar name=1></tvar>, changes to pages you watch may also be notified to you by email.</translate>
<translate> The main preference for this is <tvar name=1><code></code></tvar>.</translate>

<translate>

After receiving an email notification for a page, you have to visit the page while logged in if you want to be notified of further changes to the same page.
</translate>


<translate>
==Watchlist feed with token== 


You can set up an RSS or Atom feed of your watchlist that is accessible even when logged out:</translate>

<translate>

* Get your watchlist token from <tvar name=2>[[Special:Preferences#mw-prefsection-watchlist-tokenwatchlist]]</tvar></translate>
<translate>

* Your watchlist RSS feed can be found at <tvar name=url><span class="plainlinks">https:/api.php?action=feedwatchlist&wlowner=USERNAME&wltoken=TOKEN</span></tvar>, where USERNAME is your username without the ''User:'' prefix and TOKEN is the watchlist token.</translate>
<translate>

* If you would prefer an Atom feed rather than an RSS one, add "<tvar name=1><code>&feedformat=atom</code></tvar>" to the URL of your feed.</translate>
<translate>

* To further customise your watchlist feed add different parameters to the URL, see <tvar name=1></tvar>.

== See also == 
</translate>
*
* <translate> [[w:Wikipedia:Syndication|Wikipedia:Syndication]] - about RSS and Atom feeds</translate>

[[Category:Help|Watchlist]]
[[Category:Watchlist]]

----
''Sample content adapted from [[mediawikiwiki:Help:Watchlist]] on mediawiki.org, licensed under [https://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA 4.0].''

Help/Searching

Admin — Sat, 25 Jul 2026 17:02:08 GMT

Seed from mediawiki.org for Seekmodo connector demo

New page

<languages/>

</tvar>.</translate>}}
<translate>

The quickest way to find information in <tvar name=1></tvar> is to look it up directly. On every page there is a '''<tvar name=search>}}</tvar>''' box.
</translate>

<translate> Enter keywords and phrases and press ''Enter'' or ''Return'' or click the magnifying glass icon (or Search or Go button when using other skins).</translate>
<translate> If a page has the same title as what you entered, you jump straight to that page.</translate>
<translate> Otherwise, it searches all pages on the wiki (with some restrictions, see below), and presents a list of articles that matched your search terms, or a message informing you that no page has all the key words and phrases.</translate>

<translate>
== How it works == 


* It searches all pages on the wiki with some restrictions.</translate>
<translate>

* The article content is searched in its raw (wikitext) form - i.e., it searches the text that appears in the edit box when you click "<tvar name=edit>}}</tvar>", not the rendered page.</translate> <translate> This means that content coming from an included template will not be picked up, but the target of piped links will be.</translate>
<translate>

* The search functionality can be considered to operate on '''whole words''', separated by spaces or other punctuation marks.</translate> <translate> So if your search term includes the word 'book', the results will not include pages that only have the word 'books' or 'booklet'.</translate> <translate> And if your search term includes the term 'inter', the results will not include pages that only have the word 'international', but they may include pages that have the term 'inter-national'.</translate>
<translate>

* The results will only include pages that contain '''all''' the words in your search.</translate>
* <translate> You can search for all words that begin with a prefix by adding <tvar name=1><code>*</code></tvar> at the end of a word in your query.</translate> <translate> For example, <tvar name=1><code>book*</code></tvar> will return results for <tvar name=2><code>book</code></tvar> and <tvar name=3><code>book'''s'''</code></tvar>.</translate>
<translate>

* You can search for a phrase using double quotes.</translate> <translate> A phrase can be considered to consist of '''whole words''', so the phrase 'Prime Minister' will '''not''' be found by a search for "ime Min", but it '''will''' be found by a search for "Prime Minister".</translate>

<translate>
== Restricting the search == 


If you click the <tvar name=search><code></code></tvar> button without filling in anything, you will be taken to <tvar name=1><code>Special:Search</code></tvar> which gives you extra searching options (also available from any search results list).


You may find it useful to restrict a search to pages within a particular [[<tvar name=help-ns>Special:MyLanguage/Help:Namespaces</tvar>|namespace]] e.g., only search within the <tvar name=ns2></tvar> pages. Check the namespaces you require for this search.

== See also == 
</translate>
*
*
*
*
* <translate> Alternative backends:</translate>
**
*

__NOTOC__

[[Category:Help|Searching]]
[[Category:Search|Searching]]

----
''Sample content adapted from [[mediawikiwiki:Help:Searching]] on mediawiki.org, licensed under [https://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA 4.0].''

Help/Tables

Admin — Sat, 25 Jul 2026 17:02:07 GMT

Seed from mediawiki.org for Seekmodo connector demo

Show changes

Help/Images

Admin — Sat, 25 Jul 2026 17:02:06 GMT

Seed from mediawiki.org for Seekmodo connector demo

Show changes

Help/Categories

Admin — Sat, 25 Jul 2026 17:02:05 GMT

Seed from mediawiki.org for Seekmodo connector demo

New page

<languages />

<translate>

Categories, a software feature of MediaWiki, provide automatic indexes that are useful as tables of contents.


You can categorise pages and files by adding one or more '''Category''' tags to the content text. These tags create links at the bottom of the page that take you to the list of all pages in that category, which makes it easy to browse related articles.

== Summary == 


Each of the pages in the '''Category''' [[<tvar name=ns>Special:MyLanguage/Help:Namespaces</tvar>|namespace]] represents a so-called '''category''', a grouping of related pages, and contains an index for the pages of its category. For example, this page belongs to "<tvar name=cat></tvar>". If you open the category page, you will see a link to this page there.


When a page belongs to one or more categories, these categories appear at the bottom of the page (or in the upper-right corner, depending on the [[<tvar name=1>Special:MyLanguage/Help:Preferences</tvar>|skin]] being used).


The category pages themselves contain 2 parts:


* at their beginning, an optional part may contain text that can be edited, like any other page,
* at their end, an ever present, automatically generated, alphabetical list of all pages in that category, in the form of links. In fact, in the Unicode sort order.


To assign a category to a page, simply add the link "<nowiki>[[</nowiki>Category:''Category name'']]" to the page's wikitext. The usual place to add it is at the bottom of the page.


To link a category page within a page as a normal wiki link (without adding the page to the category), prefix the link name with a colon. For example:


A new category can be [[<tvar name=1>Special:MyLanguage/Help:Starting a new page</tvar>|created]] before assigning any page to it, in the same way as any other regular page.


Individual wikis may have their own top-level categories, such as [[w:Category:Contents|Category:Contents]] on Wikipedia.


For a complete list of all categories which have at least one page, see <tvar name=1>[[Special:Categories]]</tvar>.


For a complete list of all created/edited categories, including the ones that don't have any pages, see <tvar name=1>[[Special:Allpages/Category:]]</tvar> (note the colon at the end).

==Adding a page to a category== 


To add a page or uploaded file to a category, simply edit the page and add the following text (where '''''Name''''' is the name of the category you want to add it to).
</translate>

<nowiki>[[</nowiki>:'''''<translate> Name</translate>''''']]

<translate> Any number of <tvar name=2></tvar> tags may be added to the page and the page will be listed in all of them.</translate>
<translate> <tvar name=2></tvar> tags, along with placed in the sidebar, are usually added at the very bottom of the page for the convenience of other editors.</translate>

<translate>

On a categorised page, categories are displayed in the <tvar name=1><code>:</code></tvar> box strictly in the order they appear in the wikitext.
</translate>

<translate> (At least in MediaWiki 1.18.2) if a category is a subcategory of more than one parent, both hierarchies will be listed, but the tagged category will be stripped off all but one of these.</translate>
<translate> This creates the potential for what appear to be duplicate entries if a category with multiple parents ''and'' one of its parents are both tagged on a page.</translate>
<translate> For example suppose Maryanne is a subcategory of both Mary and Anne.</translate>
<translate> If a page tags categories Maryanne and Anne then the Category breadcrumbs will show</translate>

Anne
Anne
Mary -> Maryanne

<translate>

"Anne" appears to be duplicated, but what is meant is
</translate>

Anne
Anne -> Maryanne
Mary -> Maryanne

<translate>

This is a bug, and has been reported in <tvar name=1>[[phab:T35614]]</tvar>.

===Sort key=== 
</translate>
<translate> By default, a page is sorted within a category under the first letter of its name — ''without the namespace''.</translate>
<translate> Also, MediaWiki groups accented characters separately from their unaccented version, so pages starting by À, Á, Ä, will be listed under separate headings, instead of under heading A.</translate>
<translate> (If you have shell access, these defaults can be changed using <tvar name=CategoryCollation></tvar>.)</translate>

<translate>

A ''sort key'' specifies under which letter heading, and where in the category list, the page will appear.


There are two ways in which you can customise the category sortkey:
</translate>

* <translate> Generically, for all categories, by adding the <tvar name=1></tvar> magic word on the page.</translate>
* <translate> On an individual 'per category' basis, by placing the value inside the tag after a pipe character.</translate> <translate> For example, the tag below will add the page under heading <tvar name=1><code>S</code></tvar>.</translate>
<nowiki>[[</nowiki>:'''''<translate> Name</translate>'''''|'''''<translate> Sort</translate>''''']]

<translate> Whether or not sort keys are case-sensitive depends on your configuration settings.</translate>
<translate> The order of the sections within a category follows the Unicode sort order. The sort key does not change the page title displayed in the category.</translate>

<translate>

Spaces and other characters are perfectly valid.

==Creating a category page== 


Categories exist even if their page has not been created, but these categories are isolated from others and serve little purpose for organisation or navigation.


A category is created by creating a page in the '''''Category:''''' namespace. A category page can be created the same way as other wiki pages (see <tvar name=help></tvar>); just add "<tvar name=code><code>:</code></tvar>" before the page title.


To avoid extra work, try searching within your wiki before creating a new category. The list of all categories can be found in <tvar name=1><code></code></tvar> in the "<tvar name=2>}}</tvar>" box of the [[<tvar name=3>Special:MyLanguage/Help:Navigation#Sidebar</tvar>|sidebar]].

==Managing the category hierarchy== 


Categories may belong to other categories in a hierarchy. Since category pages are much like any other page, a <tvar name=1></tvar> tag may be added to the bottom of a category page.


It is a good idea to organise all categories into a hierarchy with a single top level category. The category structure can take the form of a tree with separate branches, but more often will have a graph structure. Generally, there should be a contiguous chain of parent-child links between each category and the top level category.

=== Category tree === 
</translate>

<translate>

Since MediaWiki 1.31, <tvar name=1></tvar> extension is packaged by default, allowing <tvar name=2>[[Special:CategoryTree]]</tvar> and <tvar name=3></tvar> to provide a tree-like structure display for the categories.

==Hidden categories== 


The categories that a page is in are normally listed at the bottom of the page. In MediaWiki 1.13+, a category can be hidden from this list by adding the [[<tvar name=1>Special:MyLanguage/Help:Magic words</tvar>|magic word]] "<tvar name=2><code><nowiki>__HIDDENCAT__</nowiki></code></tvar>" to the category page.


Users can choose to see hidden categories in a separate <tvar name=1><code></code></tvar> list, by checking <tvar name=2><code></code></tvar> in the <tvar name=3><code></code></tvar> section of <tvar name=4>[[Special:Preferences]]</tvar>.
</translate>

<translate> Hidden categories are automatically added to <tvar name=1>[[:Category:]]</tvar>.</translate>
<translate> This category is specified in the system message <tvar name=1>[[MediaWiki:Hidden-category-category]]</tvar>.</translate>

<translate>
==Linking to a category== 


To create a link to a category, use a leading colon before the category name (without this colon, the current page would be added to the category):
</translate>

:<code><nowiki>[[</nowiki>::Help]]</code> → '''[[::Help]]'''

<translate>

To change the link text, write the text inside the link tag after a pipe:
</translate>

:<code><nowiki>[[</nowiki>::Help|<translate> Help category</translate>]]</code> → '''[[::Help|<translate> Help category</translate>]]'''

<translate>

[[<tvar name=1>Special:MyLanguage/Help:Redirects</tvar>|Redirect pages]] that redirect to categories must also use the colon, otherwise they will be added to the category instead of redirecting.

== Categories and templates (transcluded pages) == 


If you add <tvar name=1><syntaxhighlight lang="wikitext" inline>[[Category:Cats]]</syntaxhighlight></tvar> inside a template (a transcluded page), ''both'' the template and pages which transclude this template will be categorised in <tvar name=2>Cats</tvar>.


If you want ''only the template'' to be categorised, you should ensure to write category marker inside <tvar name=1><code></code></tvar> tags.


If you want ''only the pages which use the template'' to be categorised, but not the template itself, you should ensure to write category marker inside <tvar name=1><code></code></tvar> tags.
</translate>

<translate> Due to caching issues, editing categories applied through templates may take a while to be visible everywhere.</translate>
<translate> You can perform a [[<tvar name=1>Special:MyLanguage/Manual:Null edit</tvar>|null edit]] on a page to update immediately its categories.</translate>

<translate>
==Redirecting a category== 
</translate>
<translate> Like any other pages (templates, files, etc), category pages can be redirected to other normal or category pages.</translate>
<translate> However, '''unlike''' templates, files, and regular content pages, when you ''use'' a category, redirects will ''not'' apply (<tvar name=1>[[phab:T5311]]</tvar>).</translate>
<translate> For example:</translate>

{| class="wikitable"
! <translate> Premise</translate>
! <translate> What you write</translate>
! <translate> Result (categorization)</translate>
! <translate> Result (link behavior)</translate>
|-
| <translate> <tvar name=1><code>Category:A</code></tvar> redirects to <tvar name=2><code>Category:B</code></tvar></translate>
| <code><nowiki>[[Category:A]]</nowiki></code>
| <translate> The page is added to <tvar name=1><code>Category:A</code></tvar></translate>
| <translate> Visitors cannot access the category page (it immediately redirects to <tvar name=1><code>Category:B</code></tvar>)</translate>
|-
| <translate> <tvar name=1><code>Category:A</code></tvar> redirects to <tvar name=2><code>Category:B</code></tvar></translate>
| <code><nowiki>[[Category:B]]</nowiki></code>
| <translate> The page is added to <tvar name=1><code>Category:B</code></tvar></translate>
| <translate> Visitors can access it via <tvar name=1><code>Category:B</code></tvar> or <tvar name=2><code>Category:A</code></tvar> (normal redirect behavior)</translate>
|-
| <translate> <tvar name=1><code>Category:A</code></tvar> redirects to <tvar name=2><code>Category:B</code></tvar></translate>
| <code><nowiki>[[:Category:A]]</nowiki></code>
| <translate> The page is not categorized</translate>
| <translate> A direct link to <tvar name=1><code>Category:A</code></tvar> is created; normal redirect behavior applies on click</translate>
|-
| <translate> <tvar name=1><code>Category:A</code></tvar> redirects to <tvar name=2><code>Category:B</code></tvar></translate>
| <code><nowiki>[[:Category:B]]</nowiki></code>
| <translate> The page is not categorized</translate>
| <translate> A direct link to <tvar name=1><code>Category:B</code></tvar> is created; it behaves as expected</translate>
|}

<translate>

Because this behavior may be confusing, some Wikimedia sites use a "category redirect" template to mark redirected categories, allowing manual or automated cleanup of pages categorised there.

==Tracking categories== 
</translate>
<translate> Certain syntax issues, such as a broken image link, or too many expensive parser functions, can cause a page to be added to a tracking category.</translate>
<translate> Also, extensions may add pages to tracking categories, for example <tvar name=1></tvar>.</translate>
<translate> See <tvar name=1></tvar> for details.</translate>

<translate>
== Renaming a category == 


If you move a category, since [[<tvar name=1>#Redirecting a category</tvar>|redirect will not work for categorising]], all category tags will be wrong, so you have to fix them.

==See also== 
</translate>
*
* <translate> <tvar name=UseCategoryBrowser></tvar> - if this is set to true, under the first list each category is listed again, [[w:breadcrumb (navigation)|breadcrumb]]-style, with all its parent categories, sorted alphabetically.</translate>

[[Category:Help|Categories]]
[[Category:Category]]

----
''Sample content adapted from [[mediawikiwiki:Help:Categories]] on mediawiki.org, licensed under [https://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA 4.0].''

Help/Templates

Admin — Sat, 25 Jul 2026 17:02:05 GMT

Seed from mediawiki.org for Seekmodo connector demo

Show changes

Help/Links

Admin — Sat, 25 Jul 2026 17:02:04 GMT

Seed from mediawiki.org for Seekmodo connector demo

Show changes

Help/Navigation

Admin — Sat, 25 Jul 2026 17:02:03 GMT

Seed from mediawiki.org for Seekmodo connector demo

New page

<languages />

<translate> Every page on a MediaWiki site not only has information to show you but also allows you to move to other pages.</translate>
<translate> This is called "navigation".</translate>

<translate>

To help you navigate, every page on <tvar name=1></tvar>, has three main navigation elements:
</translate>

# <translate> The [[<tvar name=1>#Sidebar</tvar>|sidebar]] gives you access to important pages in the wiki such as <tvar name=2>[[Special:MyLanguage/Help:Recent changes|}}]]</tvar> or <tvar name=3>[[Special:MyLanguage/Help:Managing files|}}]]</tvar>.</translate> <translate> MediaWiki requires you to log in before seeing all of the sidebar options.</translate>
# <translate> Links (often called [[<tvar name=tabs>#Page tabs</tvar>|tabs]]) which relate to the page currently displayed: its associated discussion page, the version history, and – most notably – the edit link.</translate>
# <translate> [[<tvar name=links>#User Links</tvar>|User links]]; as an anonymous user, you'll see a link to create an account or log in.</translate> <translate> As a logged-in user you have a collection of personal links, including ones to your user page and [[<tvar name=preferences>Special:MyLanguage/Help:Preferences</tvar>|preferences]].</translate>

<translate> In addition to the standard navigation elements that each page has, a page will have its own unique information which appears in the larger main area of the page.</translate>
<translate> Generally within this information will be [[<tvar name=help>Special:MyLanguage/Help:Links</tvar>|links]] to other pages.</translate>

<translate> This page mainly documents the MonoBook and Vector [[<tvar name=skins>Special:MyLanguage/Manual:Skins</tvar>|skins]].</translate>
<translate> Appearances may be different when using other skins.</translate>
__TOC__

<translate>
== Sidebar == 
</translate>
[[Image:Vector Sidebar.png|framed||left|right}}|<translate> Example sidebar, shown along the page</translate>]]
<translate> The sidebar is displayed on the edge of the page below the site logo (if using the MonoBook or Vector skin).</translate>
<translate> This sidebar gives you access to important pages in the wiki such as Recent Changes or Upload File.</translate>

<translate>
=== Navigation === 
</translate>
<translate> Clicking on the logo brings you back to the main page of the wiki.</translate>
<translate> The links in the navigation section just below will take you to important pages of the wiki.</translate>
<translate> These links can be configured by site administrators.</translate>

<translate>
=== Toolbox === 


The <tvar name=toolbox>}}</tvar> contains a selection of links which change depending on what type of page you are viewing.
</translate>
; <translate> On all pages (except special pages)</translate>
:* <translate> <tvar name=1><code></code></tvar> takes you to a special page that lists the pages on that wiki which contain a link to the current page.</translate> <translate> This is helpful when you are looking for pages of related information.</translate> <translate> The "<tvar name=1>}}</tvar>" information can also be useful when you are refactoring wiki pages and need to check whether links to this page are still relevant after changes in the current page.</translate>
:* <translate> The "<tvar name=rcl>}}</tvar>" tool lists all recent changes in the pages linked to from the current page.</translate> <translate> Recent changes to all relevant template pages are included in the resulting page list.</translate> <translate> The <tvar name=1><code></code></tvar> option that can be set in the user [[<tvar name=preferences>Special:MyLanguage/Help:Preferences</tvar>|preferences]] applies, among other things, to "<tvar name=rcl>}}</tvar>".</translate>
; <translate> On all pages (including special pages)</translate>
:* <translate> "<tvar name=upload>}}</tvar>" displays a special page that allows logged-in users to upload images and other files to the wiki.</translate> <translate> Uploaded files can be linked from or embedded in wiki pages.</translate> <translate> This link is not displayed if file uploading is not enabled.</translate><br />''<translate> Uploading files, viewing files on the server, including them in wiki pages and managing the uploaded files is discussed in the [[<tvar name=managing-files>Special:MyLanguage/Help:Managing files</tvar>|managing files]] section of this manual.</translate>''
:* <translate> The "<tvar name=specialpages>}}</tvar>" tool lists the MediaWiki special pages.</translate> <translate> In MediaWiki terminology, a special page is one that presents information about the Wiki and/or allows access to administration activities for the wiki.</translate> <translate> For example, a list of users registered with the wiki, statistics about the wiki such as the number of pages and number of page edits, system logs, a list of orphaned pages, and so on.</translate> <translate> The content of these special pages is generated automatically when the special page is loaded.</translate><br />''<translate> The function and use of the default special pages can be found in the [[<tvar name=h-specialpages>Special:MyLanguage/Help:Special pages</tvar>|special pages]] section of this manual.</translate>''


<translate>
== Page tabs == 
</translate>
[[Image:Vector page tabs.png|thumb|500px|<translate> Default page tabs at the top of the page</translate>]]

<translate> The page tabs are displayed at the top of the page to the right of the site logo (if using the MonoBook or Vector skin).</translate>
<translate> These tabs allow you to perform actions or view pages that are related to the current page.</translate>
<translate> The available default actions include: viewing, editing, and discussing the current page.</translate>
<translate> The specific tabs displayed on your pages depend on whether or not you are logged into the wiki and whether you have sysop (administrator) privileges on the wiki.</translate>
<translate> On special pages, only the namespace tab is displayed.</translate>

; <translate> Default for all users</translate>
:* <translate> "[[<tvar name=namespace>Special:MyLanguage/Help:Namespaces</tvar>|namespace]]" (page, help, special page, template, user page etc.)</translate>
:* "}}"
:* "}}" <translate> (may read "<tvar name=viewsource>}}</tvar>" if anonymous editing is disabled, the page is in the MediaWiki: namespace, or the page is protected)</translate>
:* "}}"
; <translate> Extra tabs for logged-in users</translate>
:* "}}"
:* "}}"
; <translate> Extra tabs for sysops</translate>
:* "}}"
:* "}}"

<translate>

Administrators can [[<tvar name=1>Special:MyLanguage/FAQ#How do I add/remove tabs throughout my wiki?</tvar>|add or remove tabs]] by using JavaScript or installing extensions, so the tabs you see may be different depending on which wiki you are using.

== User links == 
</translate>
[[Image:Vector_user_links.png|thumb|900px|center|<translate> Default user links at the top right of the page</translate>]]

<translate> The user links are displayed at the top far right of the page (if using the default Vector skin).</translate>
<translate> These tabs allow the logged-in user to view and edit their user page and wiki preferences.</translate>
<translate> Additionally, the user links allow the user to quickly access their contributions to the wiki and logout.</translate>

<translate>

For anonymous users the user links is replaced by a link to the wiki login page or, if enabled by the site administrator, a link to your IP address and your IP address's talk page.
</translate>

; "Username"
: <translate> This links to your user page which is where you can put information about yourself, store bits of information you want to remember or whatever else you fancy.</translate>
; "Talk"
: <translate> This links to your discussion page, where people can leave messages for you.</translate>
; "Preferences"
: <translate> Allows you to change your personal site preferences.</translate>
; "Watchlist"
: <translate> A list of all pages that you are watching. Pages can be added to this list by clicking "<tvar name=watch>}}</tvar>" at the top of the page.</translate>
; "Contributions"
: <translate> A list of all contributions you have made to the wiki.</translate>
; "Log out"
: <translate> Click this link to log out of the wiki.</translate>

[[Category:Help|Help]]

----
''Sample content adapted from [[mediawikiwiki:Help:Navigation]] on mediawiki.org, licensed under [https://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA 4.0].''

Help/Editing

Admin — Sat, 25 Jul 2026 17:02:03 GMT

Seed from mediawiki.org for Seekmodo connector demo

New page

<languages />

<translate>

Editing can be done with the wikitext source editor, or with the visual editor.


The main parts of Wikidata have a different system of editing, without there being wikitext source text.

== Editing == 
</translate>
*
*
*
*
*
*
*
*

<translate>
=== Advanced editing === 
</translate>
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*

[[Category:Help|Editing]]
[[Category:Edit]]
[[Category:Project help]]

----
''Sample content adapted from [[mediawikiwiki:Help:Editing]] on mediawiki.org, licensed under [https://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA 4.0].''

Help/Contents

Admin — Sat, 25 Jul 2026 17:02:02 GMT

Seed from mediawiki.org for Seekmodo connector demo

New page

<languages />

''[[Special:MyLanguage/Communication|<translate> Ask a question about the MediaWiki software.</translate>]]''

<translate>
== Welcome to MediaWiki.org help pages == 
</translate>
{{ambox
|type=notice
|image=[[File:Codex icon help notice-blue.svg|45px|alt=|link=]]
|text= '''<translate> These help pages are about the MediaWiki software itself.</translate>''' <translate> Many MediaWiki-powered wikis link here for technical documentation.</translate> <translate> If you came here from another wiki and are looking for help with that wiki's content or community, this page may not be what you need.</translate> <translate> See <tvar name=1></tvar>.</translate>
}}

{{ContentGrid
|content =


**
*
*
*
*
*
*
}}

*
**
*
*
*
*
*
*
*
*
*
*
*
*
**
**
**
**
*
*
*
}}

- <translate> Provides an overview of many of the below features</translate>
*
*
*
*
*
*
**
*
*
*
*
*
*
*
**
**
*
*
*
*
*
*
*
**
*
*
*
*
*
*
}}

}}

*
}}

<translate>

The following features require extra permissions that are not normally granted to all wiki users.
</translate>

*
*
*
*
*
*
*
}}

}}

[[Category:Help| ]]
__NOTOC__

----
''Sample content adapted from [[mediawikiwiki:Help:Contents]] on mediawiki.org, licensed under [https://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA 4.0].''

Main Page

MediaWiki default — Sat, 25 Jul 2026 16:59:54 GMT

New page

<strong>MediaWiki has been installed.</strong>

Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.

== Getting started ==
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/ MediaWiki release mailing list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]