Fatal error after 8.6.1

  • Resolved Rafael Fischmann

    (@rfischmann)


    4 years, 5 months ago

    I’m reverting back to 8.5 after 8.6.1 broke my site:

    Fatal error: Uncaught Error: Class 'Jetpack_Wizard' not found in /home/macmagazine/public_html/wp-content/plugins/jetpack/_inc/lib/admin-pages/class.jetpack-react-page.php:356 Stack trace: #0 /home/macmagazine/public_html/wp-content/plugins/jetpack/_inc/lib/admin-pages/class.jetpack-react-page.php(54): Jetpack_React_Page->show_setup_wizard() #1 /home/macmagazine/public_html/wp-includes/class-wp-hook.php(287): Jetpack_React_Page->jetpack_add_set_up_sub_nav_item('toplevel_page_j...') #2 /home/macmagazine/public_html/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters(NULL, Array) #3 /home/macmagazine/public_html/wp-includes/plugin.php(478): WP_Hook->do_action(Array) #4 /home/macmagazine/public_html/wp-content/plugins/jetpack/_inc/lib/admin-pages/class.jetpack-react-page.php(22): do_action('jetpack_admin_m...', 'toplevel_page_j...') #5 /home/macmagazine/public_html/wp-content/plugins/jetpack/_inc/lib/admin-pages/class.jetpack-admin-page.php(109): Jetpack_React_Page->add_page_actions('toplevel_page_j...') #6 /home/macm in /home/macmagazine/public_html/wp-content/plugins/jetpack/_inc/lib/admin-pages/class.jetpack-react-page.php on line 356

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter Rafael Fischmann

    (@rfischmann)

    Weird, even after reverting back to 8.5, a similar error persisted. Then I’ve renamed the plugin’s folder to force deactivate it, and after reactivation (even on 8.6.1), it seems to be fine now.

    What could have happened?

    Plugin Support KokkieH

    (@kokkieh)

    Hi there,

    If a reinstallation of the plugin fixed it, then most likely a file became corrupted during the update, or the update might have timed out at some point causing a file to only be downloaded partially. That’s just something that sometimes happen with plugin updates.

    I’m glad you were able to figure it out, but please let us know if something like this happens again.

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