X-Git-Url: http://git.heureux-cyclage.org/?a=blobdiff_plain;f=UPGRADE;h=f55364fe33c57374a200796d74dd33e1ea84dda8;hb=9794985c9d2ef37788d41eac00c30c0ccf3b04d1;hp=ece64ecadf4bf836bdeca07438f1bdbf3b82d33e;hpb=6c0422c8953fc75601bb66f524f06d31f8130bd8;p=lhc%2Fweb%2Fwiklou.git diff --git a/UPGRADE b/UPGRADE index ece64ecadf..f55364fe33 100644 --- a/UPGRADE +++ b/UPGRADE @@ -1,31 +1,121 @@ -== The basic theory == +This file provides an overview of the MediaWiki upgrade process. For help with +specific problems, check -Generally, within a stable release series (e.g. 1.4.0, 1.4.1, etc) there -are no required database changes, and upgrading should require no more -than copying the new source files over the old ones. +* the documentation at http://www.mediawiki.org +* the mediawiki-l mailing list archive at + http://lists.wikimedia.org/pipermail/mediawiki-l/ +* the bug tracker at https://bugzilla.wikimedia.org -If there are larger changes, such as upgrading from one release series -to another (e.g. from 1.3.12 to 1.4.3), then you may need to update the -database schema and configuration. +for information and workarounds to common issues. -Basically, to upgrade a wiki you: -* Back up your data! (See Backups! below) -* Extract the new archive. If you can do this in a clean directory that's - great, but it should work to extract over the old files too. This may - be easier if you have images etc in place and don't want to move them - around, but remember to back up first! -* Run the installer to upgrade the database schema (if necessary, - see sections below for details). +== Overview == +Comprehensive documentation on upgrading to the latest version of the software +is available at http://www.mediawiki.org/wiki/Manual:Upgrading. -== IMPORTANT: Upgrading to 1.5 == +=== Consult the release notes === + +Before doing anything, stop and consult the release notes supplied with the new +version of the software. These detail bug fixes, new features and functionality, +and any particular points that may need to be noted during the upgrade +procedure. + +=== Backup first === + +It is imperative that, prior to attempting an upgrade of the database schema, +you take a complete backup of your wiki database and files and verify it. While +the upgrade scripts are somewhat robust, there is no guarantee that things will +not fail, leaving the database in an inconsistent state. + +http://www.mediawiki.org/wiki/Manual:Backing_up_a_wiki provides an overview of +the upgrade process. You should also refer to the documentation for your +database management system for information on backing up a database, and to +your operating system documentation for information on making copies of files. + +=== Perform the file upgrade === + +Download the files for the new version of the software. These are available +as a compressed "tar" archive from the Wikimedia Download Service +(http://download.wikimedia.org/mediawiki). + +You can also obtain the new files directly from our Subversion source code +repository, via a checkout or export operation. + +Replace the existing MediaWiki files with the new. You should preserve the +LocalSettings.php file and the "extensions" and "images" directories. + +Depending upon your configuration, you may also need to preserve additional +directories, including a custom upload directory ($wgUploadDirectory), +deleted file archives, and any custom skins. + +=== Perform the database upgrade === + +You will need to have $wgDBadminuser and $wgDBadminpass set in your +LocalSettings.php, see there for more info. + +From the command line, browse to the "maintenance" directory and run the +update.php script to check and update the schema. This will insert missing +tables, update existing tables, and move data around as needed. In most cases, +this is successful and nothing further needs to be done. + +=== Check configuration settings === + +The names of configuration variables, and their default values and purposes, +can change between release branches, e.g. $wgDisableUploads in 1.4 is replaced +with $wgEnableUploads in later versions. When upgrading, consult the release +notes to check for configuration changes which would alter the expected +behaviour of MediaWiki. + +=== Check installed extensions === +In MediaWiki 1.14 some extensions are migrated into the core. Please see the +RELEASE-NOTES section "Migrated extensions" and disable these extensions in your +localSettings.php + +=== Test === + +It makes sense to test your wiki immediately following any kind of maintenance +procedure, and especially after upgrading; check that page views and edits work +normally and that special pages continue to function, etc. and correct errors +and quirks which reveal themselves. + +You should also test any extensions, and upgrade these if necessary. + +== 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 == Major changes have been made to the schema from 1.4.x. The updater has not been fully tested for all conditions, and might well break. -DO NOT ATTEMPT TO UPGRADE A LIVE, PUBLIC SITE TO 1.5 AT THIS TIME. -NEVER EVER ATTEMPT TO PERFORM AN UPGRADE WITHOUT BACKING UP FIRST! - On a large site, the schema update might take a long time. It might explode, or leave your database half-done or otherwise badly hurting. @@ -44,10 +134,9 @@ but note that the old directory hashes will no longer be valid, 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: === $wgDisableUploads has been replaced with $wgEnableUploads. @@ -82,10 +171,10 @@ should be replaced with: === Web installer === You can use the web-based installer wizard if you first remove the -LocalSettings.php (and AdminSettings.php, if any) files; be sure to -give the installer the same information as you did on the original -install (language/encoding, database name, password, etc). This will -also generate a fresh LocalSettings.php, which you may need to customize. +LocalSettings.php file; be sure to give the installer the same +information as you did on the original install (language/encoding, +database name, password, etc). This will also generate a fresh +LocalSettings.php, which you may need to customize. You may change some settings during the install, but be very careful! Changing the encoding in particular will generally leave you with a @@ -95,8 +184,8 @@ lot of corrupt pages, particularly if your wiki is not in English. Additionally, as of 1.4.0 you can run an in-place upgrade script from the command line, keeping your existing LocalSettings.php. This requires -that you create an AdminSettings.php giving an appropriate database user -and password with privileges to modify the database structure. +that you set $wgDBadminuser and $wgDBadminpassword with an appropriate +database user and password with privileges to modify the database structure. Once the new files are in place, go into the maintenance subdirectory and run the script: @@ -117,19 +206,28 @@ LocalSettings.php are not accidentally made public, as this contains 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 ===