Releases for Search API

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.

This is the Beta 4 release of the Search API module's Drupal 8 version.

While there are no known major bugs and the module is fully usable at this point, this version is still not completely stable and should only be used with great care in a production environment. Especially, the Drupal Security Team will not cover this release, so security-relevant issues might be discussed and resolved publicly (in case any are discovered).

If you want to help get this module to a stable release, or get an idea of the current status, please see the list of release blockers and targets.

This is the second Beta release of the Search API module's Drupal 8 version.
This release is compatible with facets-8.x-1.0-alpha5.

This is the Alpha 17 release of the Search API module's Drupal 8 version.

While there are no known major bugs and the module is fully usable at this point, this version is still unstable and should only be used with great care in a production environment. No data update paths will be provided for Alpha versions of this module, so upgrading to this version, or from this to a later one, might discard some of your search configuration. Use with care!

This is the Alpha 16 release of the Search API module's Drupal 8 version.

While there are no known major bugs and the module is fully usable at this point, this version is still unstable and should only be used with great care in a production environment. No data update paths will be provided for Alpha versions of this module, so upgrading to this version, or from this to a later one, might discard some of your search configuration. Use with care!

This is the Alpha 15 release of the Search API module's Drupal 8 version.

This release changes the configuration format of the default entity datasources (i.e., how the bundle and language settings are stored). This means manual intervention will likely be needed if you're updating to this version from Alpha 14 on a site with datasources restricted to certain bundles and/or languages.
There were no other major schema changes.

Fixes Search API - Moderately Critical - Multiple Vulnerabilities - SA-CONTRIB-2016-022

This is release 1.17 of the Search API module (Drupal 7 version).

It fixes numerous reported bugs and adds a few minor features.

This is the Alpha 11 release of Search API for Drupal 8.

It is compatible with the Drupal 8.0.0 stable release. A lot of parts are already working fine, but since the module is still very unstable and several major changes are still planned it is not recommended to use this version in production.

Especially, note that there will be no data update path for this module's configuration while the module is in Alpha status!

This is the Alpha 9 release of the Search API module's Drupal 8 version.

It contains a few new features and several bug fixes to keep up with changes in Drupal 8 Core.

This is the Alpha 8 release of the Drupal 8 version of the Search API. It contains a few adaptions to stay compatible with Drupal Core, as well as some new (small) features.

This is the 8.x-1.0 Alpha 6 release of the Search API project, containing a few bug fixes and created to be compatible with Drupal Core's 8.0.0 Alpha 12 version.

This is the fifth Alpha release for the Search API module, containing just a few bug fixes (especially in the tests) compared to Alpha 4.

This is the third Alpha release for the Search API module. It was created to be compatible with the Beta 9 release of Drupal Core.

This is release 1.14 of the Search API module, containing several bug fixes as well as a few small new features.

Note: If you are currently using a development snapshot made in November or December, please be aware that #1184610: Limit indexes to specific entity bundles had to be reverted due to a lack of testers for a follow-up patch. Therefore, if you are already using a bundle-specific index do not update to this version! Rather, wait for that issue to be committed again and then switch to that dev snapshot (or the next stable release after it).
If you are updating directly from 1.13 or an earlier version, you can update just as usual.

This is stable release 1.13 of the Search API module. It contains several new bug fixes, including an adaption to the recent change in Views' cache plugins.
Upgrading is recommended for all users of the module.

This is release 1.11 of the Search API module, containing several new bug fixes, partially for regressions introduced in release 1.10.

The most important bug fix is a follow-up to #2118589: Node access check missing from comment indexes. A missing check in the original patch for that issue means that, with the 1.10 version of Search API, the following message will appear in your logs for every search if you don't have the "Node access" data alteration enabled:
SearchApiException: Required field search_api_access_node not indexed on index Default fuzzysearch index. Could not perform access checks.
The message can be safely ignored, there is no actual error here – however, the message is of course disturbing and will also completely flood your logs. It is therefore advised that you upgrade to 1.11 as soon as possible if you are using the 1.10 release already.

Another improvement are the new descriptions for the "Node access", "Access check" and "Exclude unpublished nodes" data alterations, introduced in #2155127: Clarify the scope of the "Node access" and "Exclude unpublished nodes" data alterations. These should now make it clearer to users that these data alterations will only filter on the indexed nodes (or the indexed comments' nodes) themselves, and will have no effect at all on related nodes, referenced on the indexed item.
If you are using one of these data alterations and are displaying related nodes in your search results (or make them otherwise available in the search), please make sure that this issue does not affect you and that end users cannot access content that should be invisible to them that way.

This is release 1.9 of the Search API module. It contains numerous improvements to the module, bug fixes as well as new features.

Addendum: Some issues were reported after this release was created regarding #2110315: Specialized filter for users and terms. If you are using taxonomy term filters on the "Parent term" or "All parent terms" properties of a taxonomy term reference, or on another reference that isn't the Field API field itself, please either use the current dev version or wait for the next release 1.10, which should be released shortly.

There are two notable changes which might need special care for a few specific setups:

• #2086783: Remove Views field handlers for "virtual" fields removes the Views field handlers for "virtual" fields, i.e., fields added by data alterations or the like. This was done since these fields can usually not be displayed (since they only exist in the search index, not on the entity itself) and the field handlers were therefore useless and confusing. However, when using Solr (or maybe other backends, too), the fields can be retrieved from the search server directly and viewing them is actually possible.
  If you are using this setup, you will likely need #2099683: Add support for "virtual fields" in Views for the Solr backend (contained in the new Search API Solr Search 7.x-1.3 release) for things to keep working as before.
• Secondly, #2088905: Search API Views and Panels paths. adds some special path handling for Views in combination with Panels. If you use a Panels with Search API Views, please make sure this change doesn't break anything before deploying this module update.

The current development version of the 8.x-1.x branch, compatible to Drupal 8.

This release contains a few new bug fixes and features, concerning mostly the Views integration. For example, there is now a contextual filter for searching all taxonomy term reference fields at once, and the option to change the "Parse mode" (how search keys are parsed – for example, directly pass them to Solr unchanged).

This is a security release, it fixes SA-CONTRIB-2013-001 You are advised to update your version of Search API as soon as possible, especially if you're using the database backend along with Views.

The release also contains a small amount of other bugfixes and adds support for date popups in Views exposed filters.

This release mostly contains bug fixes, most of which should be rather minor and not affect most users.

The most important part, though, is the change in how Views results are indexed (#1368548: Do not index views results by entity id): Since #1368508: Document and enforce nummeric array keys starting at 0 for $views->result will soon be committed to the Views module, older versions of Search API Views could then break with the newest version of Views!
So, if you are using Views, please update to this version of the Search API before updating to the next Views release!

This is the first stable release of the Search API module. Several bugs were fixed that became known in the „release candidate“ period, regarding the indexing workflow, Views, facets and node access.

If you are updating from a Beta version, please also take the RC 1 release notes carefully into account, as they contain important information.