If you notice that routing, Autocomplete, or other front-end behaviour works in your default language but not in a translated locale, check whether the algolia_config metafield has been translated.
The algolia_config metafield stores configuration used by the Algolia Shopify integration. We don't advise translating or manually editing this per locale.
Some Shopify translation apps, such as Translate & Adapt, allow metafields to be localised. If algolia_config has been populated for another language, Shopify may serve that translated/localised version instead of the default configuration.
This can cause issues if the translated version is outdated or incomplete. For example, newer configuration values added by Algolia may exist in the default metafield but be missing from the translated version. This can result in routing or Autocomplete settings not being applied correctly for that locale.
How to check
In Shopify, review the translations for the algolia_config metafield.
If a translated locale contains its own version of algolia_config, compare it with the default version. Signs of a problem include:
- Missing sections of configuration
- Outdated selectors, such as an old Autocomplete selector
- Differences between the default configuration and the translated configuration
- Routing working in the default locale but failing in a translated locale
Resolution
Remove the translated/localised version of algolia_config so that Shopify uses the default metafield value.
After removing the translated value, test the affected locale again. Routing and Autocomplete behaviour should then use the current Algolia configuration.