Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Well,
Drupal 8 brought routes. These are great. The menu local task implementation now allows us to display independent tasks under a certain route / page. Which means that we're basically no longer bound to paths like we were with Drupal 7.
So in reality this can allow us to have entity view on front-end and any other task(edit, delete..) on the back-end...for example:
node/5 <- view task
admin/content/node/5/edit <- edit task
admin/manage/content/node/5/delete <- delete taskThis of course does not happen in the core but if you're making a complex module or distribution(my case) you can end up with such structure(which in my opinion is how it should be in the core anyway..why put node editing or deletion on the front-end??).
Now the issue I have is that once I leave the 'view' page to, lets say, 'edit' task then I immediately lose the local tasks since the 'parent_id' was obviously set to the 'view' task and therefore when I'm no longer on the 'view' task's uri there is no reason for the tasks to be displayed.
With D7 I would not be able to make such local tasks structure, but now it's possible and therefore I think there needs to be added some sort of additional route parameter, like 'task_group' which would allow us to set the group to the local task definition and the local task would be visible on route that would utilize such group.
So far we have two options to display a local task: via base_route key or via parent_id key. I am proposing that we add a third option and that would be the 'task_group' key.
So what now looks like this:
mymodule.myentity.view_tab:
route_name: mymodule.myentity.view
base_route: mymodule.myentity.view
title: 'View'
mymodule.myentity.edit_tab:
route_name: mymodule.myentity.edit
parent_id: mymodule.myentity.view_tab
title: 'Edit'
mymodule.myentity.delete_tab:
route_name: mymodule.myentity.delete
parent_id: mymodule.myentity.view_tab
title: 'Delete'
would simply look like this(+ the task_group with 'myentity' value in route definitions):
mymodule.myentity.view_tab:
route_name: mymodule.myentity.view
task_group: myentity
title: 'View'
mymodule.myentity.edit_tab:
route_name: mymodule.myentity.edit
task_group: myentity
title: 'Edit'
mymodule.myentity.delete_tab:
route_name: mymodule.myentity.delete
task_group: myentity
title: 'Delete'
Comments
Comment #1
Anonymous (not verified) CreditAttribution: Anonymous commentedI had a look at \Drupal\Core\Menu\LocalTaskManager::getLocalTasksForRoute() and it's obvious this won' be possible with just a simple patch. The thing is that there would have to be duplicates of the original local tasks since each task just basically works only with route. If it does not utilize base_route but parent_id the base_route is retrieved form the parent_id local task anyway.
Comment #2
dawehnerI don't get that parent_id is used for local tasks deeper than just one level. For the parent level tasks you always use base_route, which seems to be the thing you described.
Comment #3
dawehnerLocal tasks should be part of the menu system.