Hi @swudev, I’m sorry you struggle with the setup,
Can you confirm your website has access to the network?
Could you tell me more about your hosting provider, and technical environment?
Thread Starter
swudev
(@swudev)
This is on WPengine, another site with the same theme is working so it must be an issue with some of the customization on this particular site. I’ll research it further and report pack if I narrow down the issue.
Thread Starter
swudev
(@swudev)
WPengine has a staging/production for each site, I can clone production to staging and the plugin menu appears normally. So maybe it is an issue with it accessing the api over the network, although it does appear to confirm the api credentials. Can you send me a snippet that I could use to test that it is connected to the api maybe adding a verified status connected to api to this page. /wp-admin/admin.php?page=algolia-account-settings
Hi @swudev ,
We have had similar issue in the past with WPEngine. Deleting the object-cache.php file in the wp-content folder fixed the issue.
Also, can you tell me if you are using SSL and if so if the certificate is valid?
Thread Starter
swudev
(@swudev)
ok, I’ll give that a try. I did have success (temporarily modifying the plugin code to not check is_reachable that was returning true on staging and false on production WPengine).
It was connecting and indexing. But I am getting search errors in the plugin log.
Index wp_searchable_posts does not exist
When I look in my Algolia dashboard I see wp_searchable_posts_tmp so it does look like wp_searchable_posts is not available in my indices.
Also what is searchable_posts vs posts in the plugin settings? Seems like searchable is a smaller subset of posts. Can I index just posts?
Thanks again for your assistance.
Hi @swudev,
The errors you are describing look like caching problem.
What version of the plugin are you using?
The searchable posts index contains all post_types that are searchable. The posts index only contains the post type named “post”. You can definitely just index the later if you only want to display posts anyway.
Regarding the index suffix _tmp, this should disappear once the indexing has completed. If it is not the case, it means that the queue does not detect the end of the indexing and doesn’t proceed with the renaming. I know that several users are experiencing this and I’ve not been able to re-produce it so far. Let me know if you have a clue.
Hey @swudev,
I just released 1.4.0 which should solve the issue where your queue gets stuck before being able to move _tmp indices to their final destination.
Give it a try and let me know if that works out for you!
