• Resolved Alicadabra

    (@alicadabra)


    I have recently updated to Yoast 18.5 on two sites. The Site Health page for both is now inaccessible and triggers a Fatal Error.

    I note that a user with a similar issue (https://www.ads-software.com/support/topic/fatal-error-after-update-to-18-5/) was advised to update PHP to 7.4 or above. One of the sites where I’ve found this issue is already on PHP 7.4.28 (the other is 7.3.33 so that could be a factor there).

    In case it’s useful, here’s the error message that was emailed:

    An error of type E_ERROR was caused in line 240 of the file /home/###/public_html/wordpress/wp-content/plugins/wordpress-seo/src/integrations/admin/ryte-integration.php. Error message: Uncaught Error: Class 'Yoast\WP\SEO\Integrations\Admin\wfConfig' not found in /home/###/public_html/wordpress/wp-content/plugins/wordpress-seo/src/integrations/admin/ryte-integration.php:240
    Stack trace:
    #0 /home/###/public_html/wordpress/wp-content/plugins/wordpress-seo/src/integrations/admin/ryte-integration.php(181): Yoast\WP\SEO\Integrations\Admin\Ryte_Integration->wordfence_protection_enabled()
    #1 /home/###/public_html/wordpress/wp-content/plugins/wordpress-seo/src/integrations/admin/ryte-integration.php(154): Yoast\WP\SEO\Integrations\Admin\Ryte_Integration->request_indexability()
    #2 /home/###/public_html/wordpress/wp-content/plugins/wordpress-seo/src/services/health-check/ryte-runner.php(90): Yoast\WP\SEO\Integrations\Admin\Ryte_Integration->fetch_from_ryte()
    #3 /home/###/public_html/wordpress/wp-content/plugins/wordpress-seo/src/services/health-check/ryte-runner.php(75): Yoast\WP\SEO\Services\Health_Check\Ryte_Runner->fetch_from_ryte()
    #4 /home/###/public_html/wordpress/wp-content/plugins/
Viewing 8 replies - 1 through 8 (of 8 total)
  • Hi @alicadabra,

    Thank you so much for reaching out!

    We are aware of a bug where running WordFence and the latest Yoast SEO, would result in a fatal error on the Site Health page. Our development teams are working on releasing a hotfix as soon as possible. When the new version is released, please update to it and check if you can then visit the Site Health page without errors. Thank you for your patience!

    Ah, we just released version 18.5.1 including a fix for this fatal error. Please update to it and let us know if you’d still encounter it! ??

    Thread Starter Alicadabra

    (@alicadabra)

    Hi @jeroenrotty,
    Thanks for such a speedy reply – and the even better news that you’re already on the case fixing this! I have WordFence running on both sites so that makes sense. I’ll keep an eye out for the update and update asap.
    Thanks again.

    Thread Starter Alicadabra

    (@alicadabra)

    Wow, super speedy!

    I’ve just updated and everything is working again now.

    Thanks again for your help.

    Awesome, happy to hear it’s fixed!

    Have a great day!

    Thread Starter Alicadabra

    (@alicadabra)

    (Marking as resolved)
    ??

    @jeroenrotty
    I confirm that the problem is solved in all my clients’ sites, everything ok. Great support service. Thk’s

    Hello! We just updated our Yoast SEO plugin today and I received an email about this fatal error. Our website is still working fine currently, but I do not know if it will continue to do so with this error.

    Email Message:

    Since WordPress 5.2 there is a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email.
    
    In this case, WordPress caught an error with one of your plugins, Yoast SEO.
    
    First, visit your website (https://memfault.com/) and check for any visible issues. Next, visit the page where the error was caught (https://memfault.com/wp-admin/edit-comments.php) and check for any visible issues.
    
    Please contact your host for assistance with investigating this issue further.
    
    If your site appears broken and you can't access your dashboard normally, WordPress now has a special "recovery mode". This lets you safely login to your dashboard and investigate further.
    
    https://memfault.com/wp-login.php?action=enter_recovery_mode&rm_token=jl6HRyHKZOJehxJHlRWApn&rm_key=XklDOGFXKEKK1noxl2W7…
    
    To keep your site safe, this link will expire in 1 day. Don't worry about that, though: a new link will be emailed to you if the error occurs again after it expires.
    
    When seeking help with this issue, you may be asked for some of the following information:
    WordPress version 5.9.2
    Current theme: sightbox (version 1.0)
    Current plugin: Yoast SEO (version 18.5.1)
    PHP version 7.4.28
    
    Error Details
    =============
    An error of type E_ERROR was caused in line 60 of the file /nas/content/live/memfault/wp-content/plugins/wordpress-seo/admin/class-yoast-plugin-conflict.php. Error message: Uncaught Error: Class 'Yoast\WP\SEO\Config\Conflicting_Plugins' not found in /nas/content/live/memfault/wp-content/plugins/wordpress-seo/admin/class-yoast-plugin-conflict.php:60
    Stack trace:
    #0 /nas/content/live/memfault/wp-content/plugins/wordpress-seo/admin/class-plugin-conflict.php(41): Yoast_Plugin_Conflict::get_instance('WPSEO_Plugin_Co...')
    #1 /nas/content/live/memfault/wp-content/plugins/wordpress-seo/admin/class-plugin-conflict.php(53): WPSEO_Plugin_Conflict::get_instance()
    #2 /nas/content/live/memfault/wp-includes/class-wp-hook.php(307): WPSEO_Plugin_Conflict::hook_check_for_plugin_conflicts('')
    #3 /nas/content/live/memfault/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters(NULL, Array)
    #4 /nas/content/live/memfault/wp-includes/plugin.php(474): WP_Hook->do_action(Array)
    #5 /nas/content/live/memfault/wp-admin/admin.php(175): do_action('admin_init')
    #6 /nas/content/live/memfault/wp-admin/edit-comments.php(10): require_once('/nas/content/li...')
    #7 {main}
    thrown
Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Fatal error on Site Health page after update to 18.5’ is closed to new replies.