Jetpack: 404:PAGE NOT FOUND

  • Resolved camfa9

    (@camfa9)


    7 years, 4 months ago

    I know there are any number of Topics that discuss this issue but there doesn’t seem to be any fix that doesn’t involve major coding efforts. Seems that Jetpack itself is a problem now, but it wasn’t a problem in May 2017 when I set up the website for my client, eresbooks.com. Nor was it a problem in April, when I set up a website for client, deepcaster.com.

    This latest version of Jetpack causes problems with accessing Appearance>Customize in particular. I’ve only found one solution and that is to deactivate Jetpack, work on Appearance>Customize and then activate Jetpack again. The site works fine but going back to Appearance>Customize returns this message: “This is somewhat embarrassing, isn’t it?” and this is on a site using a year theme: Twenty Eleven

    My clients won’t be using the Dashboard so they’ll never see this, but I don’t think it’s a satisfactory solution. Jetpack seems to have a bug that hasn’t been addressed.

    For now, I will switch between Deactivate and Activate with Jetpack, as necessary, but one day, I hope Automattic will address the issue.

    Otherwise, thank you for all your hard work!

    The page I need help with: [log in to see the link]

Viewing 1 replies (of 1 total)
  • Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic ??

    That is interesting, thanks for the report! It should definitely not happen.

    I can’t seem to reproduce on a test site running Twenty Eleven right now, so I wonder if this may be caused by a conflict with another plugin. Do you use the same set of plugins on all the sites where you ran into the problem?

    It might be worth digging into this a bit 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, reproduce the error, and then 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!

Viewing 1 replies (of 1 total)
  • The topic ‘Jetpack: 404:PAGE NOT FOUND’ is closed to new replies.