Fatal error Jetpack

  • Resolved aseverirene

    (@aseverirene)


    4 years, 5 months ago

    Hi there,

    This message was sent by the site perfecteburen.nl:

    "Als je hulp nodig hebt met dit probleem, kan je gevraagd worden om de volgende informatie:
WordPress versie 5.4.2
Huidig thema: Hueman-child (versie 1.0)
Huidige plugin: Jetpack by WordPress.com (versie 8.6.1)
PHP versie 7.3.19

Foutdetails
===========
Een fout van het type E_ERROR werd veroorzaakt op regelnummer 84 van het bestand /home/perfec1q/public_html/wp-content/plugins/jetpack/vendor/automattic/jetpack-sync/src/class-main.php. Foutmelding: Uncaught Error: Class 'Automattic\Jetpack\Sync\Health' not found in /home/perfec1q/public_html/wp-content/plugins/jetpack/vendor/automattic/jetpack-sync/src/class-main.php:84
Stack trace:
#0 /home/perfec1q/public_html/wp-includes/class-wp-hook.php(287): Automattic\Jetpack\Sync\Main::on_plugins_loaded_late('')
#1 /home/perfec1q/public_html/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters(NULL, Array)
#2 /home/perfec1q/public_html/wp-includes/plugin.php(478): WP_Hook->do_action(Array)
#3 /home/perfec1q/public_html/wp-settings.php(403): do_action('plugins_loaded')
#4 /home/perfec1q/public_html/wp-config.php(90): require_once('/home/perfec1q/...')
#5 /home/perfec1q/public_html/wp-load.php(37): require_once('/home/perfec1q/...')
#6 /home/perfec1q/public_html/wp-admin/admin.php(34): require_once('/home/perfec1q/...')
#7 /home/perfec1q/public_html/wp-admin/index.php(10): require_once('/home/perfec1q/...')
#8 {main}
 thrown"

    What oh what to do?

    Kind regards,

    • This topic was modified 4 years, 5 months ago by Jan Dembowski.
    • This topic was modified 4 years, 5 months ago by Jan Dembowski. Reason: Formatting

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

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support darnelldibbles

    (@darnelldibbles)

    Hi there,

    As a first step here, would you please delete Jetpack and then reinstall it?

    Try the following exact steps for a completely fresh reinstallation:

    • From the wp-admin dashboard of your site, please go to Jetpack > Dashboard > Connections > Manage site connection from your left-hand menu.
    • Click the “Disconnect” button. If it’s already disconnected, you can skip to the next step.
    • Deactivate your Jetpack plugin by heading to Plugins > Installed Plugins and finding “Jetpack by WordPress.com.”
    • Completely uninstall Jetpack.
    • Reinstall the newest version of Jetpack.
    • Deactivate all of your plugins.
    • Activate only Jetpack.
    • Back in Jetpack > Dashboard > Connections > Manage site connection, Click the “Set up Jetpack” button and continue through the approval process.

    Please let me know the results of this troubleshooting and we can go from there. Thanks!

    Thread Starter aseverirene

    (@aseverirene)

    Hi there @darnelldibbles,

    Why oh why is there still no other solution for ‘deactivating all of your plugins’?? This is a very successful website, and I cannot just deactivate all of the plugins just to make 1 plugin work. When should I do that, btw?

    I’ll discuss it with these ladies and advise them different plugins instead of Jetpack…

    Thanks for your response, anyhow.

    Kind regards,
    Irene

    I am also running into the same problem. I have turned off all plugins and my site is still slow.

    I also have a site that this slow down started on last weekend and it is killing my traffic.

    Help.

    Plugin Support darnelldibbles

    (@darnelldibbles)

    Hi there,

    The more important step here is the fresh install of Jetpack. However, it is much easier to isolate the issue and eliminate any potential conflict that may be causing the issue when you disable your other plugins. But, feel free to just do the fresh install of the Jetpack plugin and see if it resolves the issue.

    https://jetpack.com/support/reconnecting-reinstalling-jetpack/

    Thanks,

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Fatal error Jetpack’ is closed to new replies.