Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
As described at https://www.drupal.org/project/prlp/issues/2572237 (that one is for D7), there are some cases when certain user roles are allowed to access/manage some site administration sections. But that's not the case for some "more sensitive" places, like this one.
Said that, I think it's better to have separated permissions. That way we can to decide if mentioned roles are able to access settings or not.
Patch in the way...
Comment | File | Size | Author |
---|---|---|---|
#5 | prlp-split_permissions-3126080-5.patch | 1.24 KB | loze |
#2 | prlp-split_permissions-3126080-2.patch | 707 bytes | waspper |
Comments
Comment #2
waspper CreditAttribution: waspper as a volunteer and at Skilld commentedAttaching patch...
Comment #3
waspper CreditAttribution: waspper as a volunteer and at Skilld commentedComment #4
Jitesh Doshi CreditAttribution: Jitesh Doshi at SpinSpire commentedMaking this change will break existing installations. Can you please include a migration that assigns this new permission to all existing users that have the "administer users" permission?
Comment #5
loze CreditAttribution: loze commentedHere's a patch that adds an update hook.
Thanks.
Comment #6
qzmenkoThanks, new permission works.
Comment #7
flocondetoileNot sure patch #2 will break anything. Anyway, site administrators still get access to PRLP settings.
And in my case, this patch is useful because I don't want users with the permission "administer users" to be able to manage PRLP Settings. And in my case, when i give the permission "adminsiter users" I didn't want to give them the permision to manage PRLP settings. So In my mind patch #2 should be committed, not #5 which ensure that an unwanted situation is still present.
Otherwise RTBC++ (#2 or #5)