You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 27, 2024. It is now read-only.
Here are steps :
1 Kunena is integrated. (registering and loging through Kunena Login module) (ok)
2 sliComments - Options - Permissions - Public is set do Denied (ok)
3 sliComments - Options - Permissions - Registered is set do Allow (ok)
4 Registered user is loged to site through Kunena Login module (ok)
5 Registered user cannot post comment and see "Log-in to post a comment!" (fail)
The text was updated successfully, but these errors were encountered:
This has nothing to do with kunena, its because of the joomla ACL. if you set the permission to denied it means that users in this group and user in descendants groups cannot perform the given action.
e.g.
-public - inherited (implicit deny) -> cannot perform the action
--registered - allowed -> can perform the action
...
-public - denied (explicit deny) -> cannot perform the action
--registered - allowed -> cannot perform the action
I must admit that this message "Log-in to post a comment!" is incorrect and misleading. but I didn't find anything better and since most people would not deny a specific usergroup other than "public" to post comments it seems more appropriate, and besides that visitors normally have no idea how acl, usergroups and that stuff works so "Log-in to post a comment!" seems more user friendly.
Here are steps :
1 Kunena is integrated. (registering and loging through Kunena Login module) (ok)
2 sliComments - Options - Permissions - Public is set do Denied (ok)
3 sliComments - Options - Permissions - Registered is set do Allow (ok)
4 Registered user is loged to site through Kunena Login module (ok)
5 Registered user cannot post comment and see "Log-in to post a comment!" (fail)
The text was updated successfully, but these errors were encountered: