Upgrading to 1.5 Stable
From Joomla! Documentation
Revision as of 19:29, 16 January 2008 by Chris Davenport
This article or section is in the process of an expansion or major restructuring. You are welcome to assist in its construction by editing it as well. If this article or section
It is risky to upgrade a live site without testing the upgrade process first. So before upgrading the live site you need to set up a test site which is as close as possible to the configuration of your live site, then test the upgrade on that. When you are happy with the process you can apply it to the live site (having taken a fresh backup of the live site first, of course).
|This page describes the process for upgrading from one of the Joomla! 1.5 Release Candidates to Joomla! 1.5 Stable. For details on how to migrate from Joomla! 1.0.x to Joomla! 1.5 Stable, please read Migrating from 1.0.x to 1.5 Stable instead.|
Step 1: Download the correct patch package
|What is a patch?|
Determine the current version of your Joomla! installation. For example, if you currently have version 1.5 RC4 installed you will need to download the 1.5 RC4 to 1.5 Stable patch package. The patch packages are available on <insert link to JoomlaCode here>. Each patch package is available in three different package formats. These are indicated by the file extension which is either .zip, .tar.gz or .tar.bz2. The contents of each of these alternative packages is identical so just choose the one most convenient for you.
|More about package file formats|
For example, if you are upgrading from 1.5 RC4 to 1.5 Stable and you would prefer the .tar.gz package format, then select the file named Joomla_1.5RC4_to_1.5Stable-Patch_Package.tar.gz <Check the filename>.
Step 2: Make a copy of your live site
Ideally this should be on the same platform (operating system, PHP and database version) as the live site, but don't worry if this is not possible. Making a working copy of a Joomla! website involves copying the files and the database (these are separate activities). You will then need to amend the configuration.php to reflect the new location. Check that your test site is fully functional.
|How to copy a Joomla! website|
Step 3: Install the patch package on the copy site
There are different ways of installing a package file depending on your particular circumstances. If you have difficulty with one of these methods, then simply try another.
|Unpacking a package file|
- Alternative 1: Unpack the package file on your local computer then use an FTP client to upload them to your site.
|Using an FTP client to upload files|
- Alternative 2: Use an FTP client to upload the package to your site, then use a terminal session (eg. SSH) to connect to your site and unpack the files there.
|Using a terminal session|
- Alternative 3: If your hosting provider gives you access to your site via some sort of web control panel like CPanel or Plesk, you can use the control panel file manager to upload the package, then use a terminal session (which might also be available via the control panel) to unpack the package file and overwrite all changed files on the server.
- If you are using CPanel, there is specific information on Uploading and extracting an archive file with CPanel.
Step 4: Apply database changes
If you are upgrading from Joomla! 1.5 RC3 or earlier, then you must apply a change to the database. If you are upgrading from Joomla! 1.5 RC4 you can skip this step.
Locate the file /installation/sql/mysql/diff.sql and open it in a text editor. Remove sections that do not apply to the upgrade you are performing. Note that the diff.sql file assumes that your database prefix is set to the default "jos_". If this is not the case then you must manually edit the file to reflect the database prefix that you are using.
|How to determine your database prefix|
Save the file and exit the text editor.
Now apply the diff.sql file to your database.
|How to apply a .sql file to a database|
Step 5: Test thoroughly
Check out as much of the functionality on your test site as possible. If there are any problems that will affect the way that you will need to handle the live upgrade then make a written note of them for later.
If you find errors you might check out the following possibilities:
- Ensure that all of the files were properly transferred. There have been verified reports of some FTP clients not properly transferring files across to a server without notifying the user of such a problem. One possible cause of this problem is that under certain circumstances the web server locks the files it is using and the FTP-server can't update those files. If this is the case you might try taking the site offline shortly during the FTP transfer.