For some basic information on patching and migrating, see [[Upgrading and Migrating FAQs]] and [[Upgrade Instructions]].

−

The Joomla! 1.5 patch packages are listed below. Locate the row that matches your current installation version. Next, select the package: zip, tar.gz and tar.bz2, that is most convenient for you. Verify the download using the MD5 value below the package. If you have questions about these instructions, read the ''Additional Information'' below this table.

+

You can also use a Joomla! extension to automate the process of loading version updates. See [http://extensions.joomla.org/extensions/core-enhancements/installers/9332 Update Manager for Joomla!] for more information.

* Find the correct update file. The Joomla 1.5 downloads are located at the bottom of the page.

+

** If you are on the version ''prior to the current one'', use the file that updates from the prior version to the current version (for example, [http://joomlacode.org/gf/download/frsrelease/16891/73387/Joomla_1.5.25_to_1.5.26-Stable-Patch_Package.zip Joomla_1.5.25_to_1.5.26-Stable-Patch_Package]).

+

** If you are on an ''older'' version, use the 1.5.0 to current version file (for example, [http://joomlacode.org/gf/download/frsrelease/16891/73384/Joomla_1.5.0_to_1.5.26-Stable-Patch_Package.zip Joomla_1.5.0_to_1.5.26-Stable-Patch_Package]).

+

** Select the archive format (zip, tar.gz or 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.

−

{{Ambox|image=notice|text=[[How to determine a package checksum|How to use MD5 has to check your package checksum and what to do if the checksum does not match ]]|style=width:400px}}

+

'''Additional information:'''

−

==Step 2: Make a copy of your live site==

+

{{Ambox|image=notice|text=[[Chunk:patch|What is a patch?]]|style=width:400px}}

−

{{upgrade-copysite}}

+

−

==Step 3: Install the patch package on the copy site==

−

{{installing a package file}}

−

==Step 4: Test thoroughly==

+

{{Ambox|image=notice|text=[[Unpacking a package file|Which package format should I use?]]|style=width:400px}}

−

{{upgrade-test}}

+

−

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

−

{{Ambox|image=notice|text=[[copying a Joomla website|How to copy a Joomla! website]]|style=width:400px}}

−

==Step 6: Install the patch package on your live site==

+

{{Ambox|image=notice|text=[[How to determine a package checksum|How do I use the MD5 hash to check the package?]]|style=width:400px}}

−

{{installing a package file}}

+

−

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

+

==Step 2: Backup your site==

+

Before you actually upgrade, you really should make a backup of your site. Backup your existing Joomla site files and store all the files and database in case something gets messed up, you wont have any problem reverting back.

−

==Step 7: Make any other changes required==

+

All upgrades should be first tested on a copy of your site before being applied to a live site.

−

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==

+

==Step 3: Install the upgrade file==

−

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.

+

{{installing a package file}}

+

+

==Step 4: 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 2.

Hopefully all will be well and you can relax. If you have any questions before, during, or after the upgrade then please ask them on the [http://forum.joomla.org/index.php/board,430.0.html Joomla! 1.5 Migrating and Upgrading Forum].

Hopefully all will be well and you can relax. If you have any questions before, during, or after the upgrade then please ask them on the [http://forum.joomla.org/index.php/board,430.0.html Joomla! 1.5 Migrating and Upgrading Forum].

Return to [[Upgrade Instructions]]

Return to [[Upgrade Instructions]]

+

+

[[Category:Upgrading]]

Revision as of 17:10, 19 January 2013

This Namespace has been archived - Please Do Not Edit or Create Pages in this namespace. Pages contain information for a Joomla! version which is no longer supported. It exists only as a historical reference, will not be improved and its content may be incomplete.

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

Step 2: Backup your site

Before you actually upgrade, you really should make a backup of your site. Backup your existing Joomla site files and store all the files and database in case something gets messed up, you wont have any problem reverting back.

All upgrades should be first tested on a copy of your site before being applied to a live site.

Step 3: Install the upgrade file

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.

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.

Step 4: 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 2.