I was tasked to clone a user role for a site the other day. Here are the options one has:
- Execute a db query -> not user-friendly
- Create a new role, then manually set the same permissions as another role -> endless scrolling and clicking on checkboxes ; becomes worse the more contrib with additional permissions a site has (or many content types, since they also add multiple permissions); becomes even worse if the role you want to clone has many permissions assigned to it (might also become a victim of https://www.drupal.org/project/drupal/issues/1203766 if the site has many roles)
- https://www.drupal.org/project/duplicate_role (have not actually tested it) -> not ported to Backdrop
We should have a "Clone role" action.
GitHub Issue #:
3813
Recent comments
I second this-- I have a module in contrib now that I just marked as "deprecated", and I removed its sole alpha release (because a fix in Core made it obsolete). Just plain deleting the module...
Weekly Meetings July 23rd 2026
If there's some time left in the dev meeting - although it might rather be a topic for the PMC: We have nice documentation and procedures, how to provide projects in backdrop-contrib space...
Weekly Meetings July 23rd 2026
The need for a clear AI policy is growing. Please can this be a priority.
Weekly Meetings July 23rd 2026