instantsearch.php and autocomplete.php not updated

Do you have an algolia folder in your active theme, with both of those files listed in it? It’s possible someone at least originally copied them over with intent to customize, or perhaps has, and others weren’t necessarily aware.

Hi! Thanks for replying! No, I coudn’t find them duplicated in the Algolia folder, neither in others. So I don’t know why it’s telling me they are not updated (the only one I have is updated to the current version). I also have this error coming when I click “enter” in the search bar:

<# } #>

data._highlightResult.post_title.value

<# if ( data._snippetResult['content'] ) { #>?data._snippetResult['content'].value?<# } #>

It is correlated??

Can you open your autocomplete.php and instantsearch.php files from the plugin’s template directory and check for an @since tag towards the top of both? They should say version 2.5.0

Anything with the behavior after pressing enter isn’t going to have anything to do with the admin notices about outdated template files. Can you point me to the site in question where that error is occurring?

Hi Michael!

I have partially solved the issue: I had another plugin called Search WPML with Algolia used to have the search also available for other languages which had the autocomplete.php an instantsearch.php files not updated. Now they are and the error message is not longer coming.

For the second issue, is there a way I can send you the credentials privately?

When I try to re-indicize the data from Algolia->autocomplete when I update the products I have an error message saying there is a problem with a plugin (link to troubleshooting page). Is it possible that since Woocommerce is not updated (when I try to update it it gives me error 500 in the server) then I have this problem in Algolia products update?

We can take support for this going forward to private correspondence. You’ll want to reach out at https://pluginize.com/contact/ and that’ll go into our ticket system.

Definitely worth checking on your error logs as well, to see if anything’s standing out for that “500 Internal Server Error”