Just to confirm, this is for the long search box found in the middle of the screen for the provided link?
Assuming yes, I am seeing some things there affected by your active theme, and then the rest would likely be coming from https://www.kozzi.com/wp-content/plugins/wp-search-with-algolia/css/algolia-autocomplete.css which is part of what ships with the plugin.
Best to override from the theme instead of edit the algolia-autocomplete.css file directly, but it’ll be a good spot to review and inspect for your own selectors.
Hi
What do you mean override from the theme? I was using the use Algolia in the backend option – which worked great. But that option is causing 502 Gateway errors. I tested other plugins extensively but and the errors are definitely a result of this plugin. So now I am testing the instasearch option.
As for the text I am talking about — its the search results text and title.
https://www.kozzi.com/?s=building&is_v=1
for example.
Dan Kosmayer
From what i’m seeing with that link, it’s all either inline CSS, or being affected by your theme, so nothing coming from the Algolia plugin provided CSS.
What I meant by overrides, is if there are styles being applied from our plugin, you’d want to make your changes to override, via either the theme or perhaps the customizer settings so that when we push out an update, you don’t lose your customizations.
Hi
Do you have any idea why I would be getting 502 Errors using the use algolia in the backend option?
Dan
Sadly no as it’s a pretty generic error. Error logs may be able to provide more information.
