Sticky J! 1.7.3 + CB 1.7.1 + K 1.7.1: After login as administrator from forum login, not all menu items shown in Kunena menu

I have already done that. I have not received any feedback on this yet.

Feedback I've received suggests that there is a bug here. We're looking into it now. I don't know any more at the moment.

Looks to be something in J! 1.7.3. I have not reproduced the issue on J! 1.5.25. Has anyone else seen this issue in J! 1.5.25?

*** Topic moved ***

Hello,

We have had a long discussion and testing period tonight with this.

And have concluded there is some thing Community Builder Login does, which is more than just their login as Kunena uses Community Builder's login to login..

Until we can provide a fix we suggest using the following workaround:

1. Disable login integration completely in Kunena
2. Create a new Community Builder Login Module
3. Set the new Login Module to horizontal
4. Make the Login Module appear in the Breadcrumbs position(Or any above / below the forum)
5. Make sure the module is show on the forum pages.

Regards
Tony

*** Topic split by moderator and merged with different topic ***

Okay So here is the problem, [strike]ignore what I said earlier[/strike].

I login with my SuperAmin account or my test account and I cannot see any of the Kunena menu options besides the ones that are available to the general public.

Moderator comment: see Specific Forums For Specific People! for this user's configuration report.

This is a known problem that has been reported to the Joomlapolis team. Early indications are that there is a defect in J! 1.7.3 that does not properly handle ACL permission setting (or it may require a simple switch setting change) but we don't know much more than that at this stage.

Tony's advice in the message before yours contains some good suggestions. We're still working on the issue and this topic has been stickied to draw attention to the matter.

As far as we can tell, the problem only affects users of J! 1.7.3, CB 1.7.1, K 1.7.1 where users login via the forum as an administrator. There is a problem with J! 1.7.3 that we're waiting to be fixed in J! 2.5. This is the latest information that we have.