MediaWiki 1.32/en

MediaWiki 1.32 is the latest release of MediaWiki. Consult the file for the full list of changes. It was deployed on Wikimedia Foundation wikis through incremental "wmf"-branches starting 24 April 2018. The 1.31.0 stable release was released on 10 January 2019. Download the or checkout the   branch in Git to follow this release.

Languages updated
MediaWiki supports over 350 languages. Many localisations are updated regularly. Below only new and removed languages are listed, as well as changes to languages because of Phabricator reports.


 * Added language support for (abs).
 * Added language support for (shy-latn).
 * Added language support for (btm).
 * Added language support for (zgh).
 * Added language support for (mni).
 * Added language support for (hyw).
 * Added language support for (mnw).

Action API changes

 * Added templated parameters.
 * A module can define a templated parameter like "{fruit}-quantity", where the actual parameters recognized correspond to the values of a multi-valued parameter. Then clients can make requests like "fruits=apples|bananas&apples-quantity=1&bananas-quantity=5".
 * action=paraminfo will return templated parameter definitions separately from normal parameters. All parameter definitions now include an "index" key to allow clients to maintain parameter ordering when merging normal and templated parameters.
 * It is now an error to submit too many values for a multi-valued parameter. This has generated a warning since MediaWiki 1.14.
 * Assertion failures from the 'assert' and 'assertuser' parameters will no longer use the action module's custom response format, for the few modules that use custom formatters that handle errors.
 * User list preferences such as `email-blacklist` and similar extension preferences are no longer represented as arrays when returned by action=query&meta=userinfo&uiprop=options.
 * 'missingparam' errors will now use the prefixed parameter name in the code and error text, e.g. "noxxfoo" and "The 'xxfoo' parameter must be set" rather than "nofoo" and "The 'foo' parameter must be set".
 * action=query&prop=revisions now takes a 'rvslots' parameter to indicate the multi-content revision slots for which content should be returned. It also has a new rvprop, 'roles', to indicate which roles have slots. A deprecation warning will be issued if rvprop=content or rvprop=contentmodel are used without rvslots.
 * The rvcontentformat parameter to action=query&prop=revisions has been deprecated. Clients should be prepared to deal with the default format for relevant models.
 * Use of the deprecated parameters rvexpandtemplates, rvgeneratexml, rvparse, rvdiffto, rvdifftotext, rvdifftotextpst, rvcontentformat, or the deprecated rvprop=parsetree is forbidden with the new 'rvslots' parameter.
 * action=query&prop=deletedrevisions, action=query&list=allrevisions, and action=query&list=alldeletedrevisions are changed similarly to &prop=revisions (see the three previous items).
 * (T174032) action=compare now supports multi-content revisions.
 * It has a 'slots' parameter to select diffing of individual slots. The default behavior is to return one combined diff.
 * The 'fromtext', 'fromsection', 'fromcontentmodel', 'fromcontentformat', 'totext', 'tosection', 'tocontentmodel', and 'tocontentformat' parameters are deprecated. Specify the new 'fromslots' and 'toslots' to identify which slots have text supplied and the corresponding templated parameters for each slot.
 * The behavior of 'fromsection' and 'tosection' of extracting one section's content is not being preserved. 'fromsection-{slot}' and 'tosection-{slot}' instead expand the given text as if for a section edit. This effectively declines in favor of.
 * The 'disabletidy' parameter to action=parse has been deprecated; untidy output will not be supported by future wikitext parsers.

Other changes

 * The following tables have had their UNIQUE indexes turned into proper PRIMARY KEYs for increased maintainability: interwiki, page_props, protected_titles and site_identifiers.
 * OOUI HTMLForm will now display help text inline after the input field, rather than in a popup. Previous behavior can be restored by using `'help-inline' => false`.
 * The archive table's ar_rev_id field is now unique.
 * Special:BotPasswords now requires reauthentication.
 * Multi-Content Revision (MCR) capabilities were introduced into the storage layer and have basic support for display. No user interface exists yet for creating or managing content in slots besides the main slot. See Multi-Content Revisions for more information.