WP Super Cache causes White Screen
-
After making changes to WP-Super-Cache(mostly selecting recommended settings in Advanced tab), I get WordPress White Screen.
I renamed folder >plugins>WP-Super-Cache to WP-Super-Cache_ORG in order to deactivate WP-Super-Cache, and no more White Screen.However, when I do a fresh install of WP-Super-Cache, I get the White Screen again. I suspect the DB is persisting a setting or two.
I would really like to get WP-Super-Cache back up and running.
Any Ideas?
Thanks in advance.
-
Same problem here I get WordPress White Screen,
i can’t deactivate it. Help!Thanks!
I am having all of the the same issues above and it’s having some pretty major repercussions. Any word on this?
I suspect the DB is persisting a setting or two.
Most of the settings seem to be in
/wp-content/wp-cache-config.php
So you can change the suspicious setting directly in that file before reinstalling. (Or delete the file to reset all.)
Tom
Same problem here.
To ymarkable: to deactivate WP SuperCache in this case, you have to do three things via FTP. If you don’t know how to use FTP, ask your hosting company for assistance:
(1) Open wp-config.php and delete the following lines:
define(‘WP_CACHE’, true); //Added by WP-Cache Manager
define( ‘WPCACHEHOME’, ‘[some path name on your server to your WP installation]’ ); //Added by WP-Cache Manager(2) Open your wp-content folder and delete two files:
advanced-cache.php
wp-cache-config.php(3) Inside wp-content folder, open your Plugins folder. Scroll down and delete the wp-SpamShield folder in its entirety.
If you only do the first or the second steps, the plugin will eventually try to “heal” itself and restore the white screen.
What I haven’t been able to figure out is what is causing the white screen. The only clue I have so far (beyond what others have posted here) is that when I visit the WP-SuperCache page under Dashboard > Settings and click one of the tabs, I end up getting a standard 404 page not found on the front-end website.
@vahost: Did you mean delete the /wp-super-cache/ folder, or were you thinking that WP-SpamShield was having an issue with your WP Super Cache install? If the latter, I’ll be happy to help with that.
@summergs1,ymarkable,sarahp13,ecdltf,vahost: Whenever you get a white screen in WordPress, the best way to diagnose it is to turn on WP_DEBUG. It’s a debugging mode built into WordPress, and is very useful tool when you have a situation like this come up. It will tell you where there are code errors, and help if you have plugin conflicts. To use WP_DEBUG, do the following:
First back up your
wp-config.php
file in your WordPress directory, then open it up:Look for the line that says
define('WP_DEBUG', false);
and replace it with:// Turns WordPress debugging on define('WP_DEBUG', TRUE); // Tells WordPress to log everything to the /wp-content/debug.log file define('WP_DEBUG_LOG', TRUE); // Doesn't force the PHP 'display_errors' variable to be on define('WP_DEBUG_DISPLAY', FALSE); // Hides errors from being displayed on-screen @ini_set('display_errors', 0);
(When you’re done debugging, just switch it back.) Most people only know about the first line
define('WP_DEBUG', TRUE);
, but that would turn on visible error display in your site, which is not desirable for a production site, as you can imagine. Adding the next few lines writes it to a log file instead, so it’s a very clean way to use WP_DEBUG. (Feel free to use this again in the future when you need to debug your site.)Then and recreate the error. Information will be logged to
/wp-content/debug.log
.In the
debug.log
file, you will usually see the exact reason you got the white screen.Some of most common reasons for white screens in WordPress are: undiagnosed PHP errors, memory issues, database issues, and old PHP versions.
Hope that helps!
Hey Scott,
I should have mentioned that in addition to these blank pages, I am actually unable to fully uninstall supercache (upon clicking uninstall, I get a blank page 100% of the time, unlike these other spotty errors).
Obviously removing the plugin folder is part of the deal, but what are the proper steps to go through to fully uninstall supercache?
Hi Sarah,
See my post above for the full set of steps when you have to do a manual uninstall.
Hi Scott,
To the best of my knowledge, this issue is unrelated to WP SpamShield.
Your debug suggestion was a good one, though. It helped me identify the fact that in my case the problem is due to an intermittent conflict between WP SuperCache and APC. I’ve instructed my server admins to replace APC with XCache.
@vahost: I agree..it shouldn’t be related. I just asked because in your step 3 you said delete the “wp-spamshield” folder…I think you meant delete the “wp-super-cache” folder.
@sarahp13,vahost: The method of uninstalling WP Super Cache described by vahost is mostly right but there are a couple of extra steps I’m going to add, and in a slightly different order. Here’s the entire process we recommend from start to finish:
- Using an FTP program (or through your site’s web admin panel), delete the
/wp-super-cache/
folder from within your/wp-content/plugins/
folder. - Open up your
wp-config.php
file (the main config file for WordPress), usually located in the folder your WordPress install resides in, and remove these two lines:
define(‘WP_CACHE’, true); //Added by WP-Cache Manager
define( ‘WPCACHEHOME’, ‘/xxxxxxxx/wp-content/plugins/wp-super-cache/’ ); //Added by WP-Cache Manager - Open up your
.htaccess
file in the folder your WordPress install resides in, and remove everything between these two lines:
# BEGIN WPSuperCache
# END WPSuperCacheThis step usually only applies if you are using the mod_rewrite method for caching (which is the fastest and best method for using WP Super Cache). Even if you’re not, it’s good to check this.
- Delete the
/supercache/
folder from within your/wp-content/cache/
folder. - Delete the
advanced-cache.php
andwp-cache-config.php
files from within your/wp-content/
folder.
This will completely uninstall WP Super Cache from your WordPress site.
Oh!
Duh!
Yes, remove the wp-supercache folder, not the wp-spamshield folder!
LOL, I figured that’s what you meant. ??
Hi @scott can I ask if the debug code would also log the cause of error when we are receiving 404 issue? We are encountering 404 constantly when someone post a new reply in our forum topics. Can we ask why we are having 404 issues quite often when someone is creating new reply? We fixed this issue by going to wp admin settings > permalinks and resaving the structure.
Thannks
Hi,
When you activated the super cache plugin all the js and css files are minified.So inorder to recover your site back you have replace all your css and js files with your backups.
For the cache,
you can add the below code to the .htaccess file.
<IfModule mod_deflate.c>
#The following line is enough for .js and .css
AddOutputFilter DEFLATE js css
AddOutputFilterByType DEFLATE text/plain text/xml application/xhtml+xml text/css application/xml application/rss+xml application/atom_xml application/x-javascript application/x-httpd-php application/x-httpd-fastphp text/html#The following lines are to avoid bugs with some browsers
BrowserMatch ^Mozilla/4 gzip-only-text/html
BrowserMatch ^Mozilla/4\.0[678] no-gzip
BrowserMatch \bMSIE !no-gzip !gzip-only-text/html
</IfModule># BEGIN EXPIRES
<IfModule mod_expires.c>
ExpiresActive On
ExpiresDefault “access plus 10 days”
ExpiresByType text/css “access plus 1 week”
ExpiresByType text/plain “access plus 1 month”
ExpiresByType image/gif “access plus 1 month”
ExpiresByType image/png “access plus 1 month”
ExpiresByType image/jpeg “access plus 1 month”
ExpiresByType application/x-javascript “access plus 1 month”
ExpiresByType application/javascript “access plus 1 week”
ExpiresByType application/x-icon “access plus 1 year”
</IfModule>
# END EXPIRES<IfModule mod_headers.c>
<FilesMatch “\.(js|css|xml|gz)$”>
Header append Vary Accept-Encoding
</FilesMatch>
<FilesMatch “\.(ico|jpe?g|png|gif|swf)$”>
Header set Cache-Control “public”
</FilesMatch>
<FilesMatch “\.(css)$”>
Header set Cache-Control “public”
</FilesMatch>
<FilesMatch “\.(js)$”>
Header set Cache-Control “private”
</FilesMatch>
<FilesMatch “\.(x?html?|php)$”>
Header set Cache-Control “private, must-revalidate”
</FilesMatch>
</IfModule>Thanks,
Anusha.@dekzgimutao: That’s a separate issue than the rest of this thread, so you should start a new thread about your specific issue. I don’t think WP_DEBUG would help you fix 404 errors.
Thanks @scott Allen I’ve posted a new topic here:
https://www.ads-software.com/support/topic/404-error-202?replies=1Yes, it wouldnt but would it show logs of errors including the 404 error?
Thanks
White Screen here as well.
So the only resolution to the white screen problem is to uninstall the plugin as described above including modifications to .htaccess? Or did I miss a more practical resolution?
- Using an FTP program (or through your site’s web admin panel), delete the
- The topic ‘WP Super Cache causes White Screen’ is closed to new replies.