Use route parameters to match local tasks against routes

Created on 5 December 2013, almost 11 years ago
Updated 23 May 2023, over 1 year ago

Local tasks have a route_parameters definition property. As opposed to their route_name property, the parameters are not used for both matching and rendering, but only for rendering.

This effectively means that we can only show local tasks on all parameter values of a route. We can't show tasks only when a parameter has a specific value. Example:
*.routing.yml

foo.bar:
  path: /foo/{bar}

*.local_tasks.yml

foo.bar.123:
  route_name: foo.bar
  route_parameters:
    bar: 123
foo.bar.456:
  route_name: foo.bar
  route_parameters:
    bar: 456

The first local tasks should only be displayed when {bar} is 123, and the second only when it is 456.

✨ Feature request
Status

Closed: won't fix

Version

9.5

Component
Menu systemΒ  β†’

Last updated 1 day ago

Created by

πŸ‡¬πŸ‡§United Kingdom Xano Southampton

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.

  • πŸ‡ΊπŸ‡ΈUnited States Kristen Pol Santa Cruz, CA, USA

    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)" almost a year ago.

    Since there was no additional information provided since the issue was postponed last year, I'm marking the issue "Closed (won't fix)". If anyone can provide complete steps to reproduce the issue (starting from "Install Drupal core"), document those steps in the issue summary and set the issue status back to "Active" [or "Needs Work" if it has a patch, etc.].

    Thanks!

Production build 0.71.5 2024