User:Iritscen/WikiFuture: Difference between revisions

+1.31; the death of the 2006 toolbar has been delayed but is still imminent
(added 1.30.0 and warning note about eventual 1.31)
(+1.31; the death of the 2006 toolbar has been delayed but is still imminent)
Line 1: Line 1:
Below are any notable changes that we should look forward to, or watch out for, if upgrading MediaWiki (besides various security fixes). Source: https://www.mediawiki.org/wiki/Release_notes
Below are any notable changes that we should look forward to, or watch out for, if upgrading MediaWiki (besides various security fixes). Source: https://www.mediawiki.org/wiki/Release_notes


Oldest version of MediaWiki still supported as of June 2017: 1.27. Source: https://www.mediawiki.org/wiki/Version_lifecycle
Oldest LTS version of MediaWiki: 1.27 (supported through June 2019). Source: https://www.mediawiki.org/wiki/Version_lifecycle


Current version on OniGalore: '''{{CURRENTVERSION}}'''
Current version on OniGalore: '''{{CURRENTVERSION}}'''
Line 25: Line 25:


==1.31==
==1.31==
*'''Warning: MW developers are [[mw:Editor|currently planning]] to remove support for the 2006 editing toolbar in 1.31'''. This is the one we're currently using! This change will break [[XEB]], and the editing UX doesn't get any better with the 2010 toolbar (it gets even worse with the 2017 wikitext beta...), so we need to think carefully before upgrading. The classic 2006 toolbar may become available as a third-party gadget, but will it be customizable or would we have to rewrite our own toolbar from scratch?
:''I have checked the release notes through 1.31.0.''
*Note: If you're using MySQL, SQLite, or MSSQL, are not using update.php to apply schema changes, and cannot have downtime to run migrateArchiveText.php and apply patch-drop-ar_text.sql manually, you'll have to apply a default value to the ar_text and ar_flags columns of the archive table or make those columns nullable before upgrading to MediaWiki 1.31. maintenance/archives/patch-nullable-ar_text.sql shows how to do this for MySQL.
*Automatic trimming of unnecessary whitespace from wikitext.
*Methods that alter ParserOutput directly are deprecated. Callers should use the new stateless $options parameter to ParserOutput::getText() instead.
*The global function wfOutputHandler() was removed; use its replacement MediaWiki\OutputHandler::handle() instead.
*The following variables and methods in EditPage, deprecated in MediaWiki 1.30, were removed: $isCssJsSubpage, $isCssSubpage, $isJsSubpage, $isWrongCaseCssJsPage.
*The mw.page JavaScript singleton, deprecated in 1.30, was removed.
*Added support for .json user subpages in addition to .css and .js, intended for saving configuration options.
*The 'comma' value for $wgArticleCountMethod is no longer supported for performance reasons, and installations with this setting will now work as if it was configured with 'any'. Note that we are currently using the 'comma' option, but it appears that 'any' will return the same result, as it counts all pages that are not redirects.
*Added default edit rate limit of 90 edits/minute for all users.
*Make $wgEmailConfirmToEdit only affect edit actions.
 
==Upcoming==
*'''Warning: MW developers are [[mw:Editor|currently planning]] to remove support for the 2006 editing toolbar soon'''. This is the one we're currently using! This change will break [[XEB]], and the editing UX doesn't get any better with the 2010 toolbar (it gets even worse with the 2017 wikitext beta...), so we need to think carefully before upgrading. The classic 2006 toolbar may become available as a third-party gadget, but will it be customizable or would we have to rewrite our own toolbar from scratch?


[[Category:Userspace]]
[[Category:Userspace]]