RELEASE-NOTES-1.21

   1
   2 Security reminder: MediaWiki does not require PHP's register_globals. If you
   3 have it on, turn it '''off''' if you can.
   4
   5 == MediaWiki 1.21 ==
   6
   7 THIS IS NOT A RELEASE YET
   8
   9 MediaWiki 1.21 is an alpha-quality branch and is not recommended for use in
  10 production.
  11
  12 === Configuration changes in 1.21 ===
  13 * (bug 29374) $wgVectorUseSimpleSearch is now enabled by default.
  14 * Deprecated $wgAllowRealName is removed. Use $wgHiddenPrefs[] = 'realname'
  15   instead.
  16
  17 === New features in 1.21 ===
  18 * (bug 38110) Schema changes (adding or dropping tables, indicies and
  19   fields) can be now be done separately from from other changes that
  20   update.php makes.  This is useful in environments that use database
  21   permissions to restrict schema changes but allow the DB user that
  22   MediaWiki normally runs as to perform other changes that update.php
  23   makes.  Schema changes can be run seperately.  See the file UPGRADE
  24   for more information.
  25 * (bug 34876) jquery.makeCollapsible has been improved in performance.
  26 * Added ContentHandler facility to allow extensions to support other content
  27   than wikitext. See docs/contenthandler.txt for details.
  28 * New feature was developed for showing high-DPI thumbnails for high-DPI mobile
  29   and desktop displays (configurable with $wgResponsiveImages).
  30 * Added new backend to represent and store information about sites and site
  31   specific configuration.
  32 * jQuery upgraded from 1.8.2 to 1.8.3.
  33 * jQuery UI upgraded from 1.8.23 to 1.8.24.
  34 * Added separate fa_sha1 field to filearchive table. This allows sha1
  35   searches with the api in miser mode for deleted files.
  36 * Add initial and programmatic sorting for tablesorter.
  37 * Add the event "sortEnd.tablesorter", triggered after sorting has completed.
  38 * The Job system was refactored to allow for different backing stores for
  39   queues as well as cross-wiki access to queues, among other things. The schema
  40   for the DB queue was changed to support better concurrency and reduce
  41   deadlock errors.
  42 * Added ApiQueryORM class to facilitate creation of query API modules based on
  43   tables that have a corresponding ORMTable class.
  44 * (bug 40876) Icon for PSD (Adobe Photoshop) file types.
  45 * (bug 40641) Implemented Special:Version/Credits with a list of contributors.
  46 * (bug 7851) Implemented one-click AJAX patrolling.
  47 * The <data>, <time>, <meta>, and <link> elements are allowed within WikiText
  48   for use with Microdata.
  49 * The HTML5 <mark> tag has been whitelisted.
  50 * Added ParserCloned hook for when the Parser object is cloned.
  51 * Added AlternateEditPreview hook to allow extensions to replace the page
  52   preview from the edit page.
  53 * Added EditPage::showStandardInputs:options hook to allow extensions to add
  54   new fields to the "editOptions" area of the edit form.
  55
  56 === Bug fixes in 1.21 ===
  57 * (bug 40353) SpecialDoubleRedirect should support interwiki redirects.
  58 * (bug 40352) fixDoubleRedirects.php should support interwiki redirects.
  59 * (bug 9237) SpecialBrokenRedirect should not list interwiki redirects.
  60 * (bug 34960) Drop unused fields rc_moved_to_ns and rc_moved_to_title from
  61   recentchanges table.
  62 * (bug 32951) Do not register internal externals with absolute protocol,
  63   when server has relative protocol.
  64 * (bug 39005) When purging proxies listed in $wgSquidServers using HTTP PURGE
  65   method requests, we now send a Host header by default, for Varnish
  66   compatibility. This also works with Squid in reverse-proxy mode. If you wish
  67   to support Squid configured in forward-proxy mode, set
  68   $wgSquidPurgeUseHostHeader to false.
  69 * (bug 37020) sql.php with readline eats semicolon.
  70 * (bug 11748) Properly handle optionally-closed HTML tags when Tidy is
  71   disabled, and don't wrap HTML-syntax definition lists in paragraphs.
  72 * (bug 41409) Diffs while editing an old revision should again diff against the
  73   current revision.
  74 * (bug 41494) Honor $wgLogExceptionBacktrace when logging non-API exceptions
  75   caught during API execution.
  76 * (bug 37963) Fixed loading process for user options.
  77 * (bug 26995) Update filename field on Upload page after having sanitized it.
  78 * (bug 41793) Contribution links to users with 0 edits on Special:ListUsers
  79   didn't show up red.
  80 * (bug 41899) A PHP notice no longer occurs when using the "rvcontinue" API
  81   parameter.
  82 * (bug 42036) Account creation emails now contain canonical (not
  83   protocol-relative) URLs.
  84 * (bug 41990) Fix regression: API edit with redirect=true and lacking
  85   starttimestamp and basetimestamp should not cause an edit conflict.
  86 * (bug 41706) EditPage: Preloaded page should be converted if possible and
  87   needed.
  88 * (bug 41886) Rowspans are no longer exploded by tablesorter until the table is
  89   actually sorted.
  90 * (bug 2865)  User interface HTML elements don't use lang attribute
  91   (completed the fix by adding the lang attribute to firstHeading).
  92 * (bug 42173) Removed namespace prefixes on Special:UncategorizedCategories.
  93 * (bug 36053) Log in "returnto" feature forgets query parameters if no
  94   title parameter was specified.
  95 * (bug 42410) API action=edit now returns correct timestamp for the new edit.
  96 * (bug 14901) Email notification mistakes log action for new page creation.
  97   Enotif no longer sends "page has been created" notifications for some log
  98   actions. The following events now have a correct message: page creation,
  99   deletion, move, restore (undeletion), change (edit).
 100 * (bug 457) In the sidebar of Vector, CologneBlue, Monobook, and Monobook-based
 101   skins, the heading levels have been changed from (variously per skin)
 102   <h4>, <h5> or <h6> to only <h3>s, with a <h2> hidden heading above them.
 103   If you are styling or scripting the headings in a custom way, this change
 104   will require updates to your site's CSS or JS.
 105
 106 === API changes in 1.21 ===
 107 * prop=revisions can now report the contentmodel and contentformat.
 108   See docs/contenthandler.txt.
 109 * action=edit and action=parse now support contentmodel and contentformat
 110   parameters to control the interpretation of page content.
 111   See docs/contenthandler.txt for details.
 112 * (bug 35693) ApiQueryImageInfo now suppresses errors when unserializing metadata.
 113 * (bug 40111) Disable minor edit for page/section creation by API.
 114 * (bug 41042) Revert change to action=parse&page=... behavior when the page
 115   does not exist.
 116
 117 === Languages updated in 1.21 ===
 118
 119 MediaWiki supports over 350 languages. Many localisations are updated
 120 regularly. Below only new and removed languages are listed, as well as
 121 changes to languages because of Bugzilla reports.
 122
 123 * South Azerbaijani (azb) added.
 124 * (bug 30040) Autonym for nds-nl is now 'Nedersaksies' (was 'Nedersaksisch').
 125 * (bug 34977) Now formatted numbers in Spanish use space as separator
 126   for thousands, as mandated by the Real Academia Española.
 127 * (bug 35031) Kurdish formatted numbers now use period and comma
 128   as separators for thousands and decimals respectively.
 129
 130 === Other changes in 1.21 ===
 131
 132 == Compatibility ==
 133
 134 MediaWiki 1.21 requires PHP 5.3.2 or later.
 135
 136 MySQL is the recommended DBMS. PostgreSQL or SQLite can also be used, but
 137 support for them is somewhat less mature. There is experimental support for IBM
 138 DB2 and Oracle.
 139
 140 The supported versions are:
 141
 142 * MySQL 5.0.2 or later
 143 * PostgreSQL 8.3 or later
 144 * SQLite 3.3.7 or later
 145 * Oracle 9.0.1 or later
 146
 147 == Upgrading ==
 148
 149 1.21 has several database changes since 1.20, and will not work without schema
 150 updates. Note that due to changes to some very large tables like the revision
 151 table, the schema update may take quite long (minutes on a medium sized site,
 152 many hours on a large site).
 153
 154 If upgrading from before 1.11, and you are using a wiki as a commons
 155 repository, make sure that it is updated as well. Otherwise, errors may arise
 156 due to database schema changes.
 157
 158 If upgrading from before 1.7, you may want to run refreshLinks.php to ensure
 159 new database fields are filled with data.
 160
 161 If you are upgrading from MediaWiki 1.4.x or earlier, some major database
 162 changes are made, and there is a slightly higher chance that things could
 163 break. Don't forget to always back up your database before upgrading!
 164
 165 See the file UPGRADE for more detailed upgrade instructions.
 166
 167 For notes on 1.19.x and older releases, see HISTORY.
 168
 169 == Online documentation ==
 170
 171 Documentation for both end-users and site administrators is available on
 172 MediaWiki.org, and is covered under the GNU Free Documentation License (except
 173 for pages that explicitly state that their contents are in the public domain):
 174
 175         https://www.mediawiki.org/wiki/Documentation
 176
 177 == Mailing list ==
 178
 179 A mailing list is available for MediaWiki user support and discussion:
 180
 181         https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
 182
 183 A low-traffic announcements-only list is also available:
 184
 185         https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce
 186
 187 It's highly recommended that you sign up for one of these lists if you're
 188 going to run a public MediaWiki, so you can be notified of security fixes.
 189
 190 == IRC help ==
 191
 192 There's usually someone online in #mediawiki on irc.freenode.net.