The cache setting does not work (possible issue with W3 Total Cache)

  • Hi,

    I recently changed servers on my website. On the new server, I am using W3 Total Cache.

    This seems to break the cache function of the plugin. I used to have it at two weeks, and use chron jobs to reset it at specific hours. Now, the plugin makes constantly calls to Google Analytics, even without the Chron jobs, I literally refresh the page and see new views. By the early afternoon, I reach the quota.

    Any idea which part of W3 Total Cache is responsible for this? I suspect that it might be the Database Cache on Memcached. Unfortunately, I couldn’t investigate it before I reached the quota.

    Any suggestion will be greatly appreciated.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter Angelos Kyritsis

    (@angelos-kyritsis)

    I have tried adding an exception in the Database Cache of the W3 Total Cache, but, unfortunately, it didn’t change anything.

    https://i.imgur.com/Qzp48S7.png

    The problem seems to be that there is no _transient_gapp-transient- and _transient_timeout_gapp-transient- created in wp_options, which, if I understand correctly the plugin’s function, control the caching.

    https://i.imgur.com/lZKKfMK.png

    Plugin Author maximevalette

    (@maximevalette)

    Hi Angelos,

    That’s weird because I use the standard WordPress cache methods in order to make it compatible with any cache system.

    If you disable the memcached cache in W3 does it change something?

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘The cache setting does not work (possible issue with W3 Total Cache)’ is closed to new replies.