Upgrading 1.5 from an existing 1.5x version

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).

You interested in having your Joomla 1.5.x site automaticly updated for you? If so check out this

Step 1: Download the patch package

To download the most recent patch package and to obtain the MD5 hash:

• From the joomla.org home page, click the Joomla! 1.5.x download link
• On the Joomla! 1.5.x release page, click the Joomla!1.5.xupdates link in the left column.
• Click the word Files in the blue bar to expand the list of patch packages available.
• Locate the row that matches your current installation version.
• On that row, select the patch package (zip, tar.gz and tar.bz2) that is most convenient for you.
• Verify the download using the MD5 hash listed in the right column on the same line as the package you selected.

If you have questions about these instructions, read the Additional Information below this table.

Additional information:

What is a patch?

Which package format should I use?

How do I use the MD5 hash to check the package?

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: 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.

Step 5: Backup your live site

Take a full backup copy of your live site immediately prior to upgrading. You may want to take your site offline prior to doing this so that updates are not lost.

How to copy a Joomla! website

Step 6: Install the patch package on your live 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 target="_blank" rel="nofollow"Uploading and extracting an archive file with CPanel.

The alternative selected may be different from that used in step 3 if the hosting platform for the site is different.

Step 7: Make any other changes required

Referring to your notes from step 4, make any other changes that are required to bring the site into operation following the patch installation.

Step 8: Check your live site to make sure it is working correctly

Don't assume that the upgrade will work flawlessly just because the test upgrade worked. Check to make sure that nothing untoward has happened. It could be that differences between the live site and test site platforms will bring out a problem that you did not notice during testing. If you find a problem and it cannot be resolved quickly you might have to rollback the upgrade using the backup copy you created in step 5.

Hopefully all will be well and you can relax

TrackBack URI for this entry

Comments (0)

Subscribe to this comment's feed

Show/Hide comments

Name

Email

Website

Title

Comment

smaller | bigger

Subscribe via email (Registered users only)

I have read and agree to the Terms of Usage.

Write the displayed characters

Add Comment