I was trying to create local menu tasks structure similar to this:

------- NODE ------------------------ USER ------------------------ TAXONOMY -----------

- PAGE | ARTICLE ---------- ROLE 1 | ROLE 2 ---------- VOCAB 1 | VOCAB 2

I am able to create Views for the primary tasks(node, user, taxonomy) and I am able to create seocndary tasks(page|node, role1|role2, vocab1|vocab2) BUT when I click on the primary task I no longer see the other primary tasks. If I click on NODE I don't see USER and TAXONOMY tasks but I see only PAGE and ARTICLE as primary tasks. So secondary tasks became primary tasks.

Comments

dawehner’s picture

Issue tags: +VD

Tagging. Thank you for reporting that issue! This is indeed kind of a missing feature.

Anonymous’s picture

I wanted to add non-views-generated local tasks to a Views page. I used the 'name' from route table in DB as 'base_route' for my local tasks but they still won't appear. I think this can be the same Views issue.

tim.plunkett’s picture

Issue tags: -VD +VDC

Ahem.

Anonymous’s picture

I even tried the value by which the local tasks are keyed in 'local_task_plugins:en' cache but still no success.

dawehner’s picture

We have to rethink whether we maybe should change the UI to better fit with the existing local task architecture. In that case adding a subtask would be also easier to achieve.

Anonymous’s picture

Personally I don't find the current UI that confusing. Yes, maybe the first time I wasn't sure if I'm doing it right(due to this issue) but now I think it's intuitive. You either create a local task or you create a default local taks and then you just define the "parent's" label and that's it.

manuel.adan’s picture

Status: Active » Closed (outdated)
casey’s picture

Version: 8.0-alpha7 » 8.7.x-dev
Status: Closed (outdated) » Active

This issue is still relevant. It's still not possible to create a view with a secondary level local task. The mentioned issue only is about default local tasks and also about automatically creating the parent task.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

liquidcms’s picture

I have a views page which i am trying to add as a secondary task to the Admin Content page. I am pretty sure you can't do this with the Views UI only. But even using code I can't seem to find the solution anywhere. I posted this: https://drupal.stackexchange.com/questions/314773/custom-links-task-for-... but still no answer.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

smustgrave’s picture

Status: Active » Postponed (maintainer needs more info)
mortona2k’s picture

Status: Postponed (maintainer needs more info) » Needs review

I believe this one is for secondary level tasks. The one you linked is about a bug where the parent task isn't created automatically when it should.

I don't see any mention of secondary level tasks in there.

I'd keep this open unless that's the problem causing this issue, which it may be.

smustgrave’s picture

Status: Needs review » Active

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.