Tag Info

Hot answers tagged

15

To get WordPress to display errors, edit the wp-config.php file to say define( 'WP_DEBUG', true ); By default, this is set to false and should be towards the bottom of the file. That will allow you to see which errors are being produced. Also, whitespace at the end of files almost never causes the WSOD; that's what causes the 'Headers already sent' ...


11

There is a bug in WordPress 3.3.1 causing the issue. It may affect other versions as well. To solve the issue you can update WordPress to the current stable release and do integration testing afterwards. Or you can do a quick bug fix. To fix the bug: Open file blog/wp-admin/includes/screen.php in your favorite text editor. On line 706 find the following ...


5

I have had the white screen of death several times. If you have tried disabling your plugins and that doesn't work then move on to your theme. Test with the Twenty Ten Theme. If the problem goes away then your theme is at fault. Problems to look for in your theme: Unescaped Characters can cause problems. Change @ for @ Blank Space at the end ...


5

A white screen of death is typically a fatal PHP error, most of the time due to a syntax error. This often sends no errors to the browser. Some things you can do: Turn on PHP error_log in your php.ini file and set the error_reporting levels. http://php.net/manual/en/errorfunc.configuration.php Error info: ...


5

There's not one if you didn't set one up. The codex has a good example of how to do this. <?php @ini_set('log_errors','On'); @ini_set('display_errors','Off'); @ini_set('error_log','/home/example.com/logs/php_error.log'); /** * This will log all errors notices and warnings to a file called debug.log in * wp-content (if Apache does not have write ...


2

Fatal errors point to bad syntax, or bad naming conventions. WordPress does a good job of not activating plugins that throw fatal errors. However, once a plugin is activated, all bets are off. If you've created a function or a class, it's best to follow good naming conventions and namespace properly. For example, a function called post_extras() would not be ...


2

If you have ftp access to your site, go to the root. There is a line in wp-config.cfg: define('WP_DEBUG', false); Switch it to: define('WP_DEBUG', true); Upon returning to one of the blank pages, you'll notice an error message which can shed some light on what is going wrong. From there you may either correct the issue, or bring that error back here ...


1

I think is an problem of php code, maybe in your functions.phg of the theme. Start debugging feature in WP and see the error messages. add this to wp-config.php or change the constant in the file. define( 'WP_DEBUG', TRUE ); Also i think, read this question and his answers, many solutions for the problem.


1

add if ( isset($_GET['debug']) && $_GET['debug'] == 'debug') define('WP_DEBUG', true); to your wp-config.php file. then visit your site http://www.cleanupisrael.org.il?debug=debug you should get an error message instead of just a blank screen. if that fails, then disable all the plugins and re-enable them one by one. not fun, but should tell ...


1

Add the following to wp_config.php: define( 'WP_DEBUG', true ); Reset the Plugins folder Revert to the default Theme (currently Twenty Eleven), using a similar method to the Plugin-reset step (just be sure that the only Theme available in /wp-content/themes/ is twenty-eleven) If your site is restored, great! If not, you likely have some sort of server or ...


1

Something I find super helpful is a plugin called Debug Bar. Really helpful for showing what actions are being run, also shows notices and warnings, etc. Super helpful to have in a dev environment. I'm not the developer of the plugin btw. Debug Bar Adds a debug menu to the admin bar that shows query, cache, and other helpful debugging information. ...


1

It may be an issue because there is a space at the end of wp-config.php file or function.php file. for more info see in http://creativedev.in/2012/02/blank-screen-of-wordpress-admin-panel/


1

To all the folks who get this kind of error a must check option. turn on error reporting if you have commented the lines in your wp-config.php @ini_set('display_errors','Off'); and than check for error. if it has the error like this PHP Warning: Cannot modify header information - headers already sent by (output started at /[server ...



Only top voted, non community-wiki answers of a minimum length are eligible