Disable cached HTML placeholder files when using Cloudflare edge cache only

  • Resolved Ashutosh Sharma

    (@ashutosharma97)


    1 week ago

    Hi team,

    I’m using the plugin on multiple websites hosted on the same server. I’ve disabled the disk/fallback cache options in the plugin settings, but it continues to create files in:

    wp-content/wp-cloudflare-super-page-cache/example.com/cached_html_pages

    These files count toward my server’s inode usage and contain only URL + timestamp.

    I’m using the plugin exclusively for Cloudflare edge caching and do not need local disk/fallback caching. Is there a way to prevent these files from being generated?

    Any guidance would be appreciated.

    Cheers!

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support rodicaelena

    (@rodicaelena)

    1 week ago

    Hi Ashutosh,

    Thank you for writing to us. Those files are not a disk or fallback cache, which is why turning those options off didn’t stop them.

    They come from the “Purge HTML pages only” option (Settings → Advanced). With it on, Super Page Cache keeps a small index file for every HTML page Cloudflare caches (just the URL and a timestamp). When you purge the cache, the plugin uses that list to send Cloudflare only those page URLs, so your static assets (CSS, JS, images) stay cached at the edge.

    To stop the files being created:

    1. Go to the plugin settings and turn off Purge HTML pages only.
    2. Save the settings.
    3. Delete the existing .tmp files in wp-content/wp-cloudflare-super-page-cache/example.com/cached_html_pages/. They aren’t removed automatically once the option is off. You can keep the index.php file in that folder.

    After that, no new files will be created in that folder.

    One thing to keep in mind: with this option off, “Purge whole cache” clears everything in your Cloudflare zone for that domain, including static assets, not just HTML. Single-page purges (for example, when you update a post) still target only the affected URLs. For most sites that’s fine, because assets come back into the cache on the next requests.

    Let us know if this helps.

    Kind regards!

    Thread Starter Ashutosh Sharma

    (@ashutosharma97)

    1 week ago

    Hi @rodicaelena, that helped. Thanks for the quick response and guidance!

    Plugin Support rodicaelena

    (@rodicaelena)

    1 week ago

    Hi Ashutosh,

    I’m glad I was able to help!

    If you happy with our product and support, you can always leave us a short review here https://wordpress.org/support/plugin/wp-cloudflare-page-cache/reviews/#new-post . It would help us a lot.

    Thank you!

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

You must be logged in to reply to this topic.