- This extension requires registration to download.
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
I spent many hours attempting to get the upgrade to 2.5 to happen, but it hung every try. I posted the handing errors to their support forum, but apparently they no longer do support on their support forum and you must purchase a subscription to all their extensions to get support on jupgrade.
I'd rather they just sold jupgrade, as I don't need the other extensions.
I'm moving on to another package, because this one doesn't work, and it wasn't made clear when downloading that no support is provided unless you pay for it.
There are some heavy duty gotchas so this is what i did to get it working.
Make sure you're at J1.5.26. Use Akeeba backup (3.4.3 - not higher) to make a copy of the site. Set up a test server, create a new database and restore a copy of the site. During the restore (i used akeeba kickstart) make a note are you using mysql or mysqli (probably mysqli).
On the test server, rename your htaccess file to htaccess.txt and create a folder on the root called jupgrade. Inside that folder extract joomla 2.5.4 (not higher, jupgrade won't work otherwise). Doing it this way means you don't have problems with curl and its just faster. Log in to the test site and under config > site, uncheck use Apache module_rewrite if its on. Under plugins > system enable MooTools Upgrade. Now install JUpgrade 2.5.2 and in the Parameters menu, change skip checks, skip download and skip decompress to YES. Note that jupgrade uses the mysqli driver by default so if you chose mysql during the akeeba restore you will need to change that here also. Save those changes and click on the upgrade button.
If it fails/stalls, you can try again but remember to dump out any j25_ tables in the database, clear out the jupgrade folder and start over. If it works, it does it in a couple of minutes. Your original site is preserved, your new site is in the jupgrade folder - so you have 2 different paths for each. But both are there for reference and you can start to fix stuff til its right.
JUpgrade installed like a dream and upgraded the site cleanly and quickly. In less than 5 minutes JUpgrade was installed and my site was upgraded to 2.5 from 1.5. perfectly.
Great work folks! This is how it should be.
The result was wonderful. Of course, there are many mistakes that can be made. I decided to read the documentation very carefully, step by step, while I did the migration. The comments about using Akeeba backup for the 1.5 original site need very careful scrutiny of the Akeeba site to make sure that there is a version compatible with your combination of Joomla and PHP - and there may not be. I skipped all of that and used cPanel for the backup.
The basic upgrade worked like a dream. I made one mistake - I also copied over the templates - that was a mistake. I deleted the first jupgrade migration and re-ran it without the templates (yes, that left me a bit uncertain about comments suggesting jupgrade can damage the 1.5 installation - I had no problems, after the upgrade, accessing the 1.5 and 2.5.6 sites before switching them over, and no problems running jupgrade a second time on the 1.5 site). After the 2nd upgrade without templates, I reinstalled a 2.5 compatible version of the template. It took more time configuring the 2.5 compatible version of the template than migrating Joomla with jupgrade.
So, for me, it was an extremely helpful tool. My bottom line is follow the documentation carefully, step-by-step, backup with cPanel or something else, rather than Akeeba (I installed Akeeba backup and admin tools after the migration) unless you are certain you have a compatible version. If you have a 2.5 compatible version of your template, don't try to migrate the version 1.5 template; install the 2.5 version after the migration the configure the template.
Great tool - so good, that it left me very puzzled about some of the negative reviews here, but I guess some people had big problems for some reason or another. I'm really pleased I decided to try it.