Yoast 14.9 and 15.0 (Website Crashes | PHP Fatal Error)

Hi @jetxpert,

As you may know, this error usually happens when the PHP memory setting on the server is too low. To rule that out that as the cause in your particular case, can you confirm that your site uses the recommended setting of 256M? You can find this by going to Tools > Site Health > Info and looking under the “Server” section.

You can also get more information on this error in this guide: Fatal error: Allowed memory exhausted.

Also, are you using any caching plugins, optimization plugins, or server-side caching? If so, we recommend clearing all cache and testing your site again to see if the error still appears.

Hi @priscillamc,

Thank you for the quick response.

STATS:

Memory: 768M
PHP 7.3.16
WP 5.5.1

We use SG Optimizer, WP Rocket, and Cloudflare. All cache cleared (including our theme’s cache). Issue still present. HTTP Error 500 happening only in the back-end.

Again, thank you. Would be great if you can reach out to your developer(s) for another look at this (others having similar problem). Standard troubleshooting procedures are not helping. We haven’t changed anything since upgrading to V14.9 or V15.0.

Final thought: What would happen if we clear (empty) all of Yoast’s indexable DB tables? Would this be a viable solution?

Hi,

Could you try to bump up the memory to 1024mb? Also, does your website have thousands of pages or a more than 800 pages assigned to a single author?

There is an open issue that does sound similar to what you are experiencing as it occurs in 14.9 but not in 14.8. You can check it out here.

If you reset the indexables and do not run the process again, it will naturally lazy load in the background. However, we’re not sure if this would solve the issue you are encountering.

Hi @mikes41720,

Thanks for the input.

* We’re on a shared server (SiteGround). Our max allowed memory is 768M.

* Our current number of website pages is 880. Our website has two authors with no more than 100 pages per author.

* The issue began with Yoast SEO 14.9.

* We reset the indexables and, as you predicted, did not help.

We’re going to stick with Yoast SEO 14.8 until your team has a chance to look into this further and, hopefully, confirm it is (or not) an issue with your plugin.

Thank you!

Hi!

The same problem is happening to us. Updates 14.9 and 15.0 broke Elementor, causing the server error (500 error).

However, version 14.8 works correctly.

Our settings:

WP Version: 5.5.1
PHP Memory Limit: 2 GB
WP Memory Limit: 40 MB
Number of Category: 75
Number of Tag: 7415

PHP Version: 7.4.8
PHP Post Max Size: 1 GB
PHP Time Limit: 3000
PHP Max Input Vars: 5000

The issue you are currently experiencing is a known bug that our development teams are already aware of. In addition, our development teams have already made a pull request for the relevant fix and once it’s reviewed, it will be merged into the core to release in the next update.

Hello @mazedulislamkhan.

Thanks for the answer. We will continue with Yoast SEO 14.8 until your team fixes the bug.

@jefferso7c You’re welcome, and please let us know if you require any further assistance.

Hi @jetxpert and @jefferso7c,

We’re going to mark this support issue as resolved, but you can get notifications about this issue by watching the pull request on GitHub that @mazedulislamkhan mentioned.

You’re welcome to create a new topic if you have any other questions.

@priscillamc,

Happened to be online. PLEASE RE-OPEN THIS ISSUE. This issue is not resolved.

I noticed you keep marking issues as Resolved throughout this forum when, indeed, they are not. Why? The “green checkmark” added to the top of the issues you’re closing without merit is misguiding those looking for a solution to the same issue.

With all due respect, please let your customers decide when the issue is resolved – or – close these issues or “tickets” when they are truly resolved.

Is Yoast going for score here?

Thank you for your understanding.

We close a topic after a week when there’s no activity to keep the overview of the forum. However, closing an issue doesn’t mean that you cannot re-open it. If the issue doesn’t resolve for you, you can always reply back to the same topic and it will automatically reopen for you.

That said since the issue you are currently experiencing is a known bug and there’s already a pull request waiting to be merged in the plugin, it will be fixed soon. You can always find the progress of the relevant pull request here https://github.com/Yoast/wordpress-seo/pull/16144.

Thanks for your understanding.

@mazedulislamkhan,

Catching up. Thank you. Any idea when the GitHub fix will be released? Current GitHub Status: Merged.

Cheers!

The relevant fix is planned to be included in Yoast SEO v15.4.

@mazedulislamkhan,

Following up on your last comment (above).

Yoast SEO V15.4 was released on December 2, 2020. Unfortunately, we’re still experiencing the same issue.

Yoast SEO V15.4 is supposed to introduce the “fix” of the GitHub link you provided above. It says the issue is “Merged” not “Solved”

Note: We checked your V15.4 changelog notes. They suggest the problem has been fixed, but we’re not certain about it.

Please advise.

Thank you!