MediaWiki 1.22

MediaWiki 1.22 is currently being developed. Consult the file for the full list of changes. It is currently deployed on Wikimedia Foundation wikis through incremental "wmf"-branches starting April 2013. The 1.22.0 stable release is expected to come out late in 2013. Download the or checkout the   branch in Git to follow this release.

What's new?
MediaWiki 1.22 will include all changes released in the smaller "1.22wmfX" software deployments to Wikimedia sites.

Anti-spam and countervandalism improvements
Like MediaWiki 1.21, we're improving countervandalism features and bundling anti-spam extensions:
 * The patrolling system has been improved to make the "mark as patrolled" link available on any page or revision that is patrollable. This removed the need for the "rcid" URI parameters that one could only get from Special:RecentChanges or Special:NewPages.
 * SimpleAntiSpam has been bundled (it's a small but harmless shield against the simplest forms of spambots).

Editing improvements

 * Section edit links are now positioned adjacent to headings rather than along the opposite side of the page. Note that if your wiki has certain kinds of site CSS or JavaScript, those may need to be updated. More information at Change to section edit links.
 * When comparing revisions in the history or when previewing changes while editing, "(No difference)" is now shown in place of a diff when the revisions are identical.
 * A confirmation message ("Your edit was saved.") is now shown after a successful edit. Formerly a separate extension (PostEdit), this feature is now part of the core software.

Bundled extensions
Current plans, based on Suggestions for extensions to be integrated, are to include the following extensions in the tarball:
 * Disambiguator
 * SimpleAntiSpam

PHP JSON extension now required
Though the minimum PHP version is still 5.3.2, MediaWiki now requires either the native JSON extension or the pecl-json-c fork. Most servers already have this PHP extension installed and enabled. However, if you administer your own server, and the MediaWiki installer says you don't have this extension:
 * If you compiled PHP yourself with the  configure option, you may have to recompile with.
 * On Red Hat or CentOS, check for the line  in    or.
 * Ubuntu 13.10, Fedora 19, and other recent Linux distributions package pecl-json-c separately, under names such as  (Ubuntu universe) and   (Fedora). They no longer include the original JSON extension because of licensing concerns.

Several ancient skins removed


On 2013-04-01, several ancient skins were removed from core (not an April's fool joke): Chick, Classic, MySkin, Nostalgia and Simple. More information at Turning off outdated skins.

Nostalgia was the phase I/UseModWiki-like skin, and Classic was the main skin before the introduction of the default MonoBook in MediaWiki 1.3 (2004-05-22). Dating back to February 2002, both skins existed over a year before MediaWiki got its name.

Blank system messages must be deleted
(Add ability to disable MediaWiki messages) was fixed: now blanking a system message (editing it on wiki to remove all content) will no longer restore the default value for the message, but instead make it show as empty string in the interface. If you have blank messages on your wiki (check Special:AllMessages), you must delete them.

Protection rights usage has changed
A new setting was added for enabling cascading protection for protection levels other than "Allow only administrators". Shortly afterward, the way the "editprotected" and "autoconfirmed" rights work was changed (see ). In particular, the "autoconfirmed" right is now only used for rate limiting, not page protection. If your wiki has custom user groups with the "autoconfirmed" right, you may need to grant those groups the new "editsemiprotected" right when you upgrade.

Special:Disambiguations has been removed
Special:Disambiguations, a page that listed "Pages linking to disambiguation pages", has been removed. If your wiki used this feature, consider using Extension:Disambiguator, which provides similar functionality and will be bundled in the default tarball. Switching to the new extension is easy and generally only requires a small change to a single template.