Sorry about that!
Could you add the following to your site’s wp-config.php file?
define('WP_DEBUG', true);
if ( WP_DEBUG ) {
@error_reporting( E_ALL );
@ini_set( 'log_errors', true );
@ini_set( 'log_errors_max_len', '0' );
define( 'WP_DEBUG_LOG', true );
define('WP_DEBUG_DISPLAY', false);
define( 'CONCATENATE_SCRIPTS', false );
define( 'SAVEQUERIES', true );
}
Once you’ve done so, try installing Jetpack again, and as soon as you trigger the WSOD, check the wp-content/debug.log file for errors.
You can paste the results here. You can then replace define('WP_DEBUG', true); by define('WP_DEBUG', false); in the code above.
Thanks!
Hi Jeremy, thank you for getting back to me. I didn’t see your reply till now, but I had deleted Jetpack in the interim.
I’ll give it a go, and report back.
Hi Jeremy, you won’t believe this but I was unable to replicate the error today, after replicating it constantly throughout the last few days. Jetpack switched on just fine today.
What’s very interesting is that afterwards, I put my wp-config file the way it was (with error logging set to false), and tried to switch Jetpack off. Immediately I got a 502 error.
I renamed the Jetpack directory, rebooted PHP, and got the WSOD.
I went back to wp-config, put in the code you gave me earlier, tried accessing the dashboard, and all was well again.
I then turned Jetpack on and off without any issue. It almost seems as though the code you gave me for wp-config means the difference between having bugs and not having bugs. I don’t know if that makes any sense but I thought I should report it as accurately as possible in case it helps narrow down a potential bug.
That’s interesting indeed!
Could you try to remove each line inside the brackets in the code I gave you, one at a time, and let me know if a specific line happens to be solving your issue?
Thanks!
