Back to Community

Fixing the 'WP Super Cache caching was broken but this has been fixed!' Warning

15 threads Sep 16, 2025 PluginWp super cache

Content

If you're seeing a persistent warning message in your WordPress dashboard stating "Warning ! WP Super Cache caching was broken but this has been fixed!", you're not alone. This is a common issue that can prevent your site from caching properly and cause frustration. This guide will explain why it happens and walk you through the most effective solutions.

What Causes This Warning?

The warning typically appears when the plugin's core file, advanced-cache.php, cannot properly load another essential file, wp-cache-phase1.php. This break in the chain prevents the caching mechanism from starting correctly. The message indicates that WP Super Cache has attempted an automatic fix by recreating the advanced-cache.php file and correcting the WPCACHEHOME path in your wp-config.php file. However, this fix can sometimes be temporary, and the error returns, especially after logging out and back into your site.

Common Solutions to Try

1. Manually Recreate the Configuration

Sometimes, the automatic fix needs a manual push. The most reliable method is to completely reset the plugin's configuration.

  1. Using your hosting control panel or an FTP client, navigate to the wp-content directory.
  2. Locate the file wp-cache-config.php.
  3. Rename this file to something like wp-cache-config.php.old. This will temporarily disable WP Super Cache.
  4. Go to your WordPress admin dashboard and navigate to Settings > WP Super Cache.
  5. The plugin will guide you through the setup process again, recreating all necessary files with the correct paths. This often resolves the corrupted configuration for good.

2. Check for Plugin Conflicts

As seen in the sample threads, other optimization plugins can sometimes interfere with WP Super Cache's file operations. A notable example was a bug in an older version of the WP-Optimize plugin.

  • Temporarily disable other caching or optimization plugins (e.g., LiteSpeed Cache, WP-Optimize).
  • Check if the warning disappears. If it does, reactivate your other plugins one by one to identify the culprit. You should generally only have one caching plugin active at a time.
  • Ensure all your plugins, especially those related to performance, are updated to their latest versions.

3. Verify File Permissions

WordPress and WP Super Cache need the correct permissions to create and write to files in the wp-content and wp-content/cache directories.

  • Using FTP or your host's file manager, check that the wp-content directory and its subfolders have write permissions (typically 755 for folders and 644 for files). Your hosting provider can assist with this if you are unsure.
  • Ensure the advanced-cache.php file exists in wp-content/ and that the WP_CACHE constant is defined in your wp-config.php file.

What If the Problem Persists?

If you continue to see the warning after trying these steps, the issue might be more specific to your server environment. It's recommended to search for or create a new thread on independent troubleshooting forums, detailing your specific hosting setup and any error logs from your server, which can provide crucial clues for further diagnosis.

Related Support Threads Support