Manual:Upgrading to 1.8
|Other languages:||English • Deutsch • français • 日本語 • русский|
|This page is obsolete. It is kept for historical interest only. It may document extensions or features that are obsolete and/or no longer supported. Do not rely on the information here being up-to-date.|
|This page contains information on upgrading to a non-current version of MediaWiki.|
You are advised to upgrade to version 1.31.1 if possible. Instructions for this can be found at Manual:Upgrading.
Those MediaWiki developers have been busy. MediaWiki 1.8 is out, and brings the usual wealth of fun new features. This guide should help users of the 1.7 release branch migrate to MediaWiki 1.8 in a smooth fashion. It will also work for users of the obsolete 1.6 branch.
- 1 Overview
- 2 Check requirements
- 3 Read the release notes
- 4 Back up existing files and the database
- 5 Unpack the new files
- 6 Run the update script
- 7 Upgrade extensions
- 8 Test the update
As with all MediaWiki upgrades, the basic premise is the same:
- Check the requirements
- Read the release notes
- Back up existing files and the database
- Unpack the new files
- Run the update script to check the database
- Upgrade extensions
- Test the update
MediaWiki 1.8 requires:
- PHP 5.0 or later (5.1 recommended)
- PHP 4 has not been supported since 1.7
- Note: PHP 5.0 has bugs on 64-bit systems which cause fundamental problems with MediaWiki. If you are running on an x86_64 (AMD64, EMT64) or other affected 64-bit platform, you must run PHP 5.1 or higher.
- MySQL 4.0 or later
- MySQL 3.x has not been supported since 1.6
Read the release notes
Within the distribution tarball, or within the files checked out/exported from SVN, there are a number of files with capitalised filenames, one of which contains the RELEASE-NOTES. Now's the time to open it up and find out what's been changed in 1.8.
Back up existing files and the database
While the upgrade scripts are well-maintained and robust, things could still go pear-shaped. Before proceeding to update the database schema, make a full backup of the wiki, including both the database and the files.
Make a full backup of the wiki database before attempting to run update scripts on it. This serves as a basic precaution should the schema updates fail, leaving records in a broken or corrupt state. There are a number of utilities to do this, such as MySQL dump, which is supplied with the MySQL software.
Make a copy of your LocalSettings.php file, which contains both the basic configuration details, and also any customisations you may have made to change the behaviour of MediaWiki.
If uploads are enabled in the wiki, then you will also need to back up the upload directory. By default, this is the images directory, although the path to this may have been changed in LocalSettings.php.
Extensions and custom skins
Make copies of the extensions directory, and any files or directories containing skin customisations.
Unpack the new files
If using a tarball package downloaded from SourceForge, decompress it; if using Subversion, export the files into a clean location. Replace all existing files with the new versions from 1.8, preserving the directory structure. The core code is now up to date.
Run the update script
Note: Make sure there's an AdminSettings.php file in the wiki root, and it's got up to date information in it. The user needs full permissions on the database.
The preferred method of performing the update is using the command-line maintenance script, however, it is also possible to re-run the web-based installer.
From the command line, or an SSH shell or similar, change to the maintenance directory and execute the update script:
$ php update.php
MediaWiki will inspect the existing schema and update it to work with the new code, adding tables and columns as needed. If upgrading from 1.5.x, once this is complete, you are advised to run the refreshLinks.php script to update the link tables.
Alternative 1: phpShell
If shell access is not available, look at options such as phpShell, which emulates a command prompt using PHP functions. This might not work on some locked-down hosting setups.
When using such a solution, it is often desirable to skip the countdown period at the start of the script. Pass the --quick option to the update script to do so:
$ php update.php --quick
Alternative 2: Re-run the installer
An alternative to running the update script from the shell is to re-run the web installer. To do this:
- Rename LocalSettings.php to LocalSettings.old.php
- Make the config directory writable by the web server
- Browse to the wiki and start the installer
Fill in the form fields with the same values as was done during the previous version's installation. When the installation process starts, the script will detect existing MediaWiki tables, and upgrade their schema. When this is complete, a new LocalSettings.php will be generated.
- Delete the new configuration file
- Rename LocalSettings.old.php back to LocalSettings.php
- Restore permissions on the config directory
Certain extensions have been updated in order to work with MediaWiki 1.8. Be sure to upgrade to the latest versions of such extensions. You might need to perform manual updates to custom extensions.
Test the update
Once the upgrade has completed, browse to the wiki and check basics such as viewing and editing pages to ensure things still work as expected.
Visit Special:Version and check that the version shown is correct.