CB1.8.1 J2.5.7 K2.0.2 CB Integration error

Dear Support Team,

today we upgraded our J 2.5.6 site to 2.5.7
Also we upgraded Kunena 2.0.1 to 2.0.2

Our 2.5 site is an originally 1.5 to 2.5 migrated site.

Before the upgrade no issues - Kunena CB Integration plugin was on (Using pretty much all options) without issues.
After the upgrade Kunena works perfectly fine as long as the CB Integration plugin is off. The consequences of that are clear... :blink:

If the integration plugin is on - Kunena returns white pages only on opening existing threads or creating new ones.

Fixes tried so far:
- Cleared cache (server and client)
- Purged Extension cache
- checked the Versions of the DB with the check in extensions - no errors
- ran a repair optimize on the DB - no errors
- ran repair tools in CB and also in Kunena - no errors
- tried disabling single option of the integration plugin without success.

Maybe the wizards on duty have an idea what else to try?

Why I post it here is simple - the standalone Kunena works. It is just the integration plugin...

all the best,
thank you,
Matthias

how did you upgrade?

Hi Nick,

thank you for your message. I used the Joomla Updater in the main control panel "update available"...

I am currently restoring the site from backup and will do a local install test.

Matthias

herzenssache wrote: Hi Nick,

thank you for your message. I used the Joomla Updater in the main control panel "update available"...

I am currently restoring the site from backup and will do a local install test.

Matthias

No, how did you upgrade from Joomla 1.5 to Joomla 2.5?

Turn on Joomla debug - see if any relevant messages appear.

Thank you Nick,

I originally upgraded using the "Jupgrade" migration methode.
We did encounter "small" issues with regards to the "Read Private Message" bug ( redcomponent.com/forum/92-jupgrade/121603-ans404-error-a-qread-private-messageq ).
Other then that, it worked fine.

As the live site is back on the older version now I will try the test site asap and check what happens there. I will then post a debug log if available...

all the best,
Matthias