- 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
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.
I was told by support in their forum to skip migration of the component that was giving the error, which I did, and migration to complete successfully. But how would I manually migrate the problem component?
That's the whole problem with these out-of-the-box solutions when they don't work. If I knew how to roll up my sleeves and start rooting around in php and sql, I would hardly need an out-of-the-box solution, would I?
I suppose this would work fine if you're looking to automate a manual process that you're capable of executing, but if you're looking for a component to handle something you don't have the skill set for, this might not be the best choice.
After several days of this, it's worth spending the money on a commercial solution and be done with it, in my opinion. I suppose you could pay for the support or whatever the option is, but again, I don't want to pay for more days of a process that I just want to be over.
I use it for migrating my site from Joomla 1.5.22 to Joomla 2.5. But first I need to upgrade my Joomla manually from 1.5.22 -> 1.5.23 -> ... -> 1.5.26.
Ensure the setting are correct. What I've tried.
1. Skip check
2. Skip downlowd
3. Skip unpack
(I use the unpacked copy of stable Joomla 2.5 on the jupgrade folder, means I do it manually since my internet connection is not that good). Not working well on IE9 but working well on my latest Firefox.
Make sure the prefix of your database is the same as in your database :)
Thank you very much for to the developer for this great extension.
I have upgraded several websites from J1.5.26 to 2.5 but with a combination of J2.5.4/6 and jUpgrade 2.5.0/1 updates something has become broken. It's a shame that the developers don't seem too interested in a very long thread on their forum either.
Now for a search for an alternative.
It doesnt work at all. I installed it with now problem, but when i wanted to migrate it got stuck in the upgrading process. It looked like it did something in the start but then it just keep sending the same info [undefined][undefined].
I have searched the internet, and many have the same problem and many are saying that i doesnt work at all.
So i wont recommend this extension at all.
Its time for the developers of Joomla to take their hands out of there asses and make a update extension that can do this.
It hangs on the last step, and if that happens I dont bother trying to fix it, I used to.. but its an exercise in futility most of the time and a MAJOR time suck, and the majority of the time I can never get it to work.
So, I purchased the componant "SP Upgrade" and it has worked every time.
However, I usually try using this componant first, this one is pretty much one click, and "IF" it works it is a much simpler upgrade than using SP upgrade, with less steps.
SO give this one a try, if it fails and hangs on the last step, honestly I wouldnt even bother trying to figure it out (maybe give it an hour), go purchase SP upgrade and use it instead, its worth the $$ the and support is great.
IF jupgrade works for you WOO HOO... score! Im all about getting from point a to point b as efficently as possible, and with the least amount of hassle... If this componant happens to work for you, you just did that, if it fails... simply move on.
That is NOT a ringing endorsement from the joomla developers. It would literally be faster to create a new site in 2.5, and copy and paste over all our information from the old site. The only positive thing I can say about it is that it's smart enough to put everything in a separate directory so you don't end up with a corrupted site.
jUpgrade installs easily enough. So do most components/plugins.
Click the Parameters button to change jUpgrade settings. After you adjust your settings, click the Save button. You're not taken back to the main jUpgrade pane. Clicking Cancel does nothing. If you click in the address field and press enter (after clicking Save), it takes you back to the administrator back-end index page.
After confirming that I meet the requirements for jUpgrade (as listed on the developer's website), I click the Start Upgrade button. Nothing happens and no feed back is provided to let me know what if anything has gone wrong.
So far, jUpgrade appears to be form/style over function/substance.
Make sure that when you change jUpgrade parameters, you do a screen refresh (F5) after saving them.
Conclusion: it works (for me), but it is not a 'pearl'!
I've seen lot's of complaints about this on other forums. So I thought I'd give it a try on a trivial test site I have.
It leaves a big security problem too unless you clean up after it. The URL:
www.what-ever-your-site-is.whatever/jupgrade is left with the install directory in place, so anyone can then log in to the (empty) new site.
Interestingly the support links under
all fail with a 404.
Oh well, this is turned out to be a totally useless migration tool.