I have used the extension SP Upgrade and it has worked well on the several sites I have migrated. The good thing is that you create a new 2.5 installation and it imports the data from the live site. This leaves the live site untouched and working until you want to go live with the new site.
Time depends on number of extensions. SP Upgrade does the core Joomla and Content as the first wave. You can then select database table by extension to import but do check with each developer. Things like RS Forms allows you to create a backup of forms and data that is then imported via the new installation of RS Forms on the new site.
I have done small sites in a couple of hours and big sites can take longer. Don't forget that you may need to manually intervene to get correct urls etc.
I will be doing a medium sized site next week and that is going to be about 6.5 hours of work at best guess.
Hope this helps
Please search forums before posting. Please make sure your post includes the version of the CMS you are using and a link to the problem. Annotations on screenshots can also be helpful to explain problems/goals. Please use the "secure" tab for confidential information
What makes you think that the link you posted will call up the template? That link is to the installation folder and there is already a Joomla installation on that url so the installation folder will have been deleted.
Please search forums before posting. Please make sure your post includes the version of the CMS you are using and a link to the problem. Annotations on screenshots can also be helpful to explain problems/goals. Please use the "secure" tab for confidential information
Hi David,
I am in the process of using SP Upgrade as you recommended. Works pretty good. So, now I have the new Joomla 2.5 folder, with changes and updates. Can you recommend the best way to make that live to replace the older fles that it sits in. I couldn't find very much documentation on this last step.
What I usually do is install Akeeba backup to the new site. Create a back up. Move the backup file to the public root.
Next I create a directory called oldsite. Put the existing site offline and then use cpanel to move all the Joomla directories/files from public root to the new directory - oldsite.
I then upload Akeeba kickstart to public root and use that to restore the jpa backup file to the public root. This takes care of most paths and permissions. Once new site is tested and working it can be put live and oldsite directory downloaded for safekeeping and deleted from the server.
Hope this helps
Please search forums before posting. Please make sure your post includes the version of the CMS you are using and a link to the problem. Annotations on screenshots can also be helpful to explain problems/goals. Please use the "secure" tab for confidential information
Wow, thanks for the speedy reply. Most of my sites are now at 1.5.25. should I continue the incremental patches are just do the big jump?
The real trouble Im having is I have a couple of sites that are J 1.0.13 and I need them desperately upgraded as I think they will fail when we go to MYPHP 5.3 tonight.
Interestingly, these 1.0 sites ( community intranets) were built by Andy (Rhuk) as Mambo sites back in the day. The have stood the test of time. In fact, I believe it was the first template when he started Rockettheme.
On older sites I use the 1.5.0 to 1.5.26 patch - covers all sins.
I can't even remember 1.0 any more, let alone mambo (which was my first CMS!
Please search forums before posting. Please make sure your post includes the version of the CMS you are using and a link to the problem. Annotations on screenshots can also be helpful to explain problems/goals. Please use the "secure" tab for confidential information