Question [Merged topic]K 1.7.1 and Jomsocial Activity Stream

It would be much better if you where given the choice when Kunena should publish new threads in the Jomsocial activity stream, maybe you could choose for which Kunena categories an entry should be published in the JS activity stream.

And in the Kunena ACL I think that I should be able too see all the Joomla user groups and then be able to choose exactly which user groups this categorie is visible to. I just click on them and I should be able to click on as many as I want.

But primarly it is this thing that Kunena doesn´t include child groups when I choose a Joomla access level. And even if I choose all the Joomla user groups in my Joomla access level Kunena still doesn´t post to the JS activity stream.

Yes, at the time I changed the code, I didn't fully understand how Joomla ACL works. Now I know how to do it better. It still won't be perfect. The perfect way would be doing what you suggest, but that's not going to happen in the near future, I'm afraid.

Matias wrote: Yes, at the time I changed the code, I didn't fully understand how Joomla ACL works. Now I know how to do it better. It still won't be perfect. The perfect way would be doing what you suggest, but that's not going to happen in the near future, I'm afraid.

Not even in Kunena 2.0?

I assume this discussion is based on folks who use J1.7, we are still on J1.5 and have the same problem (no Kunena activities since upgrade while other activies work as before). I could not find other users with the J1.5 and K1.7.1 problem - can you give me some advice on what to check for?

Christian

But atleast give us the optison to turn on or off if an JS activity should be created for threads in private categories.

Hi everybody,

I have the same problem with Joomla 1.7 and Kunena 1.7.1 (no probleme with Kunena 1.7.0) and I change access level by group user, that's solved the problem and my Kunena categories don't dissapeared for my registered members.

Thanks erkan

EDIT : When I use "public only" with option "no" for child item, that's works too. Strange...