Plugin Contributor
csonnek
(@csonnek)
Happiness Rocketeer 🚀
Hi there and sorry for the delay.
In Jetpack 4.8, we had added a lot of new files, most of which are new translation files for languages that have a considerable percentage of translations completed by our community members. Unfortunately, the extra language files caused updates to not complete properly on sites with limited resources that can’t fully process large zip files or copying lots of files when updating a plugin.
If you’re experiencing errors after updating to Jetpack due to an incomplete upload or update:
1. Using FTP, log into your site and navigate to and delete the /wp-content/plugins/jetpack/ folder.
2. Download the latest version of Jetpack here:
https://downloads.wordpress.org/plugin/jetpack.5.3.zip
3. Then, manually install the plugin via FTP/SFTP.
http://codex.wordpress.org/Managing_Plugins#Manual_Plugin_Installation
This process will most likely fix this problem for you.
If you still have trouble after manually updating over FTP/SFTP, please let me know and I’ll be happy to take a closer look.
You can also check with your hosting provider to see if they can upgrade your resource limit to accommodate for plugin or software updates on your site going forward.
Hey,
Thank you for the response and help. Sadly it did not do the trick. I did exactly what you proposed and still face the same problem. I think the resource limits should not be the problem, but I will tell my host.
Hi!
To confirm that the source of the problem does not come from a conflict with your theme or another plugin, it may be worth looking at your error logs first.
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 activate Jetpack again. When you start running into issues, check the wp-content/debug.log file for errors. That should tell you more about the problem. If nothing appears there, the problem may be caused by memory limits on your server.
You can then replace define('WP_DEBUG', true); by define('WP_DEBUG', false); in the code above.
I hope this helps.
