Stan Felix
Forum Replies Created
-
Forum: Plugins
In reply to: [WP Search with Algolia] Scheduled posts not appearing in the indexOkay, I’ll work on this and get back to you.
Forum: Plugins
In reply to: [WP Search with Algolia] Scheduled posts not appearing in the indexSo far have only observed this on the primary post type.
I’ll evaluate how best to test this in a dev env. This is a fairly big site.
Forum: Plugins
In reply to: [WP Search with Algolia] Scheduled posts not appearing in the indexNothing is coming up in logs.
Forum: Plugins
In reply to: [WP Search with Algolia] Scheduled posts not appearing in the indexHi Michael,
Sorry for the delayed response. We currently leverage cron at the server level for the same reasons you mentioned. What are my options for fixing this? I’m facing this issue on a client project daily.
Every time the client notices a post, I update it in WP, which pushes it to the index. This is in no way a solution to this problem.
Thanks again, and I look forward to your response.
Best,
Stan
Forum: Plugins
In reply to: [WP Search with Algolia] Reindex not stopping at 78%Hi @tw2113, thanks for following up. I ran it a couple of times via CLI, and it kept on quitting at 78%; it would not return any errors, which added to the confusion.
So I then proceeded to run it with a –from_batch=, it also kept on quitting on a specific batch number for some reason. I tried running it with verbose to try to get more information on the run, but I think this isn’t supported yet, as it returned Error: Parameter errors: unknown –verbose parameter
I eventually got the reindex to resume by incrementing the batch number; it resumed from that point until it completed at 100%.
I just do not know what was wrong with that specific batch number.
So to sum up, resolved, but have no clue why that specific batch number interrupted the reindex. Adding support for verbose or anything that can provide more specific information would be helpful when troubleshooting these types of issues.
If anyone else encounters this problem in CLI, take note of the last batch run before the interruption and run:
wp algolia reindex –all –from_batch=xxx (last batch number)