- 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
1) When you change the "parameters", there is a bug in that they don't save properly - for example, i changed the table prefix and directory path. I ran the upgrade and it used the "old" settings. I closed out, ran it again and it used the "new" settings so there is a problem with the parameters settings.
2) Most importantly, what JUpgrade does not warn you about is that it puts all the "new tables" into the existing database. I wish it had warned me of that - now my legacy database is muddled with a bunch of new tables and I had to restore my site/db.
3) And of course the final piece - it simply did not work. None of the articles, sections, categories, etc came over. It pretty much failed all the way around yet gave no errors or other warnings.
This is an unreliable/buggy extension to say the least.
And the site I attempted to use this on was VERY vanilla. Not a single 3rd party extension - was literally just a plain 1.5 site with articles.
There were a few problems getting everything working, but that was my fault. I would highly recommend reading the documentation and creating an upgrade plan before getting started.
The first issue is to make sure that if you're coming 1.5.x that you upgrade to 1.5.25. Second, if you want automatically migrate extensions, make sure the currently installed versions are 2.5 compatible. CB and Kunena are good examples of extensions that can be installed in 1.5.25 and automatically migrated to the new 2.5 site. Interestingly, I thought CB would have issues, but the 1.7 version core functionality appears to be working correctly in the new 2.5 site. In other cases, you might have to go to 1.7 first since it seems that many extensions are 1.7/2.5 compatible.
I still have a lot of work to do, but this extension definitely made my life a lot easier. Thanks and great job!
There are so many things utterly broken by this. For example all my categories are present, but do not work.
If I choose category blog as a menu item and choose a migrated category, the site 404s. If I create a new category and choose that category, it's fine. That means I have to go through and recreate all the categories, but they're right there.
Weblinks required I went through each category and open and save (with changing nothing) to make them work and put them all the links back into their categories.
I almost think I would have been better off learning how to manually migrate the site, because what I'm left with is a migration that transferred very little and of the stuff it did transfer most of it is quite broken and useless.
It seems that many of them just don't understand how difficult it is to transfer all data from Joomla! 1.5 to Joomla! 2.5.
In my opinion this extension manage this task perfectly.
Of course if you are expecting to have all data, extensions and templates transferred with just a one click, you may be disappointed.
But if it is clear for you that it needs a bit more work than one or two clicks, you'll be happy with this extension.
I think we should be very thankful for all the hard work Matias put in this component.
All tables must have the collation of utf8_general_ci , and all applicable columns within those tables must have that collation as well.
The jUpgrade script should alter the talbes and columns for you, maybe that could be a future update? Before I changed all tables to that collation I was able to go through the upgrade process, however it did not pull over menu items or extension positions. So I changed the collation, ran it again, and everything worked perfectly.
Two things that I was very displeased with:
-Asking for my address on registration
-Sending back my password in plaintext (which means they store it in plaintext)
I learned all the fixes i could have; i have a basic Joomla! installation with a very few but popular components:
Joomla! 1.5.25; CB; Akeeba Backup; Uddeim; etc.
Guy, your component doesn't work. It's easy as this: when i finally get the migration, ony with a few of your releases, it has full of fixes to do and it's simply annoying (and boring).
But, why you don't advise here that the component CHANGES the id's of the articles, doing a nightmare with internal and external links? with comments who now links to different articles?
I'm sure that Joomla! promote this upgrade component because they can't promote a commercial one, but this component works mabye for a blog in Joomla!, or smaller communities, but for sites like mine with more than 2500 articles it's worst than start from the scratch, really -i don't wanna talk about the template issues...-.
I readed all the hints, tricks, tested, in the new recomponent forum of JUpgrade, and i'm very sorry for this review, because i know it's free and you are adding it to help the community, but the real thing today is -i've tested again the x.25 release- that it doesn't work. I'm gonna test the SPUpgrade, and a I recommend everybody don't use this component, just look in the support forum and the joomla! forum with 90% with the SAME unsolved problems.
I'm sorry. But it's my tested review, tired of trying to make it works.
It probably works fine if you want to migrate simple Joomla pages, but definately does have its bugs if you try to migrate complex websites.
Same id's- Why is this so important?
Google ranking is not affected
No broken internal links (e.g. within your articles)
No broken external links. Those are links from other domains to your site
I followed all the directions, and the "update" process won't even begin. When I sought help on the forum, I got a response that the problem is MooTools, not them (of COURSE), and I should "install" the plugin I'd already mentioned I had activated.
The litany of other complaints below show I am far from alone in my problems with this component.
Don't waste your time! Avoid the migraine! Do a manual migration.
The installation process gets stuck in the middle, with not a single error.
But, after uploading manually the files to the server, the installation claims to have "upgraded" also all the "k2" stuff and akeeba component. Nice, isn't it?
Well. This is the result:
-k2 component just disappears from the backend (can't be managed)
-akeeba component just disappears from the backend (cant't be managed)
-although k2 items still exist, they can't be displayed on the site (no matter what you do with user permissions, menu links and so on).
Result: the site doesn't exist anymore.
The only good point with this extension is that, as it creates a separate directory for the new installation (/jupgrade), it's quite easy to send an FTP command to delete it.
After this, I'm going to try the manual installation process. But I will keep wondering why joomla recommends this component, given that almost 50% of users have given a a negative feedback.
I do not like the fact that I have NOTHING in my administrator section of the website...with no errors reported from jupgrade. My frontend of the site appears to be migrated, however logging in to the backend of the website reveals there is nothing there! Just a header stating ADMINISTRATOR, but no navigation menus, no admin modules or components, nothing. So that pretty much renders this component useless for me.
I went with another commercial migration component and it worked well, but it did not migrate kunena which I will now have to figure out how to do. So free migration one sort of worked, paid migration component worked better...but no complete migration solution yet.