Support » Plugin: The SEO Framework » Fatal Error

Viewing 12 replies - 1 through 12 (of 12 total)
  • Plugin Author Sybre Waaijer



    Another plugin may call The SEO Framework before it had a chance to initialize. Have you implemented filters or other code for TSF?

    If you haven’t, see if deactivating other plugins may resolve the issue. Through deduction, you should be able to find which one tries to interact too early.

    Do keep an eye out on other plugin updates; they might have already resolved the issue for you.

    Same for me, I’ve received the WP email about an issue with the plugin in the same line. The error is not visible anywhere so how can I know if it’s fixed after disabling other plugins?

    Thanks for your prompt reply.
    This immediately happened after the update to 4.0.1. I had updated other plugins at the same time so I deactivated all of the updated plugins and found TSF to be the culprit. No I have not implemented filters or other code for TSF.

    I have another website which I received the following email:

    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, The SEO Framework.

    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.

    Error Details
    An error of type E_COMPILE_ERROR was caused in line 157 of the file wp-content/plugins/autodescription/bootstrap/load.php. Error message: require(): Failed opening required /wp-content/plugins/autodescription/inc/classes/traits/enclose-core-final.class.php’ (include_path=’.:/usr/lib/php:/usr/local/lib/php’)

    Plugin Author Sybre Waaijer


    Thank you for staying persistent on this matter! It’s really appreciated to see others work with us.

    Now, I can affirm that this issue is due to another plugin trying to test for compatibility.

    Unfortunately, in doing so, the other plugin loads The SEO Framework before it had any say in the matter. In this, it can’t load the required trait, and the autoloader crashes.

    I can dive into why this is wrong (see footnote ‑), but that won’t help you πŸ™

    To help me find the causing plugin, I need the list of active plugins. Could you send those over to our contact page?

    Since WordPress 5.2, there’s an easy way to acquire this list:

    1. Go to /wp-admin/site-health.php?tab=debug.
    2. Hit “Copy site info to clipboard.”

    Seeing as more websites you’re using are affected, it’s helpful to have this information about both sites. It helps me match the plugins used, speeding up the search for errors tremendously.

    Hi @mairag, I’m glad you’re still around after all this time! Could you also send in those details listed above?

    Footnote ‑
    Plugins don’t always load in the same order, so the compatibility implementation is sporadic and unpredictable. Sometimes the compatibility works, but at other times it won’t. When it works, however, it may invoke autoloaders unintentionally, which is what is happening here. The fix is to use another compatibility checkpoint or at least use the plugins_loaded action-hook. We could also append trait-loading in our autoloader for a future update, but that won’t address the cause of this issue.

    Sent πŸ˜‰

    Sent for and

    Plugin Author Sybre Waaijer



    Thank you for all the details.

    The plugins that overlap on all three submitted sites are:
    – BackupBuddy by iThemes
    – WP-Optimize by Team Updraft & Co.

    Unfortunately, neither of these plugins seem to invoke this error. I dug through most other active plugins to find hints, and none of them try to act on The SEO Framework.

    If you can find a consistent pattern on when these errors occur, or if you know how to trigger it manually, that’d be most helpful.

    Due to the limited scope of this issue (2 valid reports out of 20,000 users = 0.01% affected), I’m considering this as an edge-case issue. I have a solution marked in the code already, but I haven’t had the time to implement it.

    I’ll keep my eye out for similar issues reported by other users.

    Plugin Author Sybre Waaijer



    I’ve decided to address this issue, although it won’t resolve the cause.

    From TSF v4.0.2, this issue should no longer occur. Cheers!

    I can confirm that my client experienced this error yesterday as well with their site and The SEO Framework. This is the exact Error Message:

    Error Details
    An error of type E_COMPILE_ERROR was caused in line 127 of the file /var/www/html/ Error message: require(): Failed opening required ‘/var/www/html/’ (include_path=’.:/usr/share/pear:/usr/share/php’)

    If you need more details, let me know.

    Plugin Author Sybre Waaijer


    Hi @santosfel5,

    That error could only occur on TSF v3.2.4… when files are mixed with TSF v4.0.x.

    Did this happen as you uploaded the new plugin files via FTP, and didn’t occur anytime since? If so, then you can safely ignore this issue.

    Otherwise, it seems that not all files have been uploaded correctly. Please reinstall the plugin; no settings will be lost in that process. Cheers!

    Plugin Author Sybre Waaijer



    TSF v4.0.2 has just been released, and the autoloader error should no longer spawn with it. If it does, do let me know! Cheers πŸ™‚

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘Fatal Error’ is closed to new replies.