Manual:Upgrading to 1.10
|This page contains information on upgrading to a non-current version of MediaWiki.|
You are advised to upgrade to version 1.36.1 if possible. Instructions for this can be found at Manual:Upgrading.
Spring is here, and so is MediaWiki 1.10. As usual, there are more features and bug fixes, and as usual, we provide this convenient quick-start guide to upgrading.
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.10 requires:
- PHP 5.0.x or later
- We recommend using PHP 5.1.x.
- Note that PHP 5.0.x under certain 64-bit platforms contains bugs which cause fundamental problems with MediaWiki. If running on an x86_64 (AMD64, EM64T) or other affected 64-bit platform, PHP 5.1.x is required.
- MySQL 4.0.x or later
- Version 3.x has not been supported since 1.6.0
- PostgreSQL 8.1 or later
- You will also require the
- You will also require the
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.10.
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:
- the wiki's content, from the database. It may be a good idea to create an XML dump in addition to the SQL database dump.
- images and other media files (the contents of the
- configuration files, i.e.
- MediaWiki's program files, including all skins and extensions, especially if you modified them.
See Manual:Backing up a wiki for instructions.
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.10, 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:
- Make the
configdirectory writable by the web server
- Make sure the database user has full rights to the database
- 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
- Restore permissions on the
Certain extensions have been updated in order to work with MediaWiki 1.10. 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.