• Resolved siutouamy

    (@siutouamy)


    I’ve been reading about the problems people are having with the latest Jetpack update. Mine is installing correctly, but it makes the site render a 500 Error. Trying to get it reversed now ??

Viewing 3 replies - 16 through 18 (of 18 total)
  • Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic ??

    @bizbookscloud @mrmikedavis If you’re willing to give the update another try, could you add the following to your site’s wp-config.php file first?

    
    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 update Jetpack again. If the error comes back, check the wp-content/debug.log file for errors, and paste the results here. You can then replace define('WP_DEBUG', true); by define('WP_DEBUG', false); in the code above.

    Thanks!

    Anonymous User 14230037

    (@anonymized-14230037)

    Thanks for the reply @jeherve

    I have a couple demo sites where I may try the debug, but as for a live production site, no way. I would not recommend that or auto update plugins at all.

    In looking at the sites that were impacted, the common feature is a caching program, either W3 Total Cache or WP Rocket, and all were on shared servers.

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic ??

    @bizbookscloud @mrmikedavis If you’re willing to give Jetpack another try, could you try the following?

    Start by adding 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, 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!

Viewing 3 replies - 16 through 18 (of 18 total)
  • The topic ‘500 Error with Jetpack 4.8 Update’ is closed to new replies.