- This extension requires registration to download.
- Joomla 1.6 is not an upgrade to Joomla 1.5 - it is a MIGRATION. Please check the information on docs.joomla.org prior to starting the process.
of Joomla 2.5, decompress it and install it. After that, it should
migrate all of the data from old Joomla 1.5 to the new Joomla 2.5
The steps to test it
1) Install the component in your Joomla 1.5 site.
2) Run the upgrade
* PHP 5.x
* Curl module of PHP enabled
* Joomla 1.5
* Enable System - Mootools Upgrade plugin that is included in Joomla 1.5.19 and greater.
A new tracker is created for jUpgrade and Joomla 2.5 migrations bugs. You can access (and use it) here:
If you have problems with migrations please go to Settings and set "Debug" = ON.
The way to test it:
1) remove ROOT/tmp/joomla25.zip and ROOT/tmp/size.tmp
2) remove ROOT/jupgrade directory
3) delete all j17_ tables (except j16_jupgrade_categories and j16_jupgrade_menus)
4) REMOVE OLD jUpgrade installation and install the version 2.5
5) Set "Skip download" to 'No'
6) F5 to reload the browser
7) Run upgrade
People who have had issues, I completely understand. The first time I used jUpdate it was a little stressful but if you read all of the excellent documentation here on Joomla.org and on the Developer's site you should be fine.
Have used to migrate 6+ sites already and haven't had an issue with a single one. As mentioned above the support and documentation is top notch, the steps are easy to follow, and I haven't had a single glitch so far.
I do recommend backing up your site with Akeeba and DLing the archive before attempting to use jUpdate though - Just to be safe. 5 Stars.
Joomla should have a much better way for us to migrate over to 2.5. I'm completely lost on how I'm going to do this. This certainly is no help whatsoever
1) Make sure all upgrades are completed as requested (Joomla higher than 1.5.19 - I upgraded to 1.5.25 first) before starting the upgrade
2) I did experience the "freeze" in IE, but it worked in Firefox
3) After the "migration", the new site is now at www.yoursite.com/jupgrade until you move the original files OUT of the root and the file in the jupgrade directory into the root. (there is a great post in the comments of the upgrade video on youtube on how to do this)
3) You will need to "clean up" the new site, as I found the JA Purity template from v1.5 had some differences from the default v2.5 templates, so plan some time to redo some banners, etc.
Other than that, it seemed to be a good process. Not including the "tweaks" to the new template, it took me less than 2 hours for the entire project, including research.
Upgraded 4 sites from 1.5.25 to 2.5.x now with this no problems at all.
Will be great when it includes even more components and different modules.
Quick note: I had one glitch, I was migrating from J1.5 and I was not aware that I needed to set jupgrade to go to 1.7 first. Small detail: minor hangup. Completely my fault for lack of understanding. Otherwise EXCELLENT job.
I followed the installation instructions very carefully, checked write permissions, enabled PHP cURL, enabled MOOTOOls, and tried every combination of parameters.
The process hung in every instance. Very disappointing and time consuming.
As for support forget about that there is none or at minimum VERY VERY VERY little of it. Had problems many others have had and there was no answer to those questions asked for the same problem over and over.
For being an extension that is still being updated they can at least provide better support. Especially, when there is such a large number of users for this extension.
Oh did I forget that there is bugs (not security issues that I seen just bugs) in this current version of the extension too. It gets old when you have to save the parameters then leave to another component and come back to jUpgrade just to get your parameters that you saved to work.
Just my 2 cents on this extension, maybe it will work for you. Maybe just maybe those that run their forums will actually start answering questions of the same problems.
The problems that come in are far to great for this to be a viable method of upgrading. The component will install into a subdirectory, and use the same DB as your original install (doesnt overwrite anything) which is great.
It just seems to be far from complete. I watched as it migrated my components, modules, content, etc only to find that it would not be present once it was finished. I had to install the new K2, which is fine, and once I did, all of my articles showed back up. Only problem is, NONE of the access levels transfer, so you have to manually open and close each menu item, article, category, k2 it, k2 category, etc in order to get the items to publish again. If you don't do this, you'll get hit with 403/404 errors anytime you attempt to access content. It does not migrate any of the component settings that you had, so all categories and items that inherit parent properties will have to be set again. Not a big deal, but if you're going to tell me you're importing my components, make sure they're actually migrating.
I was very, very excited about this component, only to be let down completely. I could have completely migrated to a new 2.5 install by just copying over my articles and manually installing components.
This component has quite a bit of potential, but is no where near ready to be considered the official migration solution, which it seems to be marketed as pretty much anytime you search google for migration options from 1.5 to 2.5
If you are looking for a quick migration solution, and especially if you're not familiar with phpmyadmin (for some issues) do not bother trying this component, as you will end up frustrated that you're site isnt working.
Your best bet is to perform a clean install, migrate your articles yourself and reinstall your components. It may seem overwhelming, but you'll end up doing the exact same thing if you use jUpgrade.
I would like to note though, had I not had ANY third party components installed, and was using j1.5 with only it's native functions, I believe jUpgrade would have worked perfectly.
I will go the manual process now ...
I encounter problem, the support comes with a solution and still it doesnt work. And they keep encouraging for the solution when it doesnt work.