Get a big ‘error’ page.
I can’t be 100% sure without knowing more about the error, but it could be linked to this issue we’ll fix in the next Jetpack release:
https://github.com/Automattic/jetpack/pull/3738
If you’d like, you could try to apply the patch on your site, and let me know how it goes!
If that doesn’t help, could you tell me more about the error?
Thanks!
The last few sites I have gotten around to updating the plugin – as soon as I update there is a major error now and the only way to get the site working again at all is to remove the plugin via FTP.
It may be something to do with the hosting server I’m on (ipage.com) but every site I use it on except 1 has now broken, irregardless whether its the only plugin active or not, or what theme I’m using. For a while, sites wouldn’t break using Jetpack until I tried to deactivate it – then everything dies. Again, only fix was to go in by FTP and delete it. Unfortunately I don’t have time to problem solve this stuff – just easier to delete and get on with work.
Thanks for the report. Do you happen to use the same plugins on each one of your sites? If so could you post a list here?
If you ever get around to debug the issue, 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 );
}
Your wp-config.php file may already include a line that says “define(‘WP_DEBUG’, false);”. You can remove it, and replace it by the code above.
Once you’ve done so, try to reproduce the error, and then 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!
