• Super Cache seems to be creating a new advanced-cache.php file in my wp-content folder every time I reload a page, and gives the following message:

    “Warning! WP Super Cache caching was broken but has been fixed! The script advanced-cache.php could not load wp-cache-phase1.php. The file /home/[my host name]/public_html/wp-content/advanced-cache.php has been recreated and WPCACHEHOME fixed in your wp-config.php. Reload to hide this message.”

    Except, it hasn’t been fixed. Otherwise, reloading the page would hide the message.

    I’ve been trying to resolve this for several hours, now, but to no avail. Here are the steps I’ve taken (besides googling around in vain for a solution) towards resolving this problem:

    I’ve worked through all 28 troubleshooting steps on the FAQ page. Some notes on those…

    7 & 14. “Look in wp-content/cache/supercache/. Are there directories and files there?” “Make sure wp-content/cache/wp_cache_mutex.lock is writable by the web server if using coarse file locking.”

    No such directory or file exist. I’m assuming they haven’t been created because the caching engine isn’t loading

    18 & 28. Open the file wp-content/advanced-cache.php in your favourite editor. Is the path to wp-cache-phase1.php correct? This file will normally be in wp-content/plugins/wp-super-cache/. If it is not correct the caching engine will not load.

    I’ve repeatedly checked to make sure the path is correct. It looks like this:

    /home/[my host name]/public_html/wp-content/plugins/wp-super-cache/

    And in the file, like this:

    '/home/[my host's name]/public_html/wp-content/plugins/wp-super-cache/' . 'wp-cache-phase1.php'

    This is definitely the correct path to the file—I’ve checked numerous times. I’ve tried joining the dot-separated strings, as a sanity check. I’ve also tried leaving the WPCACHEHOME variable in the file in the plugin/wp-super-cache folder, which is replaced with the path upon reloading the settings page, but it makes no difference. Modifying both the file in the wp-super-cache and the wp-content directories also doesn’t matter. Yet, the settings page says “if [the path] is not correct the caching engine will not load.” Additionally, I carefully checked permissions for correctness.

    I’ve defined the necessary variables to the wp-config file.

    No messages appear in the error logs.

    Strangely enough, installation on my development mirror went off without a hitch, but I haven’t the foggiest idea why it’s such a challenge here.

    Here’s what I’m running BTW:

    WordPress 4.1.1 with the Law Business theme by CMS Masters
    WP Super Cache 1.4.4
    CentOS 6.5 on a VPS on Dreamhost

    My site is galiherlaw.com

    Any help would be appreciated very much. Mahalo!

    https://www.ads-software.com/plugins/wp-super-cache/

Viewing 2 replies - 1 through 2 (of 2 total)
Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘"WP Super Cache caching was broken but has (NOT) been fixed"’ is closed to new replies.