WP 5.2 detects erros and restrict admin access

  • Resolved maleen

    (@maleen)


    4 years, 5 months ago

    Error Details
    =============
    An error of type E_ERROR was caused in line 452 of the file /wp-content/plugins/wordpress-seo/admin/class-admin.php. Error message: Uncaught Error: Class ‘WPSEO_HelpScout’ not found in /wp-content/plugins/wordpress-seo/admin/class-admin.php:452
    Stack trace:
    #0 /wp-content/plugins/wordpress-seo/admin/class-admin.php(116): WPSEO_Admin->get_helpscout_beacon()
    #1 /wp-content/plugins/wordpress-seo/admin/class-admin-init.php(31): WPSEO_Admin->__construct()
    #2 /wp-content/plugins/wordpress-seo/wp-seo-main.php(421): WPSEO_Admin_Init->__construct()
    #3 /wp-includes/class-wp-hook.php(288): wpseo_admin_init(”)
    #4 /wp-includes/class-wp-hook.php(312): WP_Hook->apply_filters(NULL, Array)
    #5 /wp-includes/plugin.php(478): WP_Hook->do_action(Array)
    #6 /wp-settings.php(392): do_action(‘plugins_loaded’)
    #7 /wp-config.php(110): require_once(‘/opt/bitnami/ap.

    i have skipped the front url extension

Viewing 4 replies - 1 through 4 (of 4 total)
  • Filip Markovski

    (@philipberovo)

    4 years, 5 months ago

    Also on some themes, after update it breaks the classic editor. My website with this theme: World Wide, after the new update, I cant switch from visual to text editor.

    First time I got the error like you, and I though it was because of this update error. I restored the previous version, then the second time the update passed without error, but I had my editor bugged again. Waiting for next version to fix this issue.

    mommykatandkids

    (@mommykatandkids)

    4 years, 4 months ago

    I received a similar error running Wordprss 5.2.4. I also can’t properly use the Classic editor anymore.

    Error Details
    =============
    An error of type E_ERROR was caused in line 502 of the file /www/wp-content/plugins/wordpress-seo/wp-seo-main.php. Error message: Uncaught Error: Class ‘Yoast_Alerts’ not found in /www/wp-content/plugins/wordpress-seo/wp-seo-main.php:502
    Stack trace:
    #0 /www/wp-content/plugins/wordpress-seo/wp-seo.php(48): require_once()
    #1 /wordpress/wp-settings.php(365): include_once(‘/www/wp-content…’)
    #2 /www/wp-config.php(105): require_once(‘/wordpress/wp-s…’)
    #3 /wordpress/wp-config.php(5): require(‘/www/wp-config….’)
    #4 /wordpress/wp-load.php(37): require_once(‘/wordpress/wp-c…’)
    #5 /wordpress/wp-admin/admin-ajax.php(22): require_once(‘/wordpress/wp-l…’)
    #6 {main}
    thrown

    Plugin Support devnihil

    (@devnihil)

    4 years, 4 months ago

    @maleen Can you please confirm you are using the most recent Yoast v12.6.2? You can learn more about updating here: https://kb.yoast.com/kb/how-can-i-update-my-free-plugin/

    Also, can you confirm you are using WordPress 5.3? You can check by clicking on the W in the top left and selecting About. If you need to update, please check with your host provider. Please know that if you are using an older version of WordPress Core you may experience unexpected behavior with Yoast. This guide explains more: https://yoast.com/why-we-dont-support-old-wordpress-versions/

    @mommykatandkids Please create a new issue if you are experiencing a similar problem as this helps us in tracking as this can be caused by many different variables (WordPress version, other plugins, etc).

    Plugin Support amboutwe

    (@amboutwe)

    4 years, 4 months ago

    This thread has been marked as resolved due to a lack of activity.

    You’re always welcome to re-open this topic. Please read this post before opening a new request.

    Thanks for understanding!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘WP 5.2 detects erros and restrict admin access’ is closed to new replies.