Closed (fixed)
Project:
Config Pages
Version:
8.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
7 May 2025 at 15:47 UTC
Updated:
19 Sep 2025 at 11:49 UTC
Jump to comment: Most recent
Comments
Comment #3
d.fisher commentedI've added a MR for this. Here's the patch.
https://git.drupalcode.org/project/config_pages/-/merge_requests/45.patch
After digging in to the code I can see that 'administer config_pages types' permission does add some security around clients accidentally clicking the button, but it might be nicer to have this broken out into its own permission. Let me know what you think either way!
Comment #4
d.fisher commentedAny thoughts on this?
Comment #5
bhogue commentedI can confirm that this new permission works as intended.
Comment #8
shumer commentedComment #9
shumer commentedComment #10
d.fisher commentedOh cool! I didn't realise this got merged! Thanks.
Comment #11
d.fisher commentedHi any chance the contribution record could be updated for this issue? I'm not sure how the new system works but when I go here: https://new.drupal.org/contribution-record/10001616 it looks like none of the names have been checked? Thank you.
Comment #13
shumer commentedHave no idea how the new system works :)
Just tried to mark check boxes there and save the changes.
Comment #14
d.fisher commentedOh yes that worked. I've been looking into the changes as I maintain a few modules and need to make sure I understand how this new system works. It looks similar to before - but has just moved to a new page instead of being attached directly to the drupal.org issue page as the intention is to migrate issues away from drupal.org and over to gitlab issues instead. Many thanks for looking into it! I appreciate it.