• Resolved rbsmidt

    (@rbsmidt)


    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:

    https://github.com/woocommerce/woocommerce/blob/ba582c307b68104ed631861ef32a3548a7f1e08a/includes/admin/reports/class-wc-admin-report.php#L40

    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 cached

    If anything in the above is unclear, please let me know. And thanks for a good plugin!

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Till Krüss

    (@tillkruess)

    Please ask the WooCommerce support team about this issue. This plugin only provides the Redis connection WooCommerce uses to cache things.

    Thread Starter rbsmidt

    (@rbsmidt)

    Hi Till

    Thanks for your quick reply, and i understand that you can’t support 3rd party plugin issues. But one last question, that you might be able to help me with.

    Does the “site-transient” caching group cover all transients on a wordpress installation, or only specific transients? And if not which other groups include transients?

    If you know where to read docs about the different caching groups in WP, i’d really appreciate a link. I haven’t been able to find much about it myself.

    Again thanks for a great plugin.

    Plugin Author Till Krüss

    (@tillkruess)

    Yes, the “site-transient” group caches all transients. Double check the WP’s core code.

    I’m not sure if there a docs explaining caching groups. I kinda get all my knowledge from the source code.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Issues with WooCommerce Reports’ is closed to new replies.