Title: FATAL ERROR after WP Supercache update
Last modified: August 24, 2017

---

# FATAL ERROR after WP Supercache update

 *  Resolved [nsnbc](https://wordpress.org/support/users/nsnbc/)
 * (@nsnbc)
 * [9 years ago](https://wordpress.org/support/topic/fatal-error-after-wp-supercache-update/)
 * Hello friends at Wordfence.
    10000s of WP websites are down today after WP Supercache
   provided an update on Aug 24. No response from developers. We cannot even log
   into our own admin area to delete the plugin and make this a Fatal Error for 
   WP Supercache (delete the plugin).
 * It’s not directly Wordfence related but it certainly is an issue that I believe
   you ought to be informed about. Lack of even most rudimentary quality assurance
   protocols – for example. Should be unacceptable in this community.
 * Also, if you could help with either contacting developers at WP Supercache and/
   or helping out with a solution that at least allows users to log in so we can
   delete this? Please?
 * We are plenty of people out here who cannot afford professional developers and
   who cannot understand easy – but for them totally un-understandable “jargon”.
   It’s terrible.
 * Thanks and looking forward
    Christof Lehmann
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Ffatal-error-after-wp-supercache-update%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

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

 *  Moderator [Jan Dembowski](https://wordpress.org/support/users/jdembowski/)
 * (@jdembowski)
 * Forum Moderator and Brute Squad
 * [9 years ago](https://wordpress.org/support/topic/fatal-error-after-wp-supercache-update/#post-9437660)
 * Side note: I’ve removed this topic from the pending queue but left the other 
   topic you’ve started as archived and not viewable.
 * Please do not make “demands” of free volunteers again. That includes demands 
   of plugin authors.
 *  [WFSupport](https://wordpress.org/support/users/wfsupport/)
 * (@wfsupport)
 * [9 years ago](https://wordpress.org/support/topic/fatal-error-after-wp-supercache-update/#post-9438975)
 * We’re sorry your having the issue with the WP Supercache plugin which we don’t
   make. Please understand we cannot officially offer support but we can make a 
   suggestion.
 * You could always follow these instructions on the plugin page at wordpress.org.
   
   Use ftp or your hosting control panel’s file manager to rename the **wp-super-
   cache **folder in **wp-content/plugins** to deactivate the plugin. Remove the
   WP_CACHE define from wp-config.php. It looks like **define( ‘WP_CACHE’, true );**
   Remove the Super Cache mod_rewrite rules from your **.htaccess** file. Remove
   the files **wp-content/advanced-cache.php** and **wp-content/wp-cache-config.
   php** Remove the directory **wp-content/cache/** Remove the renamed wp-super-
   cache directory from your plugins directory
 * If you have any other issues, reach out to the WP Supercache team for direction.
    -  This reply was modified 9 years ago by [WFSupport](https://wordpress.org/support/users/wfsupport/).

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

The topic ‘FATAL ERROR after WP Supercache update’ is closed to new replies.

 * ![](https://ps.w.org/wordfence/assets/icon.svg?rev=2070865)
 * [Wordfence Security - Firewall, Malware Scan, and Login Security](https://wordpress.org/plugins/wordfence/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wordfence/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wordfence/)
 * [Active Topics](https://wordpress.org/support/plugin/wordfence/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wordfence/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wordfence/reviews/)

 * 2 replies
 * 3 participants
 * Last reply from: [WFSupport](https://wordpress.org/support/users/wfsupport/)
 * Last activity: [9 years ago](https://wordpress.org/support/topic/fatal-error-after-wp-supercache-update/#post-9438975)
 * Status: resolved