• Resolved russwcm

    (@russwcm)


    So my client forwarded a ‘Technical Issue’ email to me today that was flagging Yoast as the culprit. I was working on the site as it goes and had updated Yoast to version 26.8 before the email arrived. I was able to keep working on the site and didn’t see any ‘Critical Error’. Nonetheless I though I’d post the issue here and see what the response is.

    WordPress version 6.9
    Active theme: Themify Ultra Child (version )
    Current plugin:  (version )
    PHP version 8.1.34

    Error Details (from email)
    ===================
    An error of type E_ERROR was caused in line 413 of the file /home/sites/11b/b/b6ed5ff479/public_html/wp-content/plugins/wordpress-seo/wp-seo-main.php. Error message: Uncaught Error: Class “WPSEO_Admin_Init” not found in /home/sites/11b/b/b6ed5ff479/public_html/wp-content/plugins/wordpress-seo/wp-seo-main.php:413
    Stack trace:
    #0 /home/sites/11b/b/b6ed5ff479/public_html/wp-includes/class-wp-hook.php(341): wpseo_admin_init(”)
    #1 /home/sites/11b/b/b6ed5ff479/public_html/wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters(NULL, Array)
    #2 /home/sites/11b/b/b6ed5ff479/public_html/wp-includes/plugin.php(522): WP_Hook->do_action(Array)
    #3 /home/sites/11b/b/b6ed5ff479/public_html/wp-settings.php(593): do_action(‘plugins_loaded’)
    #4 /home/sites/11b/b/b6ed5ff479/public_html/wp-config.php(110): require_once(‘/home/sites/11b…’)
    #5 /home/sites/11b/b/b6ed5ff479/public_html/wp-load.php(50): require_once(‘/home/sites/11b…’)
    #6 /home/sites/11b/b/b6ed5ff479/public_html/wp-admin/admin.php(35): require_once(‘/home/sites/11b…’)
    #7 /home/sites/11b/b/b6ed5ff479/public_html/wp-admin/plugins.php(10): require_once(‘/home/sites/11b…’)
    #8 {main}
     thrown

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

Viewing 1 replies (of 1 total)
  • Plugin Support Maybellyne

    (@maybellyne)

    Hello @russwcm,

    Thanks for sharing the error details. The error could have been generated during the update process and fixed itself. Since the functionality of the plugin or your website is not impacted, you can ignore it. If the error continues, do reach out again.

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.