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.Ever since #1551302: Fix server tasks system got committed (more than one and a half years ago), it is illegal for a disabled search server to have indexes attached. It seems you've just reverted your feature after running the associated update.php hook, ending up with illegal configuration in your module.
This causes problems when trying to disable the module, at which point it will try to delete the index's data from Solr, even though the server and index have never been enabled, and the user likely doesn't have Solr installed – resulting in an exception. It will probably also cause smaller errors to pop up in normal use.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | 2533504-1--fix_search_index_feature.patch | 1.41 KB | drunken monkey |
Comments
Comment #1
drunken monkeyThe attached patch should fix this.
Comment #2
dsnopekAh, so it attaches it to the server when enabling! That's quite clever. :-) Thanks for taking the time to make a patch!
Comment #3
dsnopekNow that with this patch there's an extra step to enabling SOLR manually (ie. when it's not enabled at install), I think it might make sense to add a special button or admin form to enable SOLR, so that it's easier for users to do.
Comment #4
dsnopekI tested the patch and it works great!
I think I'm going to create a new issue for setting up an admin form to quickly enable SOLR manually so that we can get this one committed: #2534596: Admin form for quickly enabling and configuring SOLR search manually
So, committed! Thanks again. :-)
Comment #6
dsnopekFor some inexplicable reason, this patch is causing upgrade from Panopoly 1.15 or older to fail: #2534646: Update from Panopoly 1.15 or older fails with "Table 'drupal.search_api_task' doesn't exist"
Here's the test build:
https://travis-ci.org/panopoly/panopoly/builds/71267552