Title: fallback cache default dir change
Last modified: August 27, 2020

---

# fallback cache default dir change

 *  Resolved [alx359](https://wordpress.org/support/users/alx359/)
 * (@alx359)
 * [5 years, 9 months ago](https://wordpress.org/support/topic/fallback-cache-default-dir-change/)
 * Would suggest relocating the fallback cache directory to `wp-content/cache/wp-
   cloudflare-page-cache/*` instead of `wp-content/wp-cloudflare-super-page-cache/*`
   like it’s now.
 * Some potential advantages of this:
    a) better/more consistent folder organization,
   by following the de-facto standard of other major cache/optimization plugins 
   like wp-fastest-cache and wp-rocket that write their generated stuff into /cache.
   b) implicit compatibility with other plugins that scan for threats but by default
   may exclude directories known for containing generated/tmp content like /cache.
   c) keep special R/W permissions contained within a specialized /cache folder

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

 *  Plugin Contributor [iSaumya](https://wordpress.org/support/users/isaumya/)
 * (@isaumya)
 * [5 years, 9 months ago](https://wordpress.org/support/topic/fallback-cache-default-dir-change/#post-13324343)
 * Hi [@alx359](https://wordpress.org/support/users/alx359/),
    Personally I like
   this idea and personally I would also love to see it like that but the problem
   is backward compatibility as if someone is running our current plugin there already
   is `wp-content/wp-cloudflare-super-page-cache/*`. Now adding `wp-content/cache/
   wp-cloudflare-page-cache/*` means there is just another unnecessary folder in
   the server with lots of files. Most people won’t bother to FTP and delete the
   old folder to keep the server clean.
 * So, basically we have to add a script for the upgrade procedure to delete `wp-
   content/wp-cloudflare-super-page-cache/*` from the server and then recreate `
   wp-content/cache/wp-cloudflare-page-cache/*` and basically regenerate the whole
   fallback cache again. This will add extra code to the plugin just for changing
   folder structure.
 * Moreover, if anyone changes the permission of the `cache/` folder we might not
   have write permission in it. These are the issues comes in my mind right out 
   of the back. But I suppose [@salvatorefresta](https://wordpress.org/support/users/salvatorefresta/)
   have more points to add on this matter.
 * But again your points are valid.
 *  Plugin Contributor [Salvatore Fresta](https://wordpress.org/support/users/salvatorefresta/)
 * (@salvatorefresta)
 * [5 years, 9 months ago](https://wordpress.org/support/topic/fallback-cache-default-dir-change/#post-13343748)
 * Hi [@alx359](https://wordpress.org/support/users/alx359/) ,
    your suggest is 
   good. I will think about it 😉

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

The topic ‘fallback cache default dir change’ is closed to new replies.

 * ![](https://ps.w.org/wp-cloudflare-page-cache/assets/icon-256x256.gif?rev=3234997)
 * [Super Page Cache – Cloudflare Cache, Page Speed & Core Web Vitals](https://wordpress.org/plugins/wp-cloudflare-page-cache/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wp-cloudflare-page-cache/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wp-cloudflare-page-cache/)
 * [Active Topics](https://wordpress.org/support/plugin/wp-cloudflare-page-cache/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wp-cloudflare-page-cache/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wp-cloudflare-page-cache/reviews/)

 * 2 replies
 * 3 participants
 * Last reply from: [Salvatore Fresta](https://wordpress.org/support/users/salvatorefresta/)
 * Last activity: [5 years, 9 months ago](https://wordpress.org/support/topic/fallback-cache-default-dir-change/#post-13343748)
 * Status: resolved