[MGNLCMNT-17] Assign roles for commenting to anonymous and superuser by default Created: 25/Sep/09  Updated: 04/Nov/15  Resolved: 04/Nov/15

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

Type: Improvement Priority: Major
Reporter: Jan Haderka Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
is causing MGNLCMNT-4 Cannot "validate" comment Closed
dependency
depends upon MGNLFORUM-126 Add "global" roles, grant -user -mode... Closed
depends upon MGNLFORUM-118 Grant all perms to superuser on install Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

Currently no roles are assigned by commenting module. However at least for the most basic scenario, the anonymous user should get assigned forum-pagecommenting-user and superuser should get forum-pagecommenting-moderator and forum-pagecommenting-admin to make commenting features work out of the box.



 Comments   
Comment by Magnolia International [ 03/Dec/10 ]

Now that commenting-forums are created "on the fly" (MGNLCMNT-20 MGNLCMNT-34), this could be an option of the commenting module (automatically grant new commenting-forum usage role to anonymous).

As for superuser, the forum module could have 3 simple roles that grant -user -moderator and -admin ACLs for all forums. (and thus all we'd need is for the forum module to grant this forum.ALL.admin role to superuser)

Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

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