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.29 of the Search API module, containing a lot of bug fixes and a few new features.
The non-bugfix improvements are mostly aimed at developers: for one, README.md now contains a list of known query tags, which can be helpful when altering search queries; and we added Query::createAndAddConditionGroup() for the prevalent use case of creating a condition group, to also add it to the query object without a separate method call.
This is release 8.x-1.27 of the Search API module for Drupal 9/10. It contains a bug fix for a security issue and should be installed as soon as possible.
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.
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.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 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.12 of the Search API module, containing several bug fixes and new features.
If you are still using the deprecated “Search API Taxonomy Term Handlers” module, please be advised that it will be removed from the project before release 8.x-1.13. An update hook is included in this release that will attempt to uninstall it. If this fails, please uninstall it manually to avoid problems at the next update. (The module serves absolutely no purpose at this point and is empty.)
This is release 1.10 of the Search API module, containing several bug fixes and new features.
Furthermore, if you are using the “Content access” processor, it would be great if you could go to #2948707: ContentAccess processor fails to account for all grant records and test the latest patch there, to make sure it doesn’t break any existing setups (and, in case you have some non-standard node access setup, to maybe confirm it improves support for those as well).
Thanks!
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.7 of the Search API module, containing several bug fixes and new features.
One noteworthy change is that #2922525: Index items only at end of page request changed the “Index items immediately” option to delay indexing until the end of the page request (instead of index right away when the change occurs). This is in line with the functionality in Drupal 7 and is expected to resolve several edge case problems that occurred previously as well as improve performance.
However, it is possible that this change could also lead to problems in (other) edge cases, so please (if you have “Index items immediately” enabled for one or more search indexes) make sure to thoroughly test this new module version on your site and report any problems you notice!
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.
