Fatal Error via 3.1

  • Resolved Kevin Geary

    (@cytkevin)


    5 years, 7 months ago

    The 3.1 update is causing a fatal error. Plugin has to be disabled via FTP to get the site back. Then a re-install is disallowed by WordPress as it detects the fatal error.

    Error…

    “Fatal error: Uncaught Error: Class ‘WP_Site’ not found in /www/wp-content/themes/Divi/core/wp_functions.php:72 Stack trace: #0 /www/wp-content/plugins/autodescription/inc/classes/core.class.php(315): get_site() #1 /www/wp-content/plugins/autodescription/inc/classes/sitemaps.class.php(64): The_SEO_Framework\Core->current_blog_is_spam_or_deleted() #2 /www/wp-content/plugins/autodescription/inc/classes/sitemaps.class.php(78): The_SEO_Framework\Sitemaps->can_run_sitemap() #3 /www/wp-content/plugins/autodescription/bootstrap/activation.php(63): The_SEO_Framework\Sitemaps->rewrite_rule_sitemap() #4 /www/wp-content/plugins/autodescription/bootstrap/activation.php(27): The_SEO_Framework\_activation_setup_sitemap() #5 /www/wp-content/plugins/autodescription/bootstrap/load.php(156): require(‘/www/wp-content…’) #6 /www/wp-includes/class-wp-hook.php(286): The_SEO_Framework\_do_plugin_activation(”) #7 /www/wp-includes/class-wp-hook.php(310): WP_Hook->apply_filters(”, Array) #8 /www/wp-includes/plugin.php(453): WP_Hook->do_action(A in /www/wp-content/themes/Divi/core/wp_functions.php on line 72″

Viewing 15 replies - 1 through 15 (of 18 total)
1 2
  • Plugin Author Sybre Waaijer

    (@cybr)

    5 years, 7 months ago

    Hi @cytkevin,

    Which versions of Divi and WordPress are you using? I’ll triangulate why TSF is invoked like this on plugin activation via their theme.

    Thanks!

    • This reply was modified 5 years, 7 months ago by Sybre Waaijer. Reason: Also need to know the WP version
    Thread Starter Kevin Geary

    (@cytkevin)

    5 years, 7 months ago

    I’m currently using Divi 3.15 (latest version). I just updated. The fatal error happened before I updated. SEO Framework isn’t working with the updated version either.

    Plugin Author Sybre Waaijer

    (@cybr)

    5 years, 7 months ago

    Thanks, Kevin!

    I’m going to check it out right now; expect v3.1.1 soon with a fix!

    My apologies for the inconvenience, by the way 🙁

    Thread Starter Kevin Geary

    (@cytkevin)

    5 years, 7 months ago

    Thanks, is there a quick way I can download the previous version so I can get the plugin activated again?

    Plugin Author Sybre Waaijer

    (@cybr)

    5 years, 7 months ago

    Hi Kevin,

    There is 🙂

    At the bottom of the “Advanced” section of the plugin, you can download previous versions:
    https://wordpress.org/plugins/autodescription/advanced/

    Plugin Author Sybre Waaijer

    (@cybr)

    5 years, 7 months ago

    Alright, I’ve found the issue.

    Divi injects get_site() as a compatibility function, while it should only be loaded on WordPress Multisite networks. In our code, we assumed that this was always the case, thus we could resort using the function safely.

    I’ve forwarded this issue to them.

    I’m going to add another check (that’s safer) to prevent a crash with Divi.

    Plugin Author Sybre Waaijer

    (@cybr)

    5 years, 7 months ago

    A fix has been brought with v3.1.1 🙂

    Thanks for reporting this issue, and being so patient and kind, Kevin!

    Thread Starter Kevin Geary

    (@cytkevin)

    5 years, 7 months ago

    Happy to help make sure things are solid! Thanks for the quick fix 🙂

    simonjayprice

    (@simonjayprice)

    5 years, 7 months ago

    Not getting any fatal error info but getting a white screen and no access to the backend. Hosts are joining a roll back.

    Plugin Author Sybre Waaijer

    (@cybr)

    5 years, 7 months ago

    Hi @simonjayprice,

    My apologies for this inconvenience!

    White screens (without information) are seen with a fatal error when debugging is disabled.

    Are you using Divi? If so, then you should be able to upgrade safely to v3.1.1. Tell your hosts to keep an eye out if it crashes at v3.1.1 too.

    Link them to this topic: They’re free to contact me with debugging information if they have any.

    Thanks!

    Thread Starter Kevin Geary

    (@cytkevin)

    5 years, 7 months ago

    Update: 3.1.1 is working on my install.

    simonjayprice

    (@simonjayprice)

    5 years, 7 months ago

    We have tried rollbacks but still have a white screen and cannot get access to the backend.

    Plugin Author Sybre Waaijer

    (@cybr)

    5 years, 7 months ago

    Hi @simonjayprice,

    Could you contact your hosting provider, ask them to:

    1. Enable debugging via WP_DEBUG.
    2. Send the white screen report to me, here: https://theseoframework.com/contact/
    3. Delete the plugin via FTP, and then install the lastest version via the plugin installer.

    Thanks!

    simonjayprice

    (@simonjayprice)

    5 years, 7 months ago

    we cannot get access to the back end /wp-admin either can we upload the new updated plugin to the ftp.

    simonjayprice

    (@simonjayprice)

    5 years, 7 months ago

    right sorted it!

Viewing 15 replies - 1 through 15 (of 18 total)
1 2
  • The topic ‘Fatal Error via 3.1’ is closed to new replies.