I'm very happy to announce this version 1.2.2 of jUpgrade in the new redCOMPONENT house. Thank you very much Ronni for supporting jUpgrade and for helping the entire Joomla Community.

The most relevant changes in this version is the redSHOP, Community Builder, JCE and Contact Enhanced support. Special thanks to Matias Griese for all the help with the 3rd extension migration.

Please contact us if you like to add your Joomla extension into the jUpgrade migration.

Remember that a tracker is created for jUpgrade and Joomla 1.7 migrations bugs.

You can access (and use it) here:
forge.joomla.org/gf/project/joomla/track...amp;tracker_id=10539

And you must to enable System - Mootools Upgrade plugin that is included in Joomla 1.5.19 and greater.

IMPORTANT: If you are having problems with downloading or the decompressing steps please RTFM -> redcomponent.com/forum/92-jupgrade/102880-jupgrade-faq

The list of changes:

• Added redSHOP support
• Added CommunityBuilder support
• Added JCE support
• Added Contact Enhanced support
• Better 3rd extensions management (thanks Matias Griese)
• Joomla package updated to 1.7.1
• Scroll down in each step (thanks Marco Barbosa)
• jUpgrade added to opentranslators.org

Just to note Johnny is releasing on behalf of Matias Aquirre.

Strange thing is, I've followed all the steps and when it's time to hit Upgrade Now, there's no response. Not sure if this is the right forum to say this in but any help would be appreciated.

With 1.2.1 I was just missing kunena.
With 1.2.2 I appear to be missing the whole backend.

Not enough time now but will look into it further tomorrow.

Remember the FAQ offers lots of help

redcomponent.com/forum/92-jupgrade/102880-jupgrade-faq

For Kunena, check my post

redcomponent.com/forum/92-jupgrade/10536...a-by-jupgrade#105369

If I understand you correctly, now is possible to upgrade my joomla 1.5 with virtuemart to joomla 1.7 and redShop?

Kunena should migrate just fine with JUpgrade 1.2.2.

FYI: There are a few bugs that people should be aware of when they do the migration:

1. When you first login to the new site (admin), you see nothing. Workaround: Logout and login.
2. Modules do not show up (Menu Assignment = No pages). You need to manually assign menu items to all your modules.
3. Menu item aliases having the same name as real menu items force real SEF alias to be renamed.

There are also a few small issues after migration, but generally the site seems to be OK.

thank you.

I'm new so don't beat me up please for asking a question that may have already been asked, still trying to get my head around the site. Why does Curl in PHP need to be turned on, is it because the upgrade has been written in Curl? Reason I am asking, the person that looks after my Linux Ubuntu server for me, advised that Curl was really liked by hackers to inject malicious coding into, hence my question.

Thanks for this jUpgrade as well, have tried it once so far, need to also get my head around the changes in Joomla as well.

Peter

Hello.

I am new here and sorry my englisch is not so very good.
Today i have installed jUpgrade 1.2.2 when i open it with firebird i can do a check. When he is checking it, it crashd.
When i set out in config for checking so i will direct download joomla 1.7 i get a message " Error: zip file was not successfully downloaded "

I work with joomla 1.5.23 and i will update it for using "gantry" frameworks...

Pls what am i missing to upgrade my joomla ??

Jacob: Install redSHOP on your j1.5 VM site - use the redSHOP import from VM feature and then once the data is in redSHOP you can migrate to J1.7.1 with redSHOP

Peter: Curl is needed to download whats need for an automatic upgrade - Curl _can_ be abused but it hardly is if the security is ok and you keep your software updated - we have Curl support on all servers and we host more than 3500 business joomla websites.

Matias
Griese wrote:

When you first login to the new site (admin), you see nothing. Workaround: Logout and login.

You get this bug too? i compared the database to found what causes this but the only table that changed is j17_session... very strange

Question to the developers of jupgrade:

I've been surfing many forums to get a solution for problems with jUpgrade 1.2.2, also 1.2.1. Nowhere I could get an answer that solves the problems.

Many people reporting errors with Mootools, including myself. Now, my question to you is:

Why don't you leave out all this Mootools-Code and provide simple Code, that is able to work with any browser and does not serve errors without error messages - even with debug enabled.

Please reply!
Thanks.

I experience the same so now we are at least 2 screaming for help!

This doesn't work. When I click on Start Upgrade, nothing happen. Oh! Yeah! I've read FAQ section upgrade mootools plugin also.

yeah = I also have Joomla 1.5.14 with MooTools 1.1 (actually v1.2 gave the same result or even more JS errors) and tried to migrate it to the upper version and actually nothing happens = just errors in JS code... When I open the jUpgrade plugin = I see all pictures for all steps already below the Start button. And, of course, when I click on this button = nothing happens at all...
Reading all FAQs gives nothing, because the plugin doesn't work from the beginnging

I had J!1.5.23 + JCE + K2 2.5.4 + Kunena 1.7

After upgrade:

Back-end: J!1.7.1, no K2, no Kunena, no JCE in the components menu, but all 3 are listed in Extension Manager (with Id from 1000 to 1002)

Front page shows only 404 error:

"An error has occurred. The requested page cannot be found.

If difficulties persist, please contact the System Administrator of this site and report the error below.
#404 Component not found"

What's more strange J!1.5.23 in the original root works fine.

Where is the problem?

Please check the 3rd party extensions video in this url: redcomponent.com/jupgrade

There are an example of how to get K2 working.

Regards

Hope I am in the right forum for this question. I attempted 1.2.2 today for first time on a Windows IIS 7 64bit 2008 system. Mootools enabled and no problem but I get an error stating 407 the root directory is unwriteable when it is. The IUSR account has FULL CONTROL all subfolders inhereted same permissions while no other module, updater, etc. has any problem writing to directories within the root folder. Is even set the IIS_IUSR account to FULL CONTROL just to prove a point and nothing..same error. Is there another account outside of the primary user accounts that has to be enabled and granted FULL CONTROL that I am unaware of? Have not found answer to this in queries on this site for the last hour and I really need to get this resolved or find an updater that works for windows users. Thanks for your time in advance.

MR

So since I received no response I turned off the error checking in the jupgrade tools menu and guess what. It upgraded just fine despite the warning that the directory was unwriteable. Developers need to note that the jupgrade 1.2.2 release has a bug in it that allows it to give false error messages regarding directory writing in IIS 7. If anyone else has the same issue just turn of the first check box regarding error checking and just let it run. Thanks.