[#5223] 2.0.7 update Fails

If possible clone your live site so you're not affecting the original and see if it works fine on your live site server as this could just be a local issue.

krileon wrote: If possible clone your live site so you're not affecting the original and see if it works fine on your live site server as this could just be a local issue.

Actually, that is what I have done. Both Localhost and the live Testsite are clones of the live site.
This migration is extremely well planned as there is no room for mistakes. .I have created an 85-step migration plan that I am using first on localhost, then testsite, last livesite, to be sure to do exactly the same thing on all 3, and I expect the clones to migrate properly before migrationg the live site.

Did you test and reproduce the error with earlier CB versions too? For example 2.0.4 as Nick successfully used in his tutorial?
I have only tried. 2.0.7.

Actually, that is what I have done. Both Localhost and the live Testsite are clones of the live site.
This migration is extremely well planned as there is no room for mistakes. .I have created an 85-step migration plan that I am using first on localhost, then testsite, last livesite, to be sure to do exactly the same thing on all 3, and I expect the clones to migrate properly before migrationg the live site.

I mean did you clone your site into a sub directory or sub domain on your live server and test there? This would completely rule out server environment being a possible cause. If you've a live test site where we can investigate further that would be of great help and if you do then please PM backend super administrator login credentials as well as FTP credentials then will take a look.

Did you test and reproduce the error with earlier CB versions too? For example 2.0.4 as Nick successfully used in his tutorial?

No, some earlier releases did have migration issues, but we've since fixed those. I wasn't able to confirm 1.9.1 to 2.0.7 migration issues in my tests.

Kyle, you have got a PM.

Have reviewed your test install and your issue is caused by K2s CB integration. It's loading CBs API in within its Joomla system plugin, which it's doing very early before CB 2.x install can properly load it in as needed. To fix this you need to navigate to Components > K2 > Parameters > Advanced then set "Community Builder integration for avatar, user names and user pages" to "No". Now you can upgrade safely.

Always one more thing to learn.
I had totally forgotten about that one.

Thansk a lot for your help!