Search Settings (d7_search_settings) migration is ignored if any of the variables it would use is missing.

Created on 10 February 2022, over 3 years ago
Updated 24 May 2025, 4 months ago

Problem/Motivation

Drupal core's d7_search_settings is ignored if any of the variables it would use is missing. In #3151993: Search settings migration (d7_search_settings) assumes that the search_default_module variable is always set , the original report was about that this migration was assuming that the search_default_module was always set. Unfortunately, the actually committed implementation is very wrong.

  • If we have only the minimum_word_size being set in the source database, that still should be migrated to Drupal 9.
  • If we have only the search_default_module variable in the source database, then the migration is still should be executed.......and so on.

Steps to reproduce

1. Pick one of these variables in the Drupal 7 source database :

  • minimum_word_size
  • overlap_cjk
  • search_cron_limit
  • search_tag_weights
  • search_and_or_limit
  • search_default_module

2. Remove all other values.
3. Execute the migrations in Site Settings (d7_search_settings should be there).

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

🐛 Bug report
Status

Postponed

Version

11.0 🔥

Component

migration system

Created by

🇮🇳India omkar.podey

Live updates comments and jobs are added and updated live.
  • Needs tests

    The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.

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