We are using Cloudflare pro plan on our website www.pcstudio.in.
From last 1-2 days we are facing an issue where in the prices changed in the backend wp panel aren’t showing up properly on the front end. Below is the example.
Product A’s prices is updated from $100 to $90 - sometime in the Archive Page (category page) it still shows $100 & when clicked on it goes to product details page there it shows $90. Vice-versa also happens sometime.
Is this related to browser cache ttl? Our current time for it is 1 day. Do you recommend changing it to less as our website will have more number of price changes on daily basis & also the traffic is high.
Please use APO for Wordpress based sites. Thank you. APO in exclusively for Wordpress and super optimized, flushes automatically cache and can bypass on cookie base etc. Basically all features you want to have at Wordpress/WooCommerce.
Please post the URL as soon as it happens again so we can take a look into it. Screenshots do apparently not containe the info I am looking for. Thanks.
Below is the URL for reference of the issue. The updated price of this product is Rs. 3999/- and in the product page it shows Rs.5925/- which we have updated just an hour back.
It seems the problem is with APO, as it seems not to flush the correct cache when you update the price. If you hard-reload APO cache gets bypassed and you see the new price (RS. 3999,-).
What exactly went wrong I can’t tell but I am sure @yevgen can shed some light into this.
Yes. We are using 4.8.0. Is there anyway to downgrade that to 4.7.0 from WP Dashboard itself or is there a place to download the earlier versions like git or something?
Guess the issue isn’t resolved even after downgrading the Wordpress Plugin to 4.7.0
I have just changed one of the product prices in the WP Dashboard & it’s reflect on the category/archive page still unless it’s refreshed (Ctrl + F5) or purge cache manually.
But when I open the product details page it shows the updated price.
Our current Browser Cache TTL is 1 day. Do you suggest us to change it? It was unchanged from last 8-9 months & everything was working fine till now. Post March 15th only this issue has started.
Thanks for raising this one; v4.8.1 has been released with an improvement to how we determined whether the cache purge request included the current zone. Could you try that and let me know how you go?
For future reference, the best place to lodge these bugs is in the GitHub issue tracker or customer support tickets to avoid this getting lost on the forums.