Latest update Broke my site

Sorry about that. This may have been caused by some issues during the update process on your site.

Could you try to log in to your site via FTP or CPanel, delete the existing Jetpack plugin folder, and reinstall the plugin manually as explained here:
https://codex.www.ads-software.com/Managing_Plugins#Manual_Plugin_Installation

You’ll find the Jetpack plugin folder here:

wp-content
   plugins
     jetpack - DELETE THIS FOLDER

If you’re not sure how to do this, you can ask your hosting company for help. They should also have documentation explaining how to edit or remove files from your site using FTP or a File Manager in your admin panel.

Let me know how it goes.

Hi Jeremy,

Tried that but got the same error. It broke my backend.
Please fix the latest update or help me troubleshoot.

@hifunda Sorry to hear that. We will need to enable debugging to find out more.

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.

Let us know what you find.

Hi Jeremy,

Sorry but I am confused where to replace the code now. Shall I email you my wp-config.php file’s contents?

Please help.

• This reply was modified 7 years ago by Kathryn Presner. Reason: removed config file information
• This reply was modified 7 years ago by hifunda.

Hi hifunda!

Before we go any further, never ever post your whole wp-config.php file somewhere online, as it contains passwords and other information that could allow someone to gain access to your site.

Now, to answer your question, before we removed the pasted file, I noticed that you already have a define( 'WP_DEBUG', false ); line in your file. Simply do as Jeremy said: remove that line, and replace it with all of this:

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 );

}

Thanks!

Sure I realized and removed it thanks, Richard.

But I am confused because there is already a:

// Enable WP_DEBUG mode
define( 'WP_DEBUG', true );

in my file and not a :

define( 'WP_DEBUG', false );

Well great! The all you need to do is add the additional stuff that Jeremy mentioned, and leave the define( 'WP_DEBUG', true );

Ok thanks Richard I did that.

1. Before reactivating the Jetpack plugin to see the error, I already got these errors on the front and back end of my site: https://prnt.sc/h8jr9i

2. This time my backend didn’t crash with 500 error but I got the same error as above: https://prnt.sc/h8jryi, I am unable to paste the contents of my log file here as my browser crashes.

@jeremy: Please tell me what to do.
Are you sure others dont have such crashes after the recent jetpack update?

Hi again,

Go through your wp-config.php file, and make sure that you have define( 'WP_DEBUG_LOG', true ); and define( 'WP_DEBUG_DISPLAY', false ); listed only once. That will prevent those notices from appearing.

I double checked – they are listed only once. This is strange, perhaps a plugin is doing this?

Please let me know how to proceed.

Well, the error message states that it’s listed twice; did you a search through the file using a text editor, to make sure you didn’t miss it anywhere?

Yes that’s exactly what I did.
Can we move this support thread to Jetpack contact forms and continue?

I really need to continue using Jetpack as my image CDN..

You can certainly contact us directly, here:

https://jetpack.com/contact-support/