Question Kunena Discuss 1.6.4 + K 1.6.5 + J! 1.7.0 + Jomsocial Activity Stream

I successfully installed the Discuss Plugin v1.6.4 on J! 1.7.0. That's not my issue. The only issue I'm having with it now is JomSocial Activity Stream integration. When Activity Notification is set to "Auto" or "JomSocial", the page fails to load because K 1.6.5 keeps creating topics. When Activity Notification is set to "None" the plugin works fine, it just doesn't post to the JomSocial Activity Stream.

I have the same problem. Right now I have K1.7 and J1.7 with Kunena Discuss 1.7 installed.

I've lost all day :pinch: (after installing Jomsocial) trying to fix the problem with Kunena Discuss & Jomsocial working together. With no luck. The best results at this moment are as mentioned above by Prophat247 - to switch Activity Notification to "None" in Kunena Configuration "Integrity" tab.

If you don't do this - everything will mess up, creating hundreds of the same posts, and giving you a fatal error when trying to post/duplicate new article.

So my choices were: disable Kunena Discuss or switch Activity Notification to "None".
I preferred the second option. not 100% functional activity stream in Jomsocial is small price to pay, comparing to what Kunena Discuss have to offer, but I Subscribe this topic, and wait patiently for a someone with bigger knowledge/luck/time etc.

..edited..
after a while...
WAIT! I see the light! :woohoo:
- leave all as it is (and it is like above)
- install JomSocial Application "plg_kunena.zip"
- enable it
- in its configuration set "Core Application" to "Yes" (default is "No")

NOW IT WORKS!
in JomSocial profil page "My kunena updates" began to show!
But there is ONE thing:

Fatal error: Call to a member function reorder() on a non-object in ...\administrator\components\com_content\models\article.php on line 323

when you trying to post/duplicate new article. Article will be created or duplicated but you will get this error. It's happing in the backend. At frontend error does not appear.

..edited..
after another while...

Here: Fatal error backend article new, edit is help by Matias with this particular issue!