custom_search_query_alter() is too agressive

Created on 25 April 2014, over 11 years ago
Updated 9 May 2025, 5 months ago

custom_search_query_alter() is a little too aggressive in it actions. It checks for three things, the node_access tag, the pager tag, and whether a query is being run against search_index.

This works well for core search, but if another module want to use data from search_index, there is no way to get it. For example, I have site where I am excluding a content type with Custom Search, but would like to have a custom search that relies on search_index and search_dataset run on one of the excluded types.

πŸ› Bug report
Status

Fixed

Version

1.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States mpdonadio Philadelphia/PA/USA (UTC-5)

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

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

Production build 0.71.5 2024