Since the search/update and autosuggest endpoints for SearchStax apps can use different domains, the previously used “Auto-suggest core” setting for search servers was inadequate for covering configuration for all users.
Instead, a new “Auto-suggest endpoint” setting was introduced where users can just copy and paste the “Auto-Suggest Endpoint” value from the SearchStax admin UI verbatim.
Existing configuration is adapted automatically in an update function, in addition a backwards-compatibility layer ensures that legacy configuration continues to work as before. The latter especially applies to configuration that uses the Key module, which cannot be migrated automatically. In case you are using a key to configure your SearchStax search server, and you are using auto-suggest, please adapt the key value as shown below:
Key value before:
{
"update_endpoint": "https://searchcloud-2-us-east-1.searchstax.com/12345/searchstax-test/update",
"update_token": "YourSecretToken",
"autosuggest_core": "searchstax-test_suggester"
}
Key value after:
{
"update_endpoint": "https://searchcloud-2-us-east-1.searchstax.com/12345/searchstax-test/update",
"update_token": "YourSecretToken",
"autosuggest_endpoint": "https://searchcloud-2-us-east-1.searchstax.com/12345/searchstax-test_suggester/emselect"
}
You can find the correct value for the autosuggest_endpoint property in the SearchStax admin UI as the “Auto-Suggest Endpoint” under “All APIs » Search & Indexing”. Alternatively, it can also be constructed from the update_endpoint in most cases (specifically, in all cases where auto-suggest on your Drupal site was working correctly before) by replacing the last two path components as shown above: using the previous value of autosuggest_core as the second-to-last component and emselect as the final one.
