MediaWiki 1.36

 

• The logo of MediaWiki has changed. This means that the "Powered By MediaWiki" button shown in the skin footer will be different.
• All HTML5 named entities are now accepted in wikitext.
• (T106263) The file description page's alternate sizes now include 2048px.

This is to reduce the size of the watchlist data in the database. To add API bot edits to the watchlist, explicitly set the 'watch' option.

• MediaWiki 1.36 now requires the PHP internationalisation extension (commonly referred to as Intl, ext-intl, or php-intl).

If you use this feature, please move the MediaWiki:Autoblock_whitelist page.

This is not safe; extension functions are run relatively late, some services are already initialised by that point and so they use the old configuration. Changes in 1.36 make this kind of breakage even more common. You can use the MediaWikiServices hook instead. (In the future there might be a dedicated hook for configuration changes.)

This is no longer encouraged, and the option has been removed.

• (T256001) $wgManualRevertSearchRadius – This setting controls a new feature that marks edits as reverts if they restore the page to an exact previous state. This configuration variable sets the maximum number of revisions of a page that will be checked against every new edit. Set this to 0 to disable the feature entirely.
• (T244058) $wgOldRevisionParserCacheExpireTime — This setting was added to control caching of ParserOutput for old (non-current) revisions.
• (T265263) $wgRememberMe - This setting configures the "remember me" checkbox on account log-in systems via RememberMeAuthenticationRequest.
• (T157145) $wgSkinMetaTags – This setting lets sysadmins configure skins that support meta tags. These tags make sharing of MediaWiki pages on a variety of social platforms more contentful and thus useful.
• (T280944) $wgIncludejQueryMigrate – This setting lets sysadmins disable the jQuery Migrate plugin. It has been enabled by default since MediaWiki 1.27 . In future releases it will be disabled by default.

• $wgLogos – Setelan ini memilih logo yang ditampilkan di situs. The default value for the site logo, which is shown in an install if you have not set one, will now be the new logo of MediaWiki.
• (T274695) $wgAjaxEditStash — This setting, to disable the edit stashing feature when users start writing an edit summary, has been deprecated. In future releases, this feature will always be enabled.
• $wgUploadStashScalerBaseUrl – This setting, to enable remote on-demand media scaling, was deprecated. Use the `thumbProxyUrl` setting in $wgLocalFileRepo instead.
• $wgSlaveLagWarning , $wgSlaveLagCritical – These settings have been renamed, to $wgDatabaseReplicaLagWarning & $wgDatabaseReplicaLagCritical respectively. The former configuration variable names are deprecated, but will be used as the fallback if they are still set, and remain temporarily available for extensions which try to read them.

If you use Dynomite, then set the new "coalesceKeys" option to "hash_tag". The "cluster" and "mcrouterAware" options were also removed without deprecation. Use "broadcastRoutingPrefix" instead.

• $wgAllowImageMoving — This setting, deprecated in 1.35, has been removed. Use group permission settings instead. For example, to prevent sysops from moving files, set $wgGroupPermissions ['sysop']['movefile'] = false;`
• $wgExtNewTables , $wgExtNewFields , $wgExtNewIndexes , $wgExtPGNewFields , $wgExtPGAlteredFields , $wgExtModifiedFields — These settings were removed. They became obsolete after 1.17 overhauled the database updater, but were kept for backward compatibility. The LoadExtensionSchemaUpdates hook should be used instead.

The last use of this setting was for pre-processor configuration, which was deprecated in 1.34 and removed in 1.35.

• $wgEnableRestAPI — This setting, ignored since 1.35, has been removed.
• $wgPagePropsHaveSortkey – This temporary setting has been removed, along with the schema change upgrade path it controlled. If your site is still using it, meaning you have not yet applied the `pp_sortkey` schema change from 1.24, you must now apply it before upgrading.

Please use PasswordCannotMatchDefaults and PasswordNotInCommonList respectively instead.