• Resolved dimal

    (@dimalifragis)


    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)
  • 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

    (@dimalifragis)

    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.

    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

    (@dimalifragis)

    Sure, it is Comet Cache (and its fork Rapid Cache).

    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.