Try asking the WooCommerce team. This should not happen.
@tillkruess,thanks i will try this
@tillkruess hello,Hello. I have created a support ticket with the WooCommerce support team.. They said that I need to get in touch with the Redis plugin side. Could you please check how to configure it so that the Redis cache for the cart and checkout pages can be excluded?thanks!
-
This reply was modified 3 weeks, 4 days ago by
losvincent.
This plugin does not have the concept of pages. You can only ignore groups. See the README / FAQ.
@tillkruess I have read the readme document and found WP_REDIS_IGNORED_GROUPS, but I don’t know how to configure it so that it can bypass the WooCommerce cart.
Hello, after multiple tests, I’ve found that when in the state of an unlogged-in visitor, the Redis cache will cause the data on the cart page to be out of sync. However, if a buyer registers an account and logs in, the data of functions such as the cart will be updated normally, and there won’t be any confusion caused by the Redis cache. What’s the principle behind this? Is it possible for the plugin to address the issue of data submission in Redis for the visitor mode in the next version update?
Are you using a page caching plugin that’s maybe causing this?
Redis Object Cache is just providing an API to WP and WC, this plugin does not cache anything itself.