Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
It's a standard feature, 99% of sites run it (those that don't use apache solr or xapian - most of which depend on search module anyway), so we should enable it by default.
Comment | File | Size | Author |
---|---|---|---|
enable_search.patch | 662 bytes | catch | |
Comments
Comment #1
Damien Tournoud CreditAttribution: Damien Tournoud commentedI support that. We need to refactor the Search API to be able to switch more easily to solr or xapian, but that's another issue, one we can probably tackle in the timeframe we have.
Comment #2
Damien Tournoud CreditAttribution: Damien Tournoud commentedThis is blocking #497804: [meta] Search entities (nodes, terms, etc.) within the administrative interface, so tagging as d7ux.
Comment #3
webchickHm. I've committed this. But I'll strongly warn that unless there is follow-up work done, this is going to be every new user's first steps in Drupal:
Step 1: Create some content.
Step 2: Search for it.
Step 3: Post a support request on the forums, since the search didn't find anything.
Since there is no step 0: Set up cron.
If that continues to be the default UX, we'll have to back this out before code freeze.
Comment #4
webchickWow. Who knew that such a sweet, harmless looking patch could cause a failure in our test suite? ;) http://testing.drupal.org/pifr/file/1/8853
I had to roll this back.
Comment #5
webchickOk. Now that #504016: Remove stupid assertion is in, trying this patch again. May we all pray that testing bot has mercy on our soul. ;)