Contextual link group names are not predictable

Created on 13 November 2013, about 11 years ago
Updated 12 August 2024, 5 months ago

Problem/Motivation

Following #2084463: Convert contextual links to a plugin system similar to local tasks/actions β†’ , contextual links cannot be attached to path parents anymore. They are collected based on group names which come from build array keys. So to attach contextual links to existing groups, you need to know this group name. However group names are somewhat arbitrary, eg. blocks have 'block', menu have 'menu', but views have 'views_ui_edit'.

Proposed resolution

Figure out how to make the names predictable to allow for automation in extending links. At least make the config entity based links use the module name.

Remaining tasks

  • Figure out what to do.
  • Build it.
  • Get it reviewed.
  • Test.
  • Commit.

User interface changes

None.

API changes

Maybe. At least some existing group names will change.

Related Issues

#2084463: Convert contextual links to a plugin system similar to local tasks/actions β†’

πŸ› Bug report
Status

Closed: outdated

Version

11.0 πŸ”₯

Component
ContextualΒ  β†’

Last updated 3 months ago

Created by

πŸ‡­πŸ‡ΊHungary GΓ‘bor Hojtsy Hungary

Live updates comments and jobs are added and updated live.
  • D8MI

    (Drupal 8 Multilingual Initiative) is the tag used by the multilingual initiative to mark core issues (and some contributed module issues). For versions other than Drupal 8, use the i18n (Internationalization) tag on issues which involve or affect multilingual / multinational support. That is preferred over Translation.

  • VDC

    Related to the Views in Drupal Core initiative.

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.

  • πŸ‡ΊπŸ‡ΈUnited States smustgrave

    @neclimdul should this be moved back to NW?

  • Status changed to Closed: outdated 5 months ago
  • πŸ‡¦πŸ‡ΊAustralia acbramley

    As part of the Bug Smash Initiative, we are triaging issues that are marked "Postponed (maintainer needs more info)". This issue was marked "Postponed (maintainer needs more info)" more than 2 year ago.

    Since we need more information to move forward with this issue, I am closing it.

    If anyone feels strongly that this bug needs to be fixed, feel free to reopen this ticket with an MR of the changes required including tests if possible :)

Production build 0.71.5 2024