Merge shortcut per role module in core shortcut 8.x

Created on 13 October 2012, about 12 years ago
Updated 12 September 2023, over 1 year ago

There's a lot of requests in core issue Assign shortcut set to role Active

Module is new but have a 500 users

Suppose module just needs to
- make a d8 branch
- merge d8 branch with core shortcut, fix core tests and add a few new
- provide a patch to Assign shortcut set to role Active

Feature request
Status

Active

Version

2.0

Component

Code

Created by

🇫🇷France andypost

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇪🇨Ecuador jwilson3

    I wouldn't be opposed to it, per se. But I've left a message on the upstream issue some time ago:

    Addressing #25 Assign shortcut set to role Active , the Shortcut Per Role module was ported to Drupal 8 and has now been updated for compatibility with Drupal 9. However, this module has a serious limitation which, IMHO, excludes it from consideration for inclusion into Drupal core until it can be resolved properly in contrib.

    The module works well when each user is generally assigned a single role like "administrator", "content editor", "moderator", "user admin", etc. However this module become complicated and less useful if your roles and permissions model is such that each user has multiple roles. This is the strategy that was adopted with Acquia's lightning, where each content type on the site had a "Type creator" and "Type editor" role. This gives fine-grain control for large teams, but makes building competing shortcut sets per role a very challenging problem. The module's behaviour is currently to inherit the shortcut set assigned to the highest weighted role, but at least one person found this behavior annoying and would rather combine sets #3145202: Option to combine shortcut sets for users with multiple roles .

    I was granted maintainership of the module to shepherd the Drupal 9 and 10 compatibility, and don't really have long term plans to figure out this hard problem on my own, but I'm open to ideas on how to approach providing an option to merging sets.

Production build 0.71.5 2024