Problems with W3 Total cache

  • I am using this along with W3 Total Cache and it seems the CloudFlare purge is happening before the cache is being purged, so the first time I update a post it purge’s CloudFlare’s cache only to fill it again with the old version. I need to save twice each time to do a proper purge. Can you fix this?

    One other thing, the CSS style ccpurge.css is affecting all the links on the admin, this needs to be more specific.

    https://www.ads-software.com/extend/plugins/cloudflare-cache-purge/

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

  • There are no purge calls to CloudFlare on posts etc. CloudFlare is only purged when the purge button on general settings page is called or the empty all with cloudflare is called.

    Thread Starter Shaun Robinson

    (@rubious)

    I’m talking about the plugin “CloudFlare Cache Purge” which is designed to purge the post/page cache each time you update it, however because it triggers after W3C purges its cache, you need to save twice to make any changes.

    Perhaps the need for this plugin could be taken away if W3C also purged single page caches from CloudFlare on save? This is if you have the PRO account and “cache everything” on all pages.

    Plugin Author shanaver

    (@shanaver)

    I haven’t run it with W3 Total Cache – it’s more of a simple Cloudflare-only solution that, if you are using W3TC, you wouldn’t need this as well.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Problems with W3 Total cache’ is closed to new replies.