Allow hooks / API functions for controlling what is added to taxonomy_index table

Created on 25 June 2013, over 11 years ago

Updated 6 February 2025, 17 days ago

Hello, after doing some research it's not clear to me whether or not there's a substantial way to interact with the taxonomy_index table.

My thought is that modules that do field level permissions should be able to prevent some nodes from being placed in a term's index is some level of privacy is desired.

This could get a little tricky, since it is possible for a node to have references to the same term. My thought is that each should have a chance to alter the index - if there is a private reference, it would be supressed, and if there is a public field it would be allowed.

So here are three examples:
1) private reference - deny indexing
2) public reference - allow indexing
3) public reference and private reference - allow indexing (public would trump private).

This issue was generated while working on another one: https://drupal.org/node/2027941

Perhaps I've overlooked some way to do this through an API? I feel like this should be a capability of the taxonomy module, since a none-core module would have a difficult time determining whether a node/term should be indexed or not on its own.

✨ Feature request

Status

Postponed: needs info

Version

11.0 🔥

Component

taxonomy.module

Created by

🇺🇸United States molenick

Live updates comments and jobs are added and updated live.

stale-issue-cleanup

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 17 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