Publishers who up to date to Yoast SEO 19.5 could have skilled greater than they anticipated. Reports of deadly errors brought on by the replace quickly started surfacing. Interestingly, the error seems confined to particular conditions and never throughout the board.
Yoast SEO model 19.5
Yoast model 19.5 accommodates a number of adjustments that enhance the consumer expertise, repair a validation situation within the Article structured information, and handle some minor bugs.
A standout enchancment is the Front-end SEO inspector that gives an summary of posts and varied SEO settings like meta tags and structured information.
Unfortunately, a bug additionally occurred in a particular state of affairs that prompted a deadly error.
A deadly error can happen when there’s a battle between two plugins.
Yoast Fatal Error
Eli Schwartz, search advertising professional and creator of the favored ebook Product Led SEO, tweeted a couple of deadly error.
….And this is the reason I needed to modify my web site to @Wix. There goes my afternoon as I’ve to determine why THIS occurred pic.twitter.com/p98MlfGSMj
— Eli Schwartz (@5le) August 10, 2022
Turns out an replace from @yoast broke it 😢
— Eli Schwartz (@5le) August 10, 2022
It’s not unusual for a random battle between plugins to trigger an issue. But this wasn’t all that random, as others confirmed that the identical factor was occurring to them.
I confronted the identical situation yesterday once I tried to replace certainly one of my new consumer’s web site @EasyPowerUg
— Webiro (@Webiroagency) August 11, 2022
The official Yoast SEO assist web page on WordPress.org additionally contained studies of deadly errors.
One consumer posted:
Fatal error: Uncaught YoastSEO_Vendor
“I woke up today and tried to access the dashboard of my website and I was met with a Fatal Error, I’m not able to access it through backend nor Login.
How can I solve this issue.”
Two others responded with the identical downside, with certainly one of them providing this remark:
“Same right here. Can’t login in backend and each web site and backend throw a deadly error.
Saw that Yoast has autoupdated immediately.
Moved each the free and the premium model from plugins listing to a short lived listing and now the location is again on-line.”
Someone else with the identical setup of the free and premium model echoed that report, posting:
“Getting a fatal error after the update too. Also have the free version, premium version and News SEO.”
The official Yoast assist individual was apologetic, responding with this assertion:
“We’re sorry that you just’re experiencing a deadly error. Thanks for reporting.
We’re investigating and it appears to be an issue with the most recent replace of Yoast SEO whereas the most recent Premium wasn’t launched but. This shouldn’t have occurred.
We’re getting this resolved as quickly as we are able to by releasing a patch without spending a dime and in addition by releasing Yoast SEO Premium asap.
Either ought to repair the deadly error.
Yoast Responds
Joost de Valk, the founding father of Yoast, provided this suggestions to Search Engine Journal:
“A patch was created shortly by the crew certainly and for many websites that resolved it solely.
For some websites the auto replace mechanism didn’t run correctly and subsequently these websites didn’t robotically repair themselves.
We’ve been discussing this internally lots, as we weren’t pleased that this occurred in any respect, and we weren’t proud of how we dealt with it. We’re all truthfully actually bummed by it and really feel sorry for the websites we’ve damaged.”
Yoast Identifies the Problem
The final commenter who famous how that they had two variations of the Yoast plugin put in, the free and the premium variations, could have been a clue to what prompted the deadly flaw as a result of that state of affairs was cited as the rationale why the Fatal Error was occurring.
Yoast responded shortly to the problems and issued a patch the exact same day, model 19.5.1.
According to the Yoast SEO WordPress Plugin changelog that paperwork what’s in every replace:
“19.5.1 – Bugfixes:
Fixes a bug the place a deadly error can be thrown on the front-end when Yoast SEO 19.5 was used with an older model of Yoast SEO Premium.”
The Problem is Fixed with Version 19.5.1
Yoast 19.5.1 has fastened the issue.
One consumer posted this remark within the Yoast assist discussion board:
“Update 19.5.1 has corrected the issue.”
However, as a result of there are hundreds of thousands of customers with hundreds of thousands of combos of different plugins put in, it’s virtually inevitable that only a few edge circumstances could pop up with points.
For instance, in a put up within the official Yoast assist discussion board, one consumer describes updating from 19.4 on to 19.5.1 and never having a passable expertise.
They shared:
“I went from 19.4 to 19.5.1 and it nonetheless broke my web site. I don’t suppose .5.1 fastened the whole situation. I by no means up to date to 19.5. Went straight from 19.4 to 19.5.1.
I’ve yoast, Yoast premium, and woo. all 3. First, one to attempt to replace was common yoast. All different plugins and WP on my web site are present. Hope that helps to repair 19.5.1Glad I by no means belief autoupdate, Not a fan of paying anybody to be a beta tester.
Yet this one nonetheless received me.”
It’s common for edge circumstances to floor for any replace, and this may be the case for Yoast 19.5.1.
The reason for the issue seems to be that Yoast printed an replace for the free model of Yoast (19.5) however didn’t concurrently publish an replace to the premium model, which then prompted the 2 plugins to battle, leading to a deadly error.
Featured picture by Shutterstock/Kues
window.addEventListener( 'load', function() { setTimeout(function(){ striggerEvent( 'load2' ); }, 2000); });
window.addEventListener( 'load2', function() {
if( sopp != 'yes' && addtl_consent != '1~' && !ss_u ){
!function(f,b,e,v,n,t,s) {if(f.fbq)return;n=f.fbq=function(){n.callMethod? n.callMethod.apply(n,arguments):n.queue.push(arguments)}; if(!f._fbq)f._fbq=n;n.push=n;n.loaded=!0;n.version='2.0'; n.queue=[];t=b.createElement(e);t.async=!0; t.src=v;s=b.getElementsByTagName(e)[0]; s.parentNode.insertBefore(t,s)}(window,document,'script', 'https://connect.facebook.net/en_US/fbevents.js');
if( typeof sopp !== "undefined" && sopp === 'yes' ){ fbq('dataProcessingOptions', ['LDU'], 1, 1000); }else{ fbq('dataProcessingOptions', []); }
fbq('init', '1321385257908563');
fbq('track', 'PageView');
fbq('trackSingle', '1321385257908563', 'ViewContent', { content_name: 'yoast-seo-plugin-fatal-errors', content_category: 'news wp' }); } });