Issue

There appear to be many dependencies on the Solr Search Defaults submodule, which mean it cannot be installed on sites that have a non-standard Drupal configuration.

On an existing website, for example, I no longer have Comments enabled and I do not have an Article content type. Both of these things are now blocking the ability to install Solr Search Defaults. I receive errors such as

Field comment in content type article not found. Solr Search Defaults module could not be installed

Can confirm this occurs on a fresh install via simplytest.me. Do any of the following to cause an error that will prevent Solr Search Defaults module from being installed:

- remove any field from Article content type
- remove Article content type entirely
- uninstall Comment module

Is there a reason that Comment module needs to be installed for this to work?

Comments

endless_wander created an issue. See original summary.

endless_wander’s picture

Issue summary: View changes
endless_wander’s picture

Removing all references to the Article content type and Comments module, including deleting their yml files under config resulted in being able to install the Solr Search Defaults module on my site.

mkalkbrenner’s picture

Version: 4.2.7 » 4.x-dev

I added search_api_solr_defaults as counterpart to search_api_defaults.
But it should never be used in production systems. It is meant for evaluation only.

And it depends on and targets the standard installation profile which installs the article content type

Nevertheless some people just try to install it, because it "sounds good". I think we should either remove it or let it depend on the standard profile.

  • mkalkbrenner committed 1568d2b on 4.x
    Issue #3283191 by mkalkbrenner: Dependencies for Solr Search Defaults...
  • mkalkbrenner committed e5c3b3c on 4.x
    Issue #3283191 by mkalkbrenner: Dependencies for Solr Search Defaults...
mkalkbrenner’s picture

Status: Active » Fixed

The sub-module caused test failures with Drupal 9.4 and 10.0. So I decided to not invest more time in that sub-module and to remove it.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.