• Resolved Gabor

    (@9abor)


    Hi there,

    Upon installing 14.1 my website crashed and emailed me automatically. Now this email is referring to Yoast SEO premium. Although I could go back to previous version, but looking for safely updating Yoast 14.1x as soon as possible.
    Thanks

Viewing 12 replies - 1 through 12 (of 12 total)
  • I’m getting same error… This is the email I received automatically below:

    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 Premium.
    […]
    When seeking help with this issue, you may be asked for some of the following information:
    WordPress version 5.4.1
    Current theme: Legacy (version 1.3)
    Current plugin: Yoast SEO Premium (version 14.1)
    PHP version 7.3.16-1+ubuntu18.04.1+deb.sury.org+1

    Thread Starter Gabor

    (@9abor)

    @tobyfoote – I guess it will be fixed soon – still there’s no reaction from the Yoast Team – I guess they’re busy 😉

    I got the same email message although it was Hungarian 🙂
    Gabor

    I spoke with WP Engine, who is my hosting company, and they reviewed. They think everything is ok. I did not get an error when updating on the WordPress site during upgrade to 14.1, but I did get the automatic email (posted earlier). I sent my automatic email to support@yoast.com for them to review and know about. I have never received an error from a Yoast upgrade, this is a first for me.

    Maybe my solution I posted will solve your problem ….

    Plugin Support devnihil

    (@devnihil)

    @9abor We’re sorry to hear you experienced that when updating the plugin. Would you be able to provide us with the log of the errors that occurred when the site crashed after the update?

    The site didn’t appear to crash. Instead, we got an automatic email from WordPress with details of the error. We never saw the error when updating inside of WordPress. @devnihil, are you part of Yoast support? If so, I sent the email to support@yoast.com.

    Thread Starter Gabor

    (@9abor)

    @devnihil I have already rolled back but my site’s symptoms including the automated email alert was exactly the same as it happened to @tobyfoote (only the email language was in Hungarian… that’s it)

    And yes the site after Fatal Error state was refressable and seemed no error message (only the email was sent) … but I went back via my server backup.

    Thanks

    Plugin Support devnihil

    (@devnihil)

    @tobyfoote Yes, I am part of the Yoast support team. I was able to find your email to us and it contained the error:

    Error Details
    =============
    An error of type E_ERROR was caused in line 459 of the file /nas/content/live/tobyfoote/wp-content/plugins/wordpress-seo-premium/wp-seo-main.php. Error message: Uncaught Error: Class 'Yoast_Alerts' not found in /nas/content/live/tobyfoote/wp-content/plugins/wordpress-seo-premium/wp-seo-main.php:459
    Stack trace:
    #0 /nas/content/live/tobyfoote/wp-content/plugins/wordpress-seo-premium/wp-seo-premium.php(73): require_once()
    #1 /nas/content/live/tobyfoote/wp-settings.php(371): include_once('/nas/content/li...')
    #2 /nas/content/live/tobyfoote/wp-config.php(122): require_once('/nas/content/li...')
    #3 /nas/content/live/tobyfoote/wp-load.php(37): require_once('/nas/content/li...')
    #4 /nas/content/live/tobyfoote/wp-admin/admin.php(34): require_once('/nas/content/li...')
    #5 /nas/content/live/tobyfoote/wp-admin/plugin-install.php(16): require_once('/nas/content/li...')
    #6 {main}
    thrown

    Looking at the error details, we observe that a class that is no longer available in the plugin, although ‘Yoast_Alerts’ is still being referenced. 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) before and after updating Yoast SEO? 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.

    When I upgraded my site to 14.1 the whole site went HTTP 500 and I couldn’t access it at all. I got the same fatal error email that some others have mentioned. I had to restore from a backup using FTP just to be able to get into the Admin console.

    I’m a software developer and I get wanting to refactor and get rid of code cruft, but having that serious a fatal error because an old version of a file was cached is pretty brutal.

    @joelabrown

    We apologize for the difficulties the plugin is causing for you. If you continue to experience issues we are happy to help! Per the forum guidelines, we ask that you please create separate topics for the issues you are experiencing.

    That way it’s easier to track issues and provide assistance on your specific concerns on your specific site. Plus, you will get your own alerts for the issue rather than someone else’s. You may make a new topic here: https://wordpress.org/support/plugin/wordpress-seo/#new-post.

    @9abor
    We will keep this thread open for another week after which we will close in order to keep the overview.

    Plugin Support Jerlyn

    (@jerparx)

    Hi,

    We’re closing this thread because we haven’t heard back from you in a while. Should you have further questions, please open a new thread.

    Cannot access posts via wordpress admin panel after upgrading to version 14.5

    “This page isn’t working saratogabars.com is currently unable to handle this request.
    HTTP ERROR 500”

    Disabled and all okay.

    Received following error in cPanel:

    “[Thu Jul 16 15:27:53.331584 2020] [lsapi:error] [pid 1027586:tid 47092869527296] [client 172.100.205.47:54782] [host saratogabars.com] Backend fatal error: PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 962560 bytes) in /home/gin0k/public_html/network/saratogabars.com/wp-includes/functions.php on line 4609\n, referer: https://saratogabars.com/wp-admin/plugins.php?plugin_status=all&paged=1&s”

    Received 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, Yoast SEO.

    First, visit your website (https://saratogabars.com/) and check for any visible issues. Next, visit the page where the error was caught (https://saratogabars.com/wp-admin/edit.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://saratogabars.com/wp-login.php?action=enter_recovery_mode&rm_token=GNDSI0F7nt3L5Gijc3gEoO&rm_key=0G9vjOxd4Dhg8qmapRqprj

    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.2
    Current theme: Freak Child (version 1.0.0)
    Current plugin: Yoast SEO (version 14.5)
    PHP version 7.4.5

    Error Details
    =============
    An error of type E_ERROR was caused in line 92 of the file /home/gin0k/public_html/network/saratogabars.com/wp-content/plugins/wordpress-seo/src/helpers/blocks-helper.php. Error message: Allowed memory size of 268435456 bytes exhausted (tried to allocate 20480 bytes)”

    Forwarded email to: support@yoast.com

    Please advise.

    Thank you.

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