But it warms only published posts (posts, pages, products), not private, draft etc.
The posts are added to the buffer (internal DB field), and then, on cache_warmer_process_posts_enqueue interval, the posts are iterated over and visited.
Can you make sure it’s present in the Action Scheduler tasks?
On admin panel: Tools -> Scheduled Actions -> Pending (tab). Then select “cache_warmer_process_posts_enqueue” and click “Run”. See if the changed posts get added to the: Cache Warmer -> Logs -> Triggered (tab).
And maybe could you send me screenshots of it. So I will verify you’re checking the right place.
I do as you said and now it’s working, I don’t know what caused the problem.
Is your warm up feature can also warm up “related” URLs? For example, creating a product should also purge the category the product have been added to.
Yes, I do working late, as I have flexible schedule 🙂
Maybe the problem was caused by Action Scheduler issues (like the scheduled tasks did not start, but after you started it manually, it began warming all accumulated posts in there).
Is your warm up feature can also warm up “related” URLs? For example, creating a product should also purge the category the product have been added to.
By “purge” you mean “warm”? No, it currently can’t. It warms only the posts you edited / published directly; and not the related category, terms of it.
But we can consider such a feature, if you want.
Viewing 4 replies - 1 through 4 (of 4 total)
The topic ‘“Posts warming after their update” not working’ is closed to new replies.