Investigate effect of change to OG Role name [#1940150]

Comment #1

japerry

KVUO

CreditAttribution: japerry commented 12 March 2013 at 01:49

Assigned:

Unassigned

» japerry

Correct, the features depend on the named role. There are four features that need to be changed:

commons_polls
commons_posts
commons_q_a
commons_wikis

Its pretty trivial to update these permissions to reflect the new name. However, this is a little disturbing how OG manages role permissions, because if any sysadmin wants to change the name, it will cause the features to become overridden.

Fortunately, my testing has shown that the permissions still apply cleanly since we change the name at the end of the install process.

Should I roll a patch to update the features?

Log in or register to post comments

Comment #2

ezra-g CreditAttribution: ezra-g commented 12 March 2013 at 13:49

Issue tags:

-Commons 7.x-3.1 radar

Given issues left to address before the 3.1 release, I suggest we remove the update hook that implemented this change and followup on this issue for a future release.

As part of the followup, we can specifically list areas where this text appears and should be changed in the UI and investigate whether changing the role name from OG's default would have any effects on OG-contrib module compatibility.

Log in or register to post comments

Comment #3

ezra-g CreditAttribution: ezra-g commented 12 March 2013 at 13:49

Issue tags:

+Commons 7.x-3.1 radar

Given issues left to address before the 3.1 release, I suggest we remove the update hook that implemented this change and followup on this issue for a future release.

As part of the followup, we can specifically list areas where this text appears and should be changed in the UI and investigate whether changing the role name from OG's default would have any effects on OG-contrib module compatibility.