An error of type E_ERROR was caused in line 13 of the file

  • Resolved Tamer Ziady

    (@tziady)


    4 years, 5 months ago

    Howdy!

    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 (*********************************************) and check for any visible issues. Next, visit the page where the error was caught (*********************************************) 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.

    *********************************************

    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.4.1
    Current theme: <*********************************************> (version 1.0)
    Current plugin: Yoast SEO (version 14.3)
    PHP version 7.0.32

    Error Details
    =============
    An error of type E_ERROR was caused in line 13 of the file ********************************************* Error message: Interface ‘Yoast\WP\SEO\Conditionals\Conditional’ not found

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

Viewing 7 replies - 1 through 7 (of 7 total)
  • WPChina

    (@wordpresschina)

    I have the same problem on multiple WordPress sites. Problem started about an hour ago.

    Thread Starter Tamer Ziady

    (@tziady)

    @wordpresschina I believe it may have something to do with the latest WordPress/Yoast update which I implemented last evening. This morning everyone is having issues.

    T

    WPChina

    (@wordpresschina)

    Thank you. Sites are crashing too. I rebooted and still saw this:

    # uptime
 04:32:49 up 14 min,  1 user,  load average: 63.38, 31.55, 13.10
    Plugin Support Jerlyn

    (@jerparx)

    Hi @wordpresschina @tziady ,

    We are sorry to hear about the error you are getting.

    This usually happens when the plugin files are cached and some old files are still used after updating the plugin. On occasions, this causes temporary errors that resolve themselves once the cache has been cleared.

    If the problem doesn’t resolve for you automatically, can you please try clearing the cache from your theme, plugin, server and CDN (e.g. CloudFlare)? If you are not sure how to clear the cache from a theme or plugin please speak to those authors. If you want to clear cache from the server, please speak to your host provider.

    Please let us know the results.

    Thread Starter Tamer Ziady

    (@tziady)

    This morning site is completely offline:

    Warning: include(/www/*************************************/htdocs/staging/wp-content/plugins/wordpress-seo/vendor/composer/../../src/conditionals/conditional.php): failed to open stream: No such file or directory in /www/*************************************/htdocs/staging/wp-content/plugins/wordpress-seo/vendor/composer/ClassLoader.php on line 444

    Warning: include(): Failed opening ‘/www/*************************************/htdocs/staging/wp-content/plugins/wordpress-seo/vendor/composer/../../src/conditionals/conditional.php’ for inclusion (include_path=’./:/usr/local/php7.0/lib/php’) in /www/*************************************/htdocs/staging/wp-content/plugins/wordpress-seo/vendor/composer/ClassLoader.php on line 444

    Fatal error: Interface ‘Yoast\WP\SEO\Conditionals\Conditional’ not found in /www/*************************************/htdocs/staging/wp-content/plugins/wordpress-seo/src/conditionals/admin-conditional.php on line 13
    There has been a critical error on your website.

    Learn more about debugging in WordPress.

    Plugin Support Michael Ti?a

    (@mikes41720)

    Hello @tziady

    We apologize for any issues that have occurred when updating the Yoast SEO plugin. Are you able to access your WordPress admin dashboard? If not, please do follow the steps in this article — https://yoast.com/help/white-screen-when-activating-or-updating-plugin/

    Since you’ve provided the WordPress and PHP versions previously and it all checks out, once you are able to regain access to your site, it’s likely that there is a plugin and/or theme conflict when activating Yoast SEO. We recommend that you perform a conflict check to indeed confirm if there is a conflict between the Yoast SEO plugin and one of your plugins and/or themes — https://yoast.com/help/how-to-check-for-plugin-conflicts/

    Plugin Support devnihil

    (@devnihil)

    We are going ahead and marking this issue as resolved due to inactivity. If you require any further assistance please create a new issue.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘An error of type E_ERROR was caused in line 13 of the file’ is closed to new replies.