Please note that this Support article contains frontend customizations via modifying the legacy Algolia template files, which are deprecated and unsupported by the Algolia Support Team.
For more information, please review this Support article - "Why is modifying Algolia template files for customizations not supported?"
If you’re using an external system to manage your theme files, you should ignore assets/algolia_config.js.liquid. This file contains the front-end settings that you configure in our admin interface.
An example of this would be when you change the amount of products displayed on the search page. Our front-end code needs to access this information. The way we do this is by updating the algolia_config.js.liquid file on every change you make in the admin interface.
Issues will arise if you:
- copy all files in your theme to an external system,
- perform edits in the admin interface, which modifies the live
algolia_config.js.liquidfile, - do code changes in this system,
- then deploy your code with the old version of the file, which will override the new one.
However, most of those systems let you ignore files. Add a rule for this file, and everything should work fine.