Releases for Search API

This is release 1.33 of the Search API module, containing a single bug fix for a critical issue introduced in the previous release (1.32).

Caution: There is a known issue (#3438940: Search API 1.33 breaks Search API Solr Datasources and installations with custom field types that use fallback types) causing problems in search views when using the “Solr Document” datasource. Please use release 1.34 instead.

This is release 1.31 of the Search API module, containing several bug fixes and new features.

The highlights:

This is release 1.30 of the Search API module, containing several bug fixes and new features.

Known issue: If you are using the “HTML filter” processor, you should not use this release, since it contains a considerable performance regression (#3388678: Performance issues after fixing 'PHP 8.1 preg_replace()' issue) that will slow down indexing drastically for larger field values. Please use release 8.x-1.31 instead, or stay with 8.x-1.29 in case you are still using Drupal 9.

This is release 1.28 of the Search API module, containing several bug fixes, including ones for regressions introduced in release 1.26.

This is release 1.26 of the Search API module, containing several bug fixes and new features.

This is release 1.24 of the Search API module, containing several bug fixes and new features.

There are two potentially breaking changes in this release that you should be aware of:

• #3253986: Tokenizer doesn't allow no ignore characters changes how the “Tokenizer” processor handles an empty value for the “Ignored characters” configuration. Set the value to ._- explicitly to obtain the previous behavior.
• Change record: Removed the search_api_base_path query option.

This is release 1.22 of the Search API module, containing several bug fixes and new features.

There is one new change record for this release: ContentEntity::filterValidItemIds() is deprecated.

Please be aware that this will be the last release supporting Drupal 8. The 1.24 release will require at least Drupal 9.2 – see #3256028: Increase Core version requirement to 9.2. (1.23 was a patch release with just a single bugfix.)

Known issue: This release is missing an update hook to update the schema for the Task entity type. This will have no negative impact on your site’s functioning, though, except for an error message in the status report. See #3247781-68: Database update fails, database schema problem on latest release for details.

This is release 1.28 of the Search API module, containing a few bug fixes.

Note: If your facets are pointing to the wrong path after updating to this release, please see #2159827-24: Fix search base path in Facet API adapter.

This is release 1.27 of the Search API module, containing several bug fixes and new features.

This is release 1.18 of the Search API module, containing several bug fixes and new features.

Caution: Some people have complained about fatal errors introduced by this module version in certain circumstances. Please be prepared to roll back to a previous version if that is the case for you, or wait for the new release with the bug fix, planned for November. See #3178941: Fatal error "Call to a member function getColumns() on bool" for details.

This is release 1.16 of the Search API module, containing several bug fixes and new features.

Caution: As this release changes a service definition, clearing the cache a second time after deploying (via drush cr or running update.php again) might be necessary. (See #3126367: TypeError: Argument 2 passed to SearchApiConverter::__construct() must implement EntityRepositoryInterface.)

This will be the last release compatible with Drupal 8.7, the next scheduled release will require Drupal 8.8 and be fully compatible with Drupal 9.0. (Unless a security release is urgently required.)

This is release 1.14 of the Search API module, containing several bug fixes and new features.

Please note several important changes in this release:

• Due to #3065385: Drush commands entirely broken because of Search API changes, this release will be incompatible with any 2.x or 3.x versions of the Search API Solr module before release 3.2 (or very recent dev versions). It will continue to work with 1.x releases, though. Also, for 2.x and older 3.x versions, only Solr Drush commands will be broken – otherwise, both modules will work fine.
• Developers, please note that in #3023704: Convert hooks to events we deprecated all hooks defined by this module, providing new events as replacements. See the change record for details. Please note that it is currently planned to remove all our hooks before the release of module version 9.x-1.0, so hooks in custom modules will also need to be converted accordingly in order to keep them working after the move to Drupal 9.
• People using the “Rendered HTML output” field and managing a multi-lingual site are advised to try out the latest (D8) patch in #3035977: Rendered HTML Output doesnt respect activeLanguage completely to make sure it doesn’t break anything on their site, or maybe even helps resolve some edge case issues with that field on multilingual sites. The fix we have in mind requires temporarily changing the global language negotiator, so it’s hard to see whether this couldn’t lead to unintended consequences for specific setups. Therefore, having a large number of people testing this before committing would be very helpful.

This is release 1.26 of the Search API module, containing several bug fixes and new features.

This is release 1.11 of the Search API module, containing several bug fixes and new features.

Short note: Final chance for providing feedback on #2948707: ContentAccess processor fails to account for all grant records in case you are using more complex node access definitions (and the “Content access” processor). This issue will probably be committed soon.

This is release 1.25 of the Search API module, containing several bug fixes and new features.

This is release 1.8 of the Search API module, containing several bug fixes and new features.

This is release 1.23 of the Search API module, containing several bug fixes and new features.

NOTE: Since this version was released, a critical regression has been found in it. Therefore, please don't install this release, but use the next one, 7.x-1.24, instead.

This is release 1.6 of the Search API module, containing several bug fixes and new features.

This is release 1.4 of the Search API module, containing several bug fixes and new features.

One important note is that this release is needed for use with the latest dev version (and upcoming Beta versions) of the Search API Autocomplete module.

There are no new API changes in this release.

This is release 1.22 of the Search API module, containing several bug fixes and new features.

This is the 1.1 release of the Search API module.

It contains some bug fixes, especially for fatal errors that occurred when using caching for search views, and some new features.

This is the fourth release candidate for the Search API module's 8.x-1.0 version. It fixes a single, major bug introduced in the RC 3 release.

This release is supposed to be ready for release and contains no known (major) bugs. Unless such a bug is discovered before then, the first stable release, Search API 8.x-1.0, will be released in the middle of next week, around April 26.

This is the second release candidate for the Search API module's 8.x-1.0 version.

Compared to the RC 1 release it mainly fixes #2866454: Several problems in update 8103, which can lead to error when running update functions (for release Beta 5 or newer) in certain setups, and two minor issues with the database backend. Updating, especially from Beta 5 or RC 1, is strongly recommended.

The release is supposed to be ready for release and contains no known (major) bugs. Unless such a bug is discovered before then and cannot be fixed in time, the first stable release, Search API 8.x-1.0, will be released next weekend, April 15 or 16.

This is the Beta 5 release of the Search API, containing numerous bug fixes, new features and other improvements.

This release fixes all remaining release blockers and doesn't contain any known major issues. In all likelihood, this will be the last Beta release. It's planned that a release candidate (RC version) will be released within a week, and then the 8.x-1.0 stable release a week after that. If you want to make sure the stable release will support all functionality that you need, this is the moment to try the module out and verify this.