[MGNLCMNT-4] Cannot "validate" comment Created: 23/Mar/09  Updated: 16/Mar/12  Resolved: 03/Dec/10

Status: Closed
Project: Commenting (closed)
Component/s: None
Affects Version/s: None
Fix Version/s: 1.2

Type: Improvement Priority: Major
Reporter: Boris Kraft Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
caused by MGNLCMNT-17 Assign roles for commenting to anonym... Closed
caused by MGNLFORUM-118 Grant all perms to superuser on install Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

With a default installation of STK 1.1 snapshot I get the following message when I try to validate a comment.

"User not allowed to [unknown permission] path [/pagecomments/a-large-article/2009-03-23-11-54-0]"

a) why?
b) what do I need to do to fix it?



 Comments   
Comment by Boris Kraft [ 23/Mar/09 ]

added some forum roles to superuser, no it works.

Comment by Jan Haderka [ 23/Mar/09 ]

It is not a bug per se. You need proper permissions in order to be able to moderate comments. Superuser is not a forum administrator nor the forum moderator by default (Similarly to superuser not being member of publishers group by default prior 3.6.5).
I presume we can make superuser member of the moderator and administrator group for page commenting by default to lower the entry barrier for usage of the feature.

Comment by Boris Kraft [ 23/Mar/09 ]

we could make the message a bit more descriptive and tell the user which roles he needs? The [unknown permission] bit is not exactly end user friendly.

Comment by Magnolia International [ 03/Dec/10 ]

the [unknown permission]}} bit comes from a limitation of info.magnolia.cms.security.PermissionImpl, which wasn't really written so as to have custom permission types like the forum introduced (e.g.. "moderation")

MGNLFORUM-118 hides the problem by grant all forum permissions to superuser on installation.

Generated at Mon Feb 12 00:02:14 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.