Support » Plugin: Yoast SEO » Fatal Error after update to v. 5.3.2

  • Resolved bubencode


    Got the below error right after I have updated my site to the latest version 5.3.2

    Fatal error: Uncaught Error: Call to undefined method WPSEO_JSON_LD::register_hooks() in /var/www/html/wp-content/plugins/wordpress-seo/frontend/class-frontend.php:159 Stack trace: #0 /var/www/html/wp-content/plugins/wordpress-seo/frontend/class-frontend.php(197): WPSEO_Frontend->__construct() #1 /var/www/html/wp-content/plugins/wordpress-seo/inc/wpseo-functions.php(17): WPSEO_Frontend::get_instance() #2 /var/www/html/wp-includes/class-wp-hook.php(298): initialize_wpseo_front(”) #3 /var/www/html/wp-includes/class-wp-hook.php(323): WP_Hook->apply_filters(NULL, Array) #4 /var/www/html/wp-includes/plugin.php(453): WP_Hook->do_action(Array) #5 /var/www/html/wp-settings.php(448): do_action(‘init’) #6 /var/www/html/wp-config.php(126): require_once(‘/var/www/html/w…’) #7 /var/www/html/wp-load.php(37): require_once(‘/var/www/html/w…’) #8 /var/www/html/wp-blog-header.php(13): require_once(‘/var/www/html/w…’) #9 /var/www/html/index.php(17): require(‘/var/www/html/w…’) #10 {main} thrown in /var/www/html/wp-content/plugins/wordpress-seo/frontend/class-frontend.php on line 159

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

Viewing 4 replies - 1 through 4 (of 4 total)
  • With me the Yoast SEO plugin has been deactivated and has been removed from the website.

    Plugin Support jerparx


    @bubencode @ron5

    These types of errors typically appear when your website or server have aggressive cache that is not cleared during or after the upgrade process. Please try clearing the cache before installing and after upgrading Yoast SEO.

    Removing which cache? There is cache on the webserver and browser cache.

    Thanks @jerparx – as you suggested, clearing of cache both on server and on CDN helped with this issue.

    • This reply was modified 1 year, 6 months ago by  bubencode.
Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Fatal Error after update to v. 5.3.2’ is closed to new replies.