Fatal Error via 3.1

  • Resolved Kevin Geary

    (@cytkevin)


    6 years, 6 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 3 replies - 16 through 18 (of 18 total)
  • Plugin Author Sybre Waaijer

    (@cybr)

    Awesome ?? Cheers!

    Done the same thing to make it work once more.

    1. Logged in my host backend (using cPanel / FileManager in my case)
    2. Browsed to reach website root
    3. Accessed the plugins folder /wp-content/plugins/ in my case
    1. Renamed the /wp-content/plugins/autodescription/ to /wp-content/plugins/.autodescription/
    2. Logged in to WP backend
    3. Installed the new version of the plugin
    4. Reloaded the website to check if it is working – and it does
    5. Deleted .autodescription folder.

    Settings seems unchanged. Is there a chance something else must change to keep all the metadata (descriptions etc) the same, for SEO sake?

    Plugin Author Sybre Waaijer

    (@cybr)

    Hi @catalinfx,

    It took me a while to reply, so I could get all my facts straight.

    It’s great to hear you’ve been able to recover the website! My apologies for the inconvenience to you, too.

    The settings are slightly different in this update. They shouldn’t have been reset; but, they should’ve been upgraded.

    Here’s what you should know.

    Page meta settings:

    • Nothing changed.

    Term meta settings:

    • Nothing changed.

    Site SEO settings:

    • Titles:
    • Internally, the title seperator is now called separator (note the typo).
    • “Strip HTML tags from generated titles?” is new, and should be turned off for old sites, but on for new sites.
    • “Automatically generate description?” is new and should be turned on by default.
    • Attachment Robots settings (noindex, nofollow, noarchive) have been upgraded to “Post Type” meta settings, as the Media type.
    • Sitemaps:
    • “Sitemap Query Limit” is new, and it should be set to 1200 by default.
    • “Add <priority> to the sitemap?” is new, and it should be turned on for old sites, off for new sites.

    That’s it! Various other settings, like “Add additions to automated description?” are now disabled by default on new sites.
    You can fish for these changes by looking for colored checkboxes. They are visible in Chrome, Firefox, and Safari. Green-bordered settings are enabled by default, red-bordered settings ought not to be enabled.

    If you’re encountering issues (that aren’t related to this fatal error), I’d like to ask you to open a new topic. ??

    I hope this helps!

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