J2.5:Updating from an existing version - Revision history

Tom Hutchison: redirect

2015-04-24T20:02:28Z

redirect

← Older revision		Revision as of 20:02, 24 April 2015
Line 1:		Line 1:
	{{warning\|This doc is under review, please do not use until it is updated.}}{{warning\|<center>'''Always back up your site before updating.'''</center>}}{{notice\|Newer documentation is available that starts with the page [[Why Migrate]] and is a funnel for migrating from 2.5 to 3.x. \|title=Please Take Note}} {{notice\|This page is only for upgrading from Joomla! versions '''1.7''' to '''2.5''' or a '''2.5.x''' version to '''{{CurrentLTSVer}}'''.{{-}} For '''Version 1.6''' see the [[#~~Troubleshooting\|Joomla! version 1.6 work around]] section.\|title=Please Take Note}}~~		#REDIRECT [[Portal:Upgrading Versions]]
	~~__TOC__~~
	~~The recommended way to update installations of Joomla! is to use the Joomla Updater component '''(Method A)''' found in the Components menu of your site Administrator.~~

	~~== Quick Overview ==~~
	~~This section is a quick summary of Method A. Most updating is a maintenance version update and a simple procedure. Be sure you have a backup of the current installation.~~
	~~;Browse to Components {{rarr}} Joomla Update~~

	*If an update is available there will be a message indicating this and a button to press.
	[[~~File:Updatewaiting.PNG\|670px]]~~

	*Click on the "Install the Update" button and allow the update to run.

	~~[[File:Updatecompleted25.PNG]]~~

	~~{{Tip\|When updating has completed you may need to refresh your screen or empty your browser cache to adjust for template CSS changes.}}~~
	{{warning\|Joomla! will notify on your administrator home page (control panel) when an update is needed, but it will not do the update for you. You need to press the button to start the update.\|title=It is Very Important to Note!}}

	~~==Checking Site==~~
	~~'''This is required for method A and B!'''~~
	~~After an update, it is a good idea to clear your browser cache snd check your site to make sure the update was successful. There are two quick checks you can do from the Extension Manager.~~
	~~==Extension Manager: Check Database==~~
	~~{{JVer\|2.5}} This feature was added in version 2.5.0. It checks that your database is up to date with your Joomla programs.~~

	~~Navigate to Extension Manager: Database. If your database is up to date, you should see a screen similar to the one below:~~
	~~[[Image:Update-screenshot-20120124-04.png\|center\|Database Screen With No Problems]]~~

	~~If your database is not up to date, you will see a screen listing the problems found, similar to the one below:~~
	~~[[Image:Update-screenshot-20120124-05.png\|center\|Database Screen With 3 Database Problems]]~~
	In this case, press the Fix button in the upper right corner. Joomla will update your database to correct the issues listed and then it will re-display the screen. If the fix was successful, the display will indicate that the database is up to date.

	~~'''N.B.''' If any errors fail to fix then make sure all the database Tables are checked in.~~

	~~;Extension Manager: Discover~~
	In some cases, when you update to a new Joomla version, new core extensions are added. If there were problems with the database update, these extensions may not have been correctly installed. To check this, navigate to Extension Manager: Discover. Then click on the Discover icon in the toolbar. The screen should show as follows:
	~~[[Image:Update-screenshot-20120124-06.png\|center\|Discover Screen With No Extensions To Install]]~~
	~~If so, you know that any new extensions added during the udpate were correctly installed in the database.~~

	~~If there are uninstalled extensions, they will show similar to the following screen:~~
	~~[[Image:Update-screenshot-20120124-07.png\|800px\|center\|Discover Screen With Two Extensions To Install]]~~
	In this case, check the check boxes and click on the Install icon in the toolbar. Joomla will install the extension(s) and then display the screen showing no extensions discovered. At this point, the new extensions have been installed in the database.

	~~==Troubleshooting==~~

	~~;Trouble Shooting and Advanced Techniques~~
	~~Starting with version 1.6, there are three ways to update your Joomla Website to versions 1.6, 1.7 or 2.5.~~
	~~If you are in an older version that did not support one click updates or are on a server that does not allow such updates you should use one of these options.~~

	* Extension Manager: Update
	* Extension Manager: Install
	* Manually Copy Program Files

	~~Each of these is discussed below.~~

	~~===Upgrade from version earlier than 1.6.x to Joomla 1.7? ===~~
	This page does not contain the instructions for migrating a Website from Joomla versions earlier than 1.6. See the [[J2.5:Migrating from Joomla 1.5 to Joomla 2.5\|Migrating from Joomla 1.5 to Joomla 2.5]] page.

	~~===Upgrade from version 1.6.x to Joomla 1.7? ===~~
	~~Note: To upgrade from version 1.6.x to Joomla 1.7 please follow the [[Upgrade 1.6.5 to 1.7\|Upgrade 1.6.5 to 1.7 guide]] before you upgrade to Joomla 2.5.~~

	~~===Upgrade to Joomla 2.5 on shared hosts===~~
	{{notice\|<small>''On some shared host environments (GoDaddy.com and perhaps others), the normal Joomla update from 1.7 to 2.5 can intermittently fail with the error "Internal Server Error". In some cases, this can happen in the middle of the file transfer process and cause errors on the site. On GoDaddy.com, this appears to happen when the server is under a heavy load and the update takes longer than 2 minutes to complete.''
	''Based on recent testing, sites on these slower shared hosts can safely be updated using a free third-party extension called [http://tinyurl.com/7d9odse Admin Tools]. If you are updating a site on a shared host, please consider using Admin Tools or else use the Manually Copy Program Files method outlined below.''
	~~''If you have experienced an error during the update, there is a process for repairing the site.''</small>\|title=Important note as of 28 January 2012}}~~

	~~'''Steps and actions:'''~~
	~~It is recommended that you follow these steps when updating a production site:~~
	~~# Back up your site before upgrading to a new version. That way, if something goes wrong during the upgrade process, you can easily restore your site to the earlier version.~~
	~~# Review the release notes for the new version to be familiar with what was changed.~~
	# Update using one of the recommended methods outlined in this document. These methods install the new program files, delete unneeded old program files, and update the database as needed for the new Joomla version.
	~~# Clear your browser cache and check that the update was successful, using the steps outlined in the '''Checking Site''' tab.~~

	If you have any questions before, during, or after the upgrade then please ask them on the [http://forum.joomla.org/viewforum.php?f=625&sid=259a29d8e21242b6770f86026f6c9c3a Joomla! 1.6 Migrating and Upgrading Forum].

	~~{{tip\|title=Problems or Errors During the Update Process?\|~~
	~~If you have problems or errors during the update process, here are some tips.~~
	* Clear your browser cache as there may have been changes to the css or javascript that will need to be reloaded by your web browser.
	* If any database error messages show after the update, be sure to check the Extension Manager: Database tab followed by the Extension Manager: Discover tab. In some cases, if a database error occurs it will prevent all the database updates from running. In this case, you can run them from the Database tab and then use the Discover→Install method to check and install any new extensions.
	* If you encounter any errors or problems during or after the update, be sure to check the FAQ for the version you updated to. For example, for version 2.5.0, this will be an article entitled [http://docs.joomla.org/Category:Version_2.5.0_FAQ http://docs.joomla.org/Category:Version_2.5.0_FAQ].}}

	~~[[Category~~:Upgrading]]
	~~[[Category:Joomla! 2.5]]~~
	~~[[Category:Update Working Group]]~~
	~~[[Category:Incoming External Link~~]]

Tom Hutchison: /* Method A - Update Method (Recommended) */ blanking

2015-03-04T05:15:29Z

Method A - Update Method (Recommended): blanking

@@ Line 16: / Line 16: @@
 {{Tip|When updating has completed you may need to refresh your screen or empty your browser cache to adjust for template CSS changes.}}
 {{warning|Joomla! will notify on your administrator home page (control panel) when an update is needed, but it will not do the update for you. You need to press the button to start the update.|title=It is Very Important to Note!}}
 ==Checking Site==

Tom Hutchison: /* Method B - Install Method */ blanking

2015-03-04T05:04:57Z

Method B - Install Method: blanking

@@ Line 37: / Line 37: @@
 # Select the update (using the checkbox) and click on the Update icon in the toolbar.
 # '''IMPORTANT:''' This process will take a few minutes. Wait until the process completes and the success message shows, similar to the screen shown below. [[Image:Update-screenshot-20120124-02.png|center]]
 # Congratulations! At this point, your site is updated.
 '''Important:''' Clear your browser cache and check that your site is working correctly. See below Checking Your Site

Tom Hutchison: /* Method C - Manual Upgrade */ removing this for now

2015-03-03T21:05:10Z

Method C - Manual Upgrade: removing this for now

@@ Line 88: / Line 88: @@
 # Congratulations! At this point, your site is updated.
 '''Important:''' Clear your browser cache and check that your site is working correctly. See below Checking Your Site
 ==Checking Site==

Tom Hutchison: added Category:Incoming External Link using HotCat

2015-03-03T03:01:00Z

added Category:Incoming External Link using HotCat

← Older revision		Revision as of 03:01, 3 March 2015
Line 206:		Line 206:
	[[Category:Joomla! 2.5]]		[[Category:Joomla! 2.5]]
	[[Category:Update Working Group]]		[[Category:Update Working Group]]
			[[Category:Incoming External Link]]

Tom Hutchison: Warning

2015-02-22T16:43:00Z

Warning

← Older revision		Revision as of 16:43, 22 February 2015
Line 1:		Line 1:
	{{warning\|<center>'''Always back up your site before updating.'''</center>}}{{notice\|Newer documentation is available that starts with the page [[Why Migrate]] and is a funnel for migrating from 2.5 to 3.x. \|title=Please Take Note}} {{notice\|This page is only for upgrading from Joomla! versions '''1.7''' to '''2.5''' or a '''2.5.x''' version to '''{{CurrentLTSVer}}'''.{{-}} For '''Version 1.6''' see the [[#Troubleshooting\|Joomla! version 1.6 work around]] section.\|title=Please Take Note}}		{{warning\|This doc is under review, please do not use until it is updated.}}{{warning\|<center>'''Always back up your site before updating.'''</center>}}{{notice\|Newer documentation is available that starts with the page [[Why Migrate]] and is a funnel for migrating from 2.5 to 3.x. \|title=Please Take Note}} {{notice\|This page is only for upgrading from Joomla! versions '''1.7''' to '''2.5''' or a '''2.5.x''' version to '''{{CurrentLTSVer}}'''.{{-}} For '''Version 1.6''' see the [[#Troubleshooting\|Joomla! version 1.6 work around]] section.\|title=Please Take Note}}
	__TOC__		__TOC__
	The recommended way to update installations of Joomla! is to use the Joomla Updater component '''(Method A)''' found in the Components menu of your site Administrator.		The recommended way to update installations of Joomla! is to use the Joomla Updater component '''(Method A)''' found in the Components menu of your site Administrator.

Tom Hutchison: Tom Hutchison moved page J2.5:Upgrading from an existing version to J2.5:Updating from an existing version: moving around

2014-12-09T17:02:03Z

Tom Hutchison moved page J2.5:Upgrading from an existing version to J2.5:Updating from an existing version: moving around

← Older revision	Revision as of 17:02, 9 December 2014
(No difference)

Jgress- at 22:23, 7 December 2014

2014-12-07T22:23:33Z

← Older revision		Revision as of 22:23, 7 December 2014
Line 1:		Line 1:
	{{warning\|<center>'''Always back up your site before updating.'''</center>}}{{notice\|This page is only for upgrading from Joomla! versions '''1.7''' to '''2.5''' or a '''2.5.x''' version to '''{{CurrentLTSVer}}'''.{{-}} For '''Version 1.6''' see the [[#Troubleshooting\|Joomla! version 1.6 work around]] section.\|title=Please Take Note}}		{{warning\|<center>'''Always back up your site before updating.'''</center>}}{{notice\|Newer documentation is available that starts with the page [[Why Migrate]] and is a funnel for migrating from 2.5 to 3.x. \|title=Please Take Note}} {{notice\|This page is only for upgrading from Joomla! versions '''1.7''' to '''2.5''' or a '''2.5.x''' version to '''{{CurrentLTSVer}}'''.{{-}} For '''Version 1.6''' see the [[#Troubleshooting\|Joomla! version 1.6 work around]] section.\|title=Please Take Note}}
	__TOC__		__TOC__
	The recommended way to update installations of Joomla! is to use the Joomla Updater component '''(Method A)''' found in the Components menu of your site Administrator.		The recommended way to update installations of Joomla! is to use the Joomla Updater component '''(Method A)''' found in the Components menu of your site Administrator.

Tom Hutchison: added Category:Update Working Group using HotCat

2014-08-19T23:41:32Z

added Category:Update Working Group using HotCat

← Older revision		Revision as of 23:41, 19 August 2014
Line 205:		Line 205:
	[[Category:Upgrading]]		[[Category:Upgrading]]
	[[Category:Joomla! 2.5]]		[[Category:Joomla! 2.5]]
			[[Category:Update Working Group]]

Tom Hutchison: /* Method C - Manual Upgrade */ making a tip!

2014-02-23T14:11:09Z

Method C - Manual Upgrade: making a tip!

← Older revision		Revision as of 14:11, 23 February 2014
Line 92:		Line 92:
	This method is similar to the old method for updating Joomla versions. Here we want to replace the existing program files with the files from the update archive. The advantage of this method is that it will work on slower shared hosts. The disadvantage is that it requires more work by the system administrator.		This method is similar to the old method for updating Joomla versions. Here we want to replace the existing program files with the files from the update archive. The advantage of this method is that it will work on slower shared hosts. The disadvantage is that it requires more work by the system administrator.

	''~~Important:~~ This method can also be used to repair a site where the automatic update failed due to a server timeout.''		{{tip\|''This method can also be used to repair a site where the automatic update failed due to a server timeout.''}}

	===Copy the New Program Files to Your Site===		===Copy the New Program Files to Your Site===