This issue is split off from #682000: Remove the default limit of 7 shortcuts per shortcut set, but Drupal 8 only.
The proposal that was suggested was to completely remove all code related to limiting the number of shortcuts per shortcut set via the UI (whereas the patch in the other issue merely sets the default to have no limit, in a way that is intended for D7 backport, but still allows limits to be imposed by setting a variable).
There are some pros and cons to this; read up on the above issue for more details.
One thing that I know someone will bring up so I'll bring it up now myself; if we no longer enforce a limit, do we need to have the concept of enabled/disabled shortcuts anymore? (It's a related question, but perhaps it can it be deferred to a separate issue?)
Comment | File | Size | Author |
---|---|---|---|
#12 | 1304486-12.patch | 14.02 KB | swentel |
#9 | core-1304486-9.patch | 14.17 KB | nod_ |
#3 | core-1304486-3.patch | 13.85 KB | nod_ |
#2 | 1304486-2.patch | 14.07 KB | swentel |
Comments
Comment #1
Bojhan CreditAttribution: Bojhan commentedWe shouldn't, the whole enabled/disabled shortcuts is freaking confusing anyway.
Comment #2
swentel CreditAttribution: swentel commentedYes, let's kill this!
Comment #3
nod_reroll. Works fine for me let's see what testbot says.
Makes me happy to see so much JS removed :)
Comment #4
swentel CreditAttribution: swentel commentedLet's do this! :)
Comment #5
Dries CreditAttribution: Dries commented#3: core-1304486-3.patch queued for re-testing.
Comment #6
Dries CreditAttribution: Dries commentedI'm asking for a re-test because it did not seem to apply locally.
Comment #8
webchickProbably needs a re-roll due to #1684866: JSHint shortcut.
Comment #9
nod_reroll
Comment #10
swentel CreditAttribution: swentel commentedApplies cleanly now
Comment #11
Dries CreditAttribution: Dries commentedThanks for the re-roll. Committed to 8.x. Thanks.
Comment #12
swentel CreditAttribution: swentel commentedHere's the D7 version
Comment #13
David_Rothstein CreditAttribution: David_Rothstein commentedThis needs some kind of an upgrade path - otherwise your disabled shortcuts will be listed in the UI but with no way to reenable them (except by deleting and readding). And it's confusing too, since they show up on the admin screens but there's no indication they're disabled.
Comment #14
David_Rothstein CreditAttribution: David_Rothstein commentedI also don't see how this patch can ever be backported to Drupal 7? It makes major UI changes, changes function signatures, removes other functions, etc...
Comment #15
David_Rothstein CreditAttribution: David_Rothstein commentedhttp://drupal.org/node/1358140#comment-6320784 identifies some out-of-date documentation that was introduced here also.
Comment #16
xmacinfoA possible duplicate with a patch is here #682000: Remove the default limit of 7 shortcuts per shortcut set for Drupal 7.
Please note that we do not need to make any changes to add more than 7 shortcuts. By clicking on “display line weight” link on the shortcut page, you can add as many shortcuts as you like. No need to disable JavaScript or apply a patch to Drupal.
I am leaving version and priority as is for this issue, since the focus is to properly remove the limits in D8.
Comment #17
andypostI think better to convert a shortcut set to ConfigEntity and using EntityNG provide a ability to store entity references to new menu-items see #916388: Convert menu links into entities
About upgrade path: suppose we just need to implement a block setting to limit a number of links to display. No idea for now how to make this but having to make this setting per user or role #1122816: Assign shortcut set to role
EDIT filed #1811640: Convert shortcuts into configuration
Comment #18
webchickI'm not sure about removing this setting. Seems it's even more important in the world of mobile stuff? When we did usability testing on the mobile toolbar patch, it was noted that "Almost all participants (5 of 6 participants) had trouble noticing the "Edit shortcut" and thought need a little more visual emphasis. This is an important one because shortcuts were very important to all of the participants."
If anything, we probably want to make it configurable per breakpoint once #1734642: Move breakpoint module into core hits.
Comment #19
andypostHaving shortcut sets as configurables #1497380: Convert shortcut sets to ConfigEntity allows us to store additional setting per set (number of items of breakpoints)
Comment #19.0
andypostSmall clarification
Comment #20
catchNo longer needs an upgrade path. Please open a new issue for follow-up.
Comment #22
David_Rothstein CreditAttribution: David_Rothstein commentedFollowup was in #1777392: $limit parameter removed from shortcut_admin_add_link, but still in documentation and is no longer relevant.
I'm sure it needs a D7-to-D8 migration path in theory, but let's leave that to the aether.