| Index: trunk/phase3/UPGRADE |
| — | — | @@ -16,7 +16,7 @@ |
| 17 | 17 | === Consult the release notes === |
| 18 | 18 | |
| 19 | 19 | Before doing anything, stop and consult the release notes supplied with the new |
| 20 | | -version of the software. This detail bug fixes, new features and functionality, |
| | 20 | +version of the software. These detail bug fixes, new features and functionality, |
| 21 | 21 | and any particular points that may need to be noted during the upgrade |
| 22 | 22 | procedure. |
| 23 | 23 | |
| — | — | @@ -27,32 +27,34 @@ |
| 28 | 28 | the upgrade scripts are somewhat robust, there is no guarantee that things will |
| 29 | 29 | not fail, leaving the database in an inconsistent state. |
| 30 | 30 | |
| 31 | | -Refer to the MySQL or Postgres documentation for information on backing up a |
| 32 | | -database. For information on making copies of files, consult the documentation |
| 33 | | -for your operating system. |
| | 31 | +http://www.mediawiki.org/wiki/Manual:Backing_up_a_wiki provides an overview of |
| | 32 | +the upgrade process. You should also refer to the documentation for your |
| | 33 | +database management system for information on backing up a database, and to |
| | 34 | +your operating system documentation for information on making copies of files. |
| 34 | 35 | |
| 35 | 36 | === Perform the file upgrade === |
| 36 | 37 | |
| 37 | | -Having downloaded the desired new version of the software, either as a package |
| 38 | | -from SourceForge, or via an export from Subversion, decompress the files as |
| 39 | | -needed, and replace the existing MediaWiki files with the new. |
| | 38 | +Download the files for the new version of the software. These are available |
| | 39 | +as a compressed "tar" archive from the Wikimedia Download Service |
| | 40 | +(http://download.wikimedia.org/mediawiki). |
| 40 | 41 | |
| 41 | | -You should preserve: |
| | 42 | +You can also obtain the new files directly from our Subversion source code |
| | 43 | +repository, via a checkout or export operation. |
| 42 | 44 | |
| 43 | | -* The LocalSettings.php file |
| 44 | | -* The AdminSettings.php file, where it exists |
| 45 | | -* The extensions directory |
| 46 | | -* The images directory |
| | 45 | +Replace the existing MediaWiki files with the new. You should preserve the |
| | 46 | +LocalSettings.php file, AdminSettings.php file (if present), and the |
| | 47 | +"extensions" and "images" directories. |
| 47 | 48 | |
| 48 | | -If using an alternative uploads directory, preserve this; and if using custom |
| 49 | | -skins, preserve these too. The core code is now updated. |
| | 49 | +Depending upon your configuration, you may also need to preserve additional |
| | 50 | +directories, including a custom upload directory ($wgUploadDirectory), |
| | 51 | +deleted file archives, and any custom skins. |
| 50 | 52 | |
| 51 | 53 | === Perform the database upgrade === |
| 52 | 54 | |
| 53 | 55 | You will need an AdminSettings.php file set up in the correct format; see |
| 54 | 56 | AdminSettings.sample in the wiki root for more information and examples. |
| 55 | 57 | |
| 56 | | -From the command line, browse to the maintenance directory and run the |
| | 58 | +From the command line, browse to the "maintenance" directory and run the |
| 57 | 59 | update.php script to check and update the schema. This will insert missing |
| 58 | 60 | tables, update existing tables, and move data around as needed. In most cases, |
| 59 | 61 | this is successful and nothing further needs to be done. |
| — | — | @@ -72,6 +74,8 @@ |
| 73 | 75 | normally and that special pages continue to function, etc. and correct errors |
| 74 | 76 | and quirks which reveal themselves. |
| 75 | 77 | |
| | 78 | +You should also test any extensions, and upgrade these if necessary. |
| | 79 | + |
| 76 | 80 | == Upgrading from 1.8 wikis == |
| 77 | 81 | |
| 78 | 82 | MediaWiki 1.9 and later no longer keep default localized message text |