Problem/Motivation

Core search for Node content and Help Topics relies on the search index being complete and updated in order to return accurate results.

After enabling Search, users would probably expect searches to work. But in practice, it can take several (or many, depending on the number of nodes and search indexing settings) cron runs for the search index to be complete.

On #3087218: Help searches fail if site is not fully indexed, and users do not know why and #3194120: Need a way to say it's time to run cron we discussed forcing cron to run under various circumstances, such as when the search index was not yet complete and when modules/themes were installed. That didn't happen. Instead, for Help Search the solution seems to be to warn searching users if the help topic search index is not complete. Note that help searchers are are admin users, who might actually be able to do something about running cron, or at least would be expected to know who to contact with a higher level of permissions.

This issue is about what to do for node searches.

Steps to reproduce

Install the Node and Search modules, and create some content items. Try to search from (site url)/search. You will not see complete search results until after several cron runs.

Proposed resolution

Consider whether Node module should output a message when a search is performed if the index is incomplete. Maybe it should have a configurable threshold. For instance, on some sites they might not want to show users (who can't do anything about it) this message, but on others maybe they want to show it only if the site is less than 75% index-complete. Maybe the message should be configurable also?

Remaining tasks

Figure out what to do and make a patch.

User interface changes

If a user searches and gets no or incomplete results, they might at least know why.

API changes

Probably not.

Data model changes

TBD -- probably some configuration for the threshold and message?

Release notes snippet

Maybe?

Comments

jhodgdon created an issue. See original summary.

jhodgdon’s picture

jhodgdon
she/her
Primary language English
commented
Title: Set cron flag if search index is not complete » Node searches fail if index is not complete, and users do not know why
Issue summary: View changes
Related issues: +#3087218: Help searches fail if site is not fully indexed, and users do not know why

The parent issue #3194120: Need a way to say it's time to run cron will not be done, so I am retitling this to state the problem, and fixing up summary.

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.

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.

quietone’s picture

quietone commented
Status: Active » Postponed

The Search Module was approved for removal in #3476883: [Policy, no patch] Move Search module to contrib .

This is Postponed. The status is set according to two policies. The Remove a core extension and move it to a contributed project and the Extensions approved for removal policies.

The deprecation work is in #3565780: [meta] Tasks to deprecate the Search module and the removal work in #3565783: [meta] Tasks to remove the Search module.

Search will be moved to a contributed project before Drupal 12.0.0 is released.

quietone’s picture

quietone commented
Project: Drupal core » Search (from core)
Version: main » 1.0.0
Component: search.module » Code
Status: Postponed » Active
Issue tags: -Needs product manager review

The Search Module has moved from core to contrib,