This file provides an overview of the MediaWiki upgrade process. For help with
specific problems, check
-* the documentation at http://meta.wikimedia.org
* the documentation at http://www.mediawiki.org
* the mediawiki-l mailing list archive at
- http://mail.wikipedia.org/pipermail/mediawiki-l
+ http://lists.wikimedia.org/pipermail/mediawiki-l/
* the bug tracker at http://bugzilla.wikimedia.org
for information and workarounds to common issues.
== Overview ==
-* Documentation on upgrading from 1.5 to 1.6 can also be found at
-http://www.mediawiki.org/wiki/Help:Upgrading_to_1.6
+Comprehensive documentation on upgrading to the latest version of the software
+is available at http://www.mediawiki.org/wiki/Manual:Upgrading_MediaWiki.
=== Consult the release notes ===
the upgrade scripts are somewhat robust, there is no guarantee that things will
not fail, leaving the database in an inconsistent state.
-Refer to the MySQL documentation for information on backing up a database. For
-information on making copies of files, consult the documentation for your
-operating system.
+Refer to the MySQL or Postgres documentation for information on backing up a
+database. For information on making copies of files, consult the documentation
+for your operating system.
=== Perform the file upgrade ===
normally and that special pages continue to function, etc. and correct errors
and quirks which reveal themselves.
+== Upgrading from 1.8 wikis ==
+
+MediaWiki 1.9 and later no longer keep default localized message text
+in the database; 'MediaWiki:'-namespace pages that do not exist in the
+database are simply transparently filled-in on demand.
+
+The upgrade process will delete any 'MediaWiki:' pages which are left
+in the default state (last edited by 'MediaWiki default'). This may
+take a few moments, similar to the old initial setup.
+
+Note that the large number of deletions may cause older edits to expire
+from the list on Special:Recentchanges, although the deletions themselves
+will be hidden by default. (Click "show bot edits" to list them.)
+
+
+See RELEASE-NOTES for more details about new and changed options.
+
+
+== Upgrading from 1.7 wikis ==
+
+$wgDefaultUserOptions now contains all the defaults, not only overrides.
+If you're setting this as a complete array(), you may need to change it
+to set only specific items as recommended in DefaultSettings.php.
+
== Upgrading from 1.6 wikis ==
$wgLocalTZoffset was in hours, it is now using minutes.
+Link autonumbering got fixed (#5918) for protocols other than http.
+ - 'irc://irc.server.tld/' render as a link with a chat icon
+ - '[irc://irc.server.tld]' render as an autonumbered link: [1]
== Upgrading from pre-1.5 wikis ==
so you will also have to move them to new destinations.
Message changes:
-* A number of additional UI messages have been chagned from HTML to
+* A number of additional UI messages have been changed from HTML to
wikitext, and will need to be manually fixed if customized.
=== Configuration changes from 1.4.x: ===
a database password.)
To back up the database, use the tools provided by your service provider
-(if applicable) or the standard mysqldump program.
+(if applicable) or the standard mysqldump or pg_dump programs.
For general help on mysqldump:
http://dev.mysql.com/doc/mysql/en/mysqldump.html
WARNING: If using MySQL 4.1.x, mysqldump's charset conversion may in
some cases damage data in your wiki. If necessary, set the charset
-option to 'latin1' to avoid the conversion. Fore more info see:
-http://mail.wikipedia.org/pipermail/wikitech-l/2004-November/026359.html
+option to 'latin1' to avoid the conversion.
+
+For general help on pg_dump:
+http://www.postgresql.org/docs/current/static/app-pgdump.html
== Caveats ==
+=== Postgres ===
+
+Postgres support is new, and much of the upgrade instructions may
+not apply. The schema was changed significantly from 1.7 to 1.8,
+so you will need to at least use the update.php or web installer,
+as described above.
+
=== Upgrading from 1.4.2 or earlier ===