Install
Works with Drupal: 8.xUsing Composer to manage Drupal site dependencies
Alternative installation files
Release notes
This is the sixth maintenance release of Search API Solr Search 8.x-2.x.
Important: You need to generate and deploy your Solr config files if you update from any any version before 8.x-2.5!
Important: You might need to adjust the solrcore.properties
file to your needs. If you get errors about missing classes you should adjust the solr.install.dir
.
Solr 6 and 7, nothing else!
The minimum supported Solr version is 6.4. But due to security issues it's highly recommended that you use at least Solr 6.6.2!
If you use Solr 6.5.x you have to be aware that there's a known issue within Solr itself that always leads to zero results in combination with search_api_autocomplete: #2869529: Autocomplete (and spell checking) is broken on Solr 6.5.x, Solr 6.6 will solve the issue.
Since this bug is fixed in Solr 6.6.0 we declare Solr 6.5.x as unsupported!
As you can see at http://lucene.apache.org/solr/community.html we're in sync with the Solr project. Every version before 6.4 is declared as "End Of Life".
PHP 7 required!
Due to the requirements of the libraries we use we can't support PHP 5 anymore!
The only way to install this module properly is the usage of composer!
To install the module including its dependencies simply change into your drupal directory and run composer require drupal/search_api_solr:^2.6
.
Upgrade path for Search API Multilingual Solr Search 8.x-1.x
We recommend to wait for the 8.x-3.0 of this module. But for those who can't wait we created a small guide to describe the required steps.
Unfortunately it's not that easy to implement an automated upgrade path that fits all installations. I already implemented "custom update hooks" that work.
Contact me if the manual guide mentioned above doesn't meet your requirements.
Changes since 8.x-2.5
- Issue #3033338: Any schema backend produces error "undefined field index_id" on index status page by robcast, mkalkbrenner
- Issue #3029536: Filtering by content type field doesn't work if more than one option is selected by mkalkbrenner, nicrodgers