Question CB Integration - Profile tab says "You are not authorized to view this page!"

Yeah im getting these errors aswell.

Only when loggin in through kunena though. When using the cb login module all works fine...

Yes, gazm, we understand the problem. The issue involves using the login form in Kunena as long as you have Kunena integrated to use the Community Builder login function. As a workaround, you can set the Kunena integration option to use the Joomla login function instead. There is a downside: if users try to register at your site from the Kunena forum, they will also be offered the Joomla registration function (if it's enabled) using the option I've just mentioned. We understand the problem and I have referred the matter to the project team for a resolution of the issue.

Your problem, gazm, can also be addressed by using the fix given by Matias in msg #18 in this topic. This removes the message "The profile page is not available for guests".

I still have to further investigate the main subject of this topic, namely, "Profile tab says 'You are not authorized to view this page!'"

I can probably fix the other issues now that we are able to reproduce them, but we still need to be able to reproduce the first issue (from the title)..

I believe that above error comes from Joomla, so it has something to do with profile menu item..

Any ideas how to get that error? How many of you are seeing it? Maybe we will find something in common..

Matias, use the login I've provided to sozzled. Try to create a new topic and you will get that message right away.

Matias - I was the one who originally posted the issue. I've worked around it for now by changing my Kunena Profile Menu tab to the type CB User Profile. You can subscribe at " www.espiritusanto.cc " and I'll accept you in if you want to try and debug it. Let me know and I'll set the Kunena Profile tab back to it's normal setting.

Brian

@vau3677: Your issue is different. There's a bug in Kunena 1.6.4 with locked categories. Unlock those and posting should work again. The issue has been fixed into K1.6.5.