Hi @queenielow
My sincerest apologies for missing this. Did you ever figure things out? or did you move on for the time being?
If it’s still going on, can you provide a link to where we could see the error occurring?
Thanks, Michael for checking in.
Unfortunately, it’s not fixed, so I have to revert to the old version of the plugin in order for it to work.
I can set it up on UAT and will let you know when it’s ready, so you can have a look. 🙂
Cheers,
Queenie
Hi Michael,
Apologies, here is the UAT site – shorturl.at/dryLS
The error shows on console log:
InstantSearch.ts:225 Uncaught Error: ThesearchClient` option is required.
See documentation: https://www.algolia.com/doc/api-reference/widgets/instantsearch/js/
at new R (InstantSearch.ts:225:13)
at oc (index.ts:58:3)
at enware-algolia.js?ver=1.5.0:2:18
at enware-algolia.js?ver=1.5.0:143:4`
Cheers,
Queenie
If you have customized templates for the instantsearch.php file and potentially the autocomplete.php template file, you’re potentially going to need to review them for compatibility with the versions we ship with.
From what I’m seeing, we reference searchClient in this spot:
var search = instantsearch({
indexName: algolia.indices.searchable_posts.name,
searchClient: algoliasearch( algolia.application_id, algolia.search_api_key ),
Also can be seen at https://github.com/WebDevStudios/wp-search-with-algolia/blob/2.3.1/templates/instantsearch.php#L79-L83
This searchClient line would be fetching and using the application and search API key coming from the settings page on the backend. It’s also possible that maybe you don’t have one or both of those filled in?
Thanks Michael, I’ll look it up.
