Title: Base Cache Directory
Last modified: August 21, 2016

---

# Base Cache Directory

 *  [Eduardo Turiño](https://wordpress.org/support/users/eturi/)
 * (@eturi)
 * [11 years, 12 months ago](https://wordpress.org/support/topic/base-cache-directory/)
 * Hi there. Congrats for this amazing plugin. Simple yet powerful.
 * WordPress content directory (by default wp-content) can be renamed with `WP_CONTENT_DIR`
   definition or using iThemes Security’s (formerly Better WP Security) built-in
   feature.
 * Please take this into consideration when filling the default value in Directory/
   Expiration Time –> Base Cache Directory
 * [https://wordpress.org/plugins/quick-cache/](https://wordpress.org/plugins/quick-cache/)

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

 *  Plugin Author [Raam Dev](https://wordpress.org/support/users/raamdev/)
 * (@raamdev)
 * [11 years, 11 months ago](https://wordpress.org/support/topic/base-cache-directory/#post-4988018)
 * Thank you very much for the report! I’ve opened a new issue here on GitHub to
   track this:
 * [https://github.com/websharks/quick-cache/issues/206](https://github.com/websharks/quick-cache/issues/206)
 *  Plugin Author [Raam Dev](https://wordpress.org/support/users/raamdev/)
 * (@raamdev)
 * [11 years, 11 months ago](https://wordpress.org/support/topic/base-cache-directory/#post-4988019)
 * I thought that I should add that while the UI doesn’t reflect the custom `WP_CONTENT_DIR`
   path, the backend code should be using the custom path correctly when writing
   the cache files, as this was specifically fixed in the previous release:
 * > **Bug Fix: **Obey custom content directories. If you have customized your `
   > WP_CONTENT_DIR` and `WP_CONTENT_URL` constants to point somewhere other than
   > the default, Quick Cache will now obey those and use your custom directory 
   > for storing cache files. See [https://github.com/WebSharks/Quick-Cache/issues/95](https://github.com/WebSharks/Quick-Cache/issues/95)
 *  Plugin Author [Raam Dev](https://wordpress.org/support/users/raamdev/)
 * (@raamdev)
 * [11 years, 11 months ago](https://wordpress.org/support/topic/base-cache-directory/#post-4988028)
 * After further testing, I discovered that if your `WP_CONTENT_DIR` path is outside
   the `ABSPATH`, then Quick Cache doesn’t handle the path properly.
 * I’ve reopened the issue addressing the custom `WP_CONTENT_DIR` bug and will get
   this fixed for the next release, along with a fix for the UI so that it shows
   the correct path:
 * [https://github.com/websharks/quick-cache/issues/95](https://github.com/websharks/quick-cache/issues/95)
 * [https://github.com/websharks/quick-cache/issues/206](https://github.com/websharks/quick-cache/issues/206)

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

The topic ‘Base Cache Directory’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/quick-cache_efefef.svg)
 * [Quick Cache (Speed Without Compromise)](https://wordpress.org/plugins/quick-cache/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/quick-cache/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/quick-cache/)
 * [Active Topics](https://wordpress.org/support/plugin/quick-cache/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/quick-cache/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/quick-cache/reviews/)

 * 3 replies
 * 2 participants
 * Last reply from: [Raam Dev](https://wordpress.org/support/users/raamdev/)
 * Last activity: [11 years, 11 months ago](https://wordpress.org/support/topic/base-cache-directory/#post-4988028)
 * Status: not resolved