Support » Plugin: WP Super Cache » Few questions about WP-Super-Cache in combination with Cloudflare

  • Hey there,
    i have a few questions regarding your plugin in combination with a free cloudflare account:
    I have a hosted wordpress-website where traffic is routed over couldflare by DNS.
    And i installed the WP-Super-Cache plugin. As far as i understand this plugin creates static HTML-Files, which are automatically updated when, for example, a comment is made.
    But on my cloudflare account caching is also enabled. But i wonder if and how cloudflare will get notified when a static html-page needs to be reloaded because on the hosted server a new comment was made and so the WP-Super-Cache plugin created a new static file. In my understanding cloudflare would be serving the old static file for a fixed time, or did i miss something here?

    Then: I read in the plugin settings about “304 Not Modified” (which is disabled in my setting) and “Enable dynamic caching”. There is a link to the FAQ but i couldn’t find an explanation for both. Can you give me a short one?

    And last question is about the “preload” config-tab:
    Since i can’t run chronjobs on my hosted server, what will trigger the preload-function? Any site-visit? If so, will the pageload-speed be slower if i enable it? And i saw the setting for how many articles schould be preloaded. Does this control how many articles are preloaded everytime the preload-event is triggered? Or does this control how many articles are preloaded as maximum in general?
    I want to be my website as fluid as it can. I have a few static pages, the rest are articles. Please help me to set up the best configuration and help me understand so i don’t have to bother you again 🙂
    Big thanks in advance!

Viewing 7 replies - 1 through 7 (of 7 total)
  • xspyrox


    Is this plugin not supported/developted anymore?

    Plugin Author Donncha Ó Caoimh


    As I said on Twitter, don’t use Cloudflare and WP Super Cache together. You’ll only experience pain, probably. Use one or the other.

    The 304 not modified header relates to this header. The server tells the browser that the page hasn’t changed.

    Preloading won’t significantly slow down your site at all. It runs using WP-Cron and fetches a page at a time so it takes a while to fetch every page.
    The number refers to how many posts are fetched. It’s only ever 1 at a time.

    I can second that.

    When I used cloudflare for this past month, cloudflare stopped caching it properly. Our site used to have lots of bandwidth being taken care by cloudflare.

    So beginning of this month I uninstalled W3TC, and you can see the bandwidht dropped beginning this month, and installed it again yesterday, and you can see how quickly the bandwidth served by Cloudflare picks up. So… indeed, do not use this WP Supercache with cloudflare.

    Hey @amaravati ,
    thanks for the additional information on that topic 🙂
    From my understanding the WP-Plugin would be the better choice for caching because the plugin can determine better which pages have changed (for example if a comment was added) since the last caching, so the one page needs to be cached anew. Or am i wrong in that believe?

    Thanks in advance 🙂


    I believe most cache plugins can re-cache (basically, flush/delete the cache of that page/post) after the post/page is modified. Then, when a next request is made to WP, the cache will then be created. Rather a standard feature.

    But the difficulty is, to ‘inform’ cloudflare to flush/delete the cache for that particular page. You can either have W3TC, with the cloudflare extension. Or download a specific Cloudflare Plugin for wordpess (Cloudflare has their own plugin as well, but there are also others).

    So, short answer: you are correct, but that feature is not specific to this plugin. Most Cache plugins do that.

    @amaravati no offense against this plugin, i was thinking about caching-plugins in general. Just named only this plugin, because we are discussing on the comment-page about this plugin 😉
    But yes, that’s exactly what i thought: Cloudflare would need to get informed about small changes on wordpress in some way…
    So i guess i will disable cloudflare and use only the internal wordpress-caching (namely i will use this W3TC plugin), then caching is completely controleld by the plugin, so it should be the best way for delivering cached but up-to-date pages to the user, am i right? 🙂

    If you want something free, yes you are right.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Few questions about WP-Super-Cache in combination with Cloudflare’ is closed to new replies.