Issues with WooCommerce Reports
-
I’m running Redis on a WP/WooCommerce powered shop, and for page optimisation it works siper good.
I am however facing some issues in the wp-admin area. After switching from Memcached to Redis, it seems that the custom date range for WooCommerce reports broken. The report fetch request seems to be cached. Scenarios that occur:
1. I Choose the period “this month”, which shows correctly. I then choose a custom period (01/01/2016-01/01/2017). The reports still show results for “this month”.
2. I enter a custom date range before trying any of the pre-defined reports. First one shows up correctly, subsequent ones will show the first again and again.
The start and end date are also randomly switched back to the previous period when the results load.
I’ve been in contact with WooCommerce Support Team to find out which caching groups they store the reports in, hoping that i could ignore a group to get things working. They didn’t know much about Redis, but pointed me in the direction of the source code of the reports:
So the reports are cached in transients, i see. But i can’t really find docs caching group name for transients. Also i would want to know how many other features i give up caching, if i find the group name for transients and ignore them?
So my question is:
1) Do you know how to bypass the cache for wp-admin requests such as WooCommerce Reports?
2) Can you deduct anything from the above github link, that shows which group to ignore in order to stop the reports request from getting cachedIf anything in the above is unclear, please let me know. And thanks for a good plugin!
The topic ‘Issues with WooCommerce Reports’ is closed to new replies.