-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Auto Purge Content On Update" no longer working #496
Comments
Oh i realized maybe this is the same issue as the following one: We always use REST API in our mobile app, and i checked the cache for the direct url is correctly purged after post updating, but its REST API is not working properly. |
I am having the same problem, no page purge when updating content on site... Do you have (for example) a specific product page cache purged when you update that product's price? |
We are also facing this issue since past few months after using APO in site. Seriously cloudflre needs to fix this bug |
What are we going to do to get this attention??? How are we gonna get attention? I am gonna post to facebook groups as well to get attention as much as possible... |
Any updates on this? |
Confirmation
WordPress version
6.0.2
Cloudflare-WordPress version
4.11.0
PHP version
7.4
Expected result
The CloudFlare WordPress plugin should purge a post's cache on CloudFlare after a post is updated. It worked before when "Auto Purge Content On Update" was available and “Automatic Platform Optimization for WordPress” was not introduced.
Actual result
After “Automatic Platform Optimization for WordPress” was introduced and "Auto Purge Content On Update" was discontinued, the plugin no longer purge cache automatically for an updated post.
Steps to reproduce
Update an existing post, and see whether cached user can see the new contents immediately. Previously they can, but now they can't until I purge all cache on CloudFlare.
Additional factoids
No response
References
No response
The text was updated successfully, but these errors were encountered: