Title: advanced-cache.php was created by another plugin
Last modified: April 18, 2023

---

# advanced-cache.php was created by another plugin

 *  Resolved [dimal](https://wordpress.org/support/users/dimalifragis/)
 * (@dimalifragis)
 * [3 years, 1 month ago](https://wordpress.org/support/topic/advanced-cache-php-was-created-by-another-plugin/)
 * Sometimes other POPULAR caching plugins, leave “advanced-cache.php” but EMPTY
   in the folder. Zero size. But still you get a fatal error from WPSC:
 * **Warning! You may not be allowed to use this plugin on your site.**
 * The file /home/wp-content/advanced-cache.php was created by another plugin or
   by your system administrator. Please examine the file carefully by FTP or SSH
   and consult your hosting documentation.
 * And you have to manually delete the “advanced-cache.php” file. I suggest this
   not needed stop to be changed if the file exists but it is empty.
 * Thanks

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

 *  Plugin Author [Donncha O Caoimh (a11n)](https://wordpress.org/support/users/donncha/)
 * (@donncha)
 * [3 years, 1 month ago](https://wordpress.org/support/topic/advanced-cache-php-was-created-by-another-plugin/#post-16667998)
 * Unfortunately, it’s up to the other plugins to delete the advanced-cache.php,
   not zero it out.
 * Some hosts may put a zero-size file there just to block caching plugins, so it’s
   impossible to know the intention of whoever left the file there, and it would
   be potentially risky removing it.
 *  Thread Starter [dimal](https://wordpress.org/support/users/dimalifragis/)
 * (@dimalifragis)
 * [3 years, 1 month ago](https://wordpress.org/support/topic/advanced-cache-php-was-created-by-another-plugin/#post-16668351)
 * An empty (zero) advanced-cache.php doesn’t stop ANY caching plugin to be installed
   and running, only WPSC.
 * Comet Cache, Fastest Cache, Litespeed Cache, all modify it and run. So not what
   you say.
 *  Plugin Author [Donncha O Caoimh (a11n)](https://wordpress.org/support/users/donncha/)
 * (@donncha)
 * [3 years, 1 month ago](https://wordpress.org/support/topic/advanced-cache-php-was-created-by-another-plugin/#post-16670358)
 * Do you know which caching plugin left a zero size advanced-cache.php? Perhaps
   they would fix their uninstall code, as leaving files behind isn’t best practise.
 *  Thread Starter [dimal](https://wordpress.org/support/users/dimalifragis/)
 * (@dimalifragis)
 * [3 years, 1 month ago](https://wordpress.org/support/topic/advanced-cache-php-was-created-by-another-plugin/#post-16670363)
 * Sure, it is Comet Cache (and its fork Rapid Cache).
 *  [Daniel](https://wordpress.org/support/users/ihenetudan/)
 * (@ihenetudan)
 * [3 years, 1 month ago](https://wordpress.org/support/topic/advanced-cache-php-was-created-by-another-plugin/#post-16677677)
 * Thanks for the information. If Comet Cache and Rapid Cache are leaving behind
   an empty advanced-cache.php file, I suggest contacting their developers to address
   this issue in their uninstallation process.
 * In the meantime, please manually delete the empty advanced-cache.php file before
   activating WP Super Cache to avoid conflicts.

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

The topic ‘advanced-cache.php was created by another plugin’ is closed to new replies.

 * ![](https://ps.w.org/wp-super-cache/assets/icon-256x256.png?rev=3506220)
 * [WP Super Cache](https://wordpress.org/plugins/wp-super-cache/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wp-super-cache/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wp-super-cache/)
 * [Active Topics](https://wordpress.org/support/plugin/wp-super-cache/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wp-super-cache/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wp-super-cache/reviews/)

 * 5 replies
 * 3 participants
 * Last reply from: [Daniel](https://wordpress.org/support/users/ihenetudan/)
 * Last activity: [3 years, 1 month ago](https://wordpress.org/support/topic/advanced-cache-php-was-created-by-another-plugin/#post-16677677)
 * Status: resolved