CBForums Plugin Error on Registration

Hello, I'm getting the following error on the page the pops up after completing the registration.

Warning: cbforums - syncUser SQL Error: in (WEBSITE)public_html/components/com_comprofiler/plugin/user/plug_cbforums/models/kunena20.php on line 850

I have checked the line 850:
trigger_error( CBTxt::T( 'FORUMS_SYNC_USER_ERROR', '[element] - syncUser SQL Error: [error]', array( '[element]' => $plugin->element, '[error]' => $exists->getError() ) ), E_USER_WARNING );

This is the same as this topic in the Profession Member Support area www.joomlapolis.com/forum/153-professional-member-support/240323-7411-cbforums-plugin-error-on-registration . I cannot post there as I don't have professional membership

In my case the Kunena fields we are trying to sync are Forum Order and Signature.

The error occurs on registration. Updating the user profile in CB results in correct synchronisation with Kunena.

This worked ok until about 6 to 8 weeks ago - since then I have updated both CB to version 2.3 and Kunena to 5.1.7.

I'm guessing something has changed in Kunena breaking CBs ability to synchronize those fields. I've confirmed Signature synchronizes fine. Gender errors. Forum Order may also be erroring and recommend try removing that from synchronizing. Will be reviewing all the synchronization fields when I get to the bug ticket to see which are broken exactly.

Thanks - I have just tested with only the Kunena signature and not forum order on my CB registration form and still get the same error.

The error doesn't occur on the CB Update Profile

What type of field is your CB field for forum signature? It should be text or textarea only. I'm not sure what more to suggest as I have not reviewed this bug any further yet. Does removing forum signature from synchronization resolve the issue?

Kyle

Both signature and forum order are defined as text fields in CB. If I remove both from registration then I get rid of the error. The fields are still on CB update profile and work ok there so I have a workaround

This all worked ok until sometime just before Christmas so as you suggest it seems Kuena have changed something as the CB module hasn’t changed

Regards
Dave