Add a hook to allow query tags to be altered, and use it for taxonomy term access query tags

Created on 17 November 2016, almost 9 years ago

Updated 28 August 2025, 18 days ago

This is a followup to the security release at https://www.drupal.org/SA-CORE-2016-005 → .

In that release we introduced some hardcoded functionality into the database layer to ensure that queries tagged with either 'term_access' or 'taxonomy_term_access' would be treated as having both tags for the purposes of query alteration. See http://cgit.drupalcode.org/drupal/diff/core/lib/Drupal/Core/Database/Que... and http://cgit.drupalcode.org/drupal/diff/includes/database/select.inc?id=c....

This issue is to discuss whether that can be cleaned up, for example by adding a new hook to the database API that allows query tags to be altered, and then having the taxonomy module implement that hook.

To discuss: Would this new hook actually be useful for any other purpose?

✨ Feature request

Status

Postponed: needs info

Version

11.0 🔥

Component

database system

Created by

🇺🇸United States David_Rothstein

Live updates comments and jobs are added and updated live.

Needs backport to D7
After being applied to the 8.x branch, it should be considered for backport to the 7.x branch. Note: This tag should generally remain even after the backport has been written, approved, and committed.

stale-issue-cleanup
To track issues in the developing policy for closing stale issues, [Policy, no patch] closing older issues

Incomplete comments

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Comment 18 days ago →
🇺🇸United States smustgrave
Thank you for sharing your idea for improving Drupal.

We are working to decide if this proposal meets the Criteria for evaluating proposed changes. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or there is no community support. Your thoughts on this will allow a decision to be made.

Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024