Problem/Motivation

Create a view, such as nodes associated with a group or taxonomy term, and add validation on the bundle, as well as a local task.

On entities with a different bundle, the local task still shows up even though the view itself with be a 404 or 403 depending on the argument configuration. This is because argument validation isn't taken into account for view access.

Proposed resolution

Consider adding support for #2858776: Make defining bundle-specific routes easier as a view access handler, so that the route can be made bundle-specific too.

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

Comments

catch created an issue. See original summary.

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.

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.

aleix’s picture

aleix
Primary language Catalan
Location Terrassa
commented

While not there, here it is a workaround: https://peacocksoftware.com/blog/drupal-89-views-tab-only-certain-node-t...

aleix’s picture

aleix
Primary language Catalan
Location Terrassa
commented

Looking a little more on how can I do it, I was trying to get the same behavior as in drupal 7 where the tab is shown depending on how the validation is done in argument contextual filter( similar as what happens in https://www.drupal.org/project/views/issues/2345763 ).
The workaround in previous comment is too specific and customized for a specific route. A more generic way of doing, could be what is done in this experimental module: https://gitlab.com/communia/views_validate_tabs . It adds a new access plugin extending permission but using the validator defined in contextual filter.

scotwith1t’s picture

scotwith1t
Location Birmingham, AL
commented

Nice one, thanks for the custom module. Simple enough and certainly contrib-worthy until this is addressed in core. In our case, the Event node type has a tab for admins to see registrations, which of course don't apply to other content types. Thanks again, @aleix.

catch’s picture

catch
he/him
Primary language English
commented
Status: Active » Closed (duplicate)
Related issues: +#2778345: Views argument validators aren't taken into account on access checks - local task point to 404

Duplicate of #2778345: Views argument validators aren't taken into account on access checks - local task point to 404