This setting was intended to control the legacy AJAX framework, but some
extensions mistakenly used it to control any AJAX functionality at all.
But keeping this around when we're deprecating things like $wgEnableAPI
makes no sense.
[Retro-back-ported after
bf61efd87 had landed in 1.32.]
Change-Id: I7b767478f9fb44236e6514b0e83228d9fb8e856f
* $wgValidateAllHtml was removed and will be ignored.
* $wgScriptExtension was removed (deprecated and ignored since 1.25).
See 1.25 release notes for more information.
+* $wgUseAjax is now marked as deprecated, just like the deprecated AJAX
+ framework that it enables. Some extensions mistakenly used this to check
+ whether any AJAX functionality at all should be enabled, further making this
+ problematic to retain.
=== New features in 1.31 ===
* (T76554) User sub-pages named ….json are now protected in the same way that ….js
=== Configuration changes in 1.32 ===
* (T115414) The $wgEnableAPI and $wgEnableWriteAPI settings, deprecated in 1.31, have been removed.
-* The $wgUseAjax setting is now formally deprecated, and MediaWiki will act as if it is always set.
+* The $wgUseAjax setting, deprecated in 1.31, is now ignored.
* The $wgSiteSupportPage setting, unused since 1.5, was removed.
* …
/**
* Enable AJAX framework
*
- * @deprecated since MediaWiki 1.32 and ignored
+ * @deprecated (officially) since MediaWiki 1.31 and ignored since 1.32
*/
$wgUseAjax = true;