djennez

Hi @truckeystar , the cause for this warning was in Yoast 18.4, and fixed in 18.4.1. However, the cause is that a session was created and that session is likely still active on your site / server. This message should disappear after a little while, depending on your server settings. Please give it 60 minutes or so, and see if it still exists. You can also try logging out and back in on your site.

Hi all,

While there is no single specific error log in this thread, the plugin names mentioned here match the plugins that are known to be causing a particular issue when Yoast 17.8 is installed. Therefore, the following message may apply to most, if not all, participants of this thread.

The WPSEO_Frontend class has been deprecated since version 14.0 of our plugin. In version 17.8, we completely removed it. If any code tries to access that class, it will throw a fatal error.

This most likely means that there is code in your website that is trying to do this. To fix the problem, you will have to find the plugin or custom code responsible and disable / change it. Most of the time, the fatal error will be accompanied by a message showing which files were trying to execute the failing code, and a plugin name may be found in there.

If you have written this code yourself, please see https://developer.yoast.com/blog/yoast-seo-14-0-using-yoast-seo-surfaces/ for alternatives. If you find that it is a plugin or theme that is calling this code, please contact the maintainer of that add-on (and feel free to share the previous link with them).

Some of the plugins that we know of that had this code have since updated their plugins to mitigate this. Please make sure you are running the latest versions of all your plugins and themes.

Hi @marikane,

The WPSEO_Frontend class has been deprecated since version 14.0 of our plugin. In version 17.8, we completely removed it. If any code tries to access that class, it will throw a fatal error.

Looking at your error message, it looks like you have a plugin called w2dc, which, I guess, is the “Web 2.0 Directory plugin for WordPress”. This plugin seems to be calling this removed code and causing these errors.

To prevent this error, you will have to disable that plugin and / or reach out to the maintainers of that plugin to make them aware of this issue. You can also provide them with this link with the current alternatives for the WPSEO_Frontend class.

Hi @madicom,

The WPSEO_Frontend class has been deprecated since version 14.0 of our plugin. In version 17.8, we completely removed it. If any code tries to access that class, it will throw a fatal error.

Looking at your error message, it looks like your theme aardvark is trying to access this removed code, which results in this fatal error.

To prevent this error, you will have to disable that theme and / or reach out to the maintainers of that theme to make them aware of this issue. You can also provide them with this link with the current alternatives for the WPSEO_Frontend class.

Hi @webdados,

The WPSEO_Frontend class has been deprecated since version 14.0 of our plugin. In version 17.8, we completely removed it. If any code tries to access that class, it will throw a fatal error.

If you have written this code yourself, please see https://developer.yoast.com/blog/yoast-seo-14-0-using-yoast-seo-surfaces/ for alternatives.

@parselearn thanks for the heads-up. I did some additional investigating and found your conclusions to be correct. Though it would’ve helped if there was a bit more information like code samples.

I have raised an internal issue for this with a major severity.

If you run into any similar issues with custom code, please feel free to notify us on our GitHub (https://github.com/Yoast/wordpress-seo/blob/trunk/.github/CONTRIBUTING.md#i-have-found-a-bug) with the information that you have.

@theinvisiblehan that’s ok, I can understand the bluntness / frustration.

Semrush is one of the parties that we’ve immediately reached out to, and from what I understand (I do not maintain the communication with them), they have been working on this for the past weeks. So I expect them to fix this on their end soon. We did not mention any third parties in the article for the sole reason to not “throw them under a bus”. We are communicating with multiple third party SEO tools on this matter.

And we indeed do not make the call if it makes sense. We follow schema.org guidelines in that regard, and working by reference is sensible usage according to their documentation. Tools that do not follow that documentation are incomplete, which is why we suggest that our users reach out to them and point them to that article.

Hi all, we recently published this post regarding the schema breadcrumb “name” warnings that a lot of you are seeing: https://yoast.com/help/breadcrumb-changes-yoast-seo-16-2/ . That should help you determine if you’re running into an actual bug, or a tool that is not able to parse schema data correctly.

@theheartypixel the blog that houses this article is experiencing technical difficulties. We’re working on getting it back online, after which point you should be able to read the article again.

@wpmakenorg if you’ve recently (auto)updated our plugin, this may be the cause of this, as files will get updated and modified.

However, if you’ve not recently updated the Yoast plugin; does WordFence show you what exactly has changed in the mentioned file? If so, can you share that?

My fix was implemented in the 15.9 release candidate of the plugin. So it should be live in the next release.

@sergo2003 thanks for the headsup. I have written a fix for the warning. However, something is breaking schema breadcrumbs in your site. The fix will only remove the warning, but schema breadcrumbs will still fail to be generated. So it would be good to know which plugin or custom code is messing this up.

There is a chance that you can fix this by running the “Reset migrations and indexables” button from our Yoast Test helper plugin.

Hi @lcm404 , the changes mentioned above should not have impacted shortcodes. In fact, I am able to register and execute your shortcode without problems. Both with and without the Yoast plugin.

function WelcomeMessageShortcode() {
	return 'Welcome to Website.com blah blahb blah';
}
add_action( 'init', function(){add_shortcode('welcomemessage', 'WelcomeMessageShortcode');});

Putting the shortcode [welcomemessage] in my category or tag descriptions now renders the text.

I don’t think our plugin is interfering here? If it is, we’d like to know all the details as a bugreport as my colleague has mentioned above.

• This reply was modified 3 years, 9 months ago by djennez.

@rafalabrador good to know! Though I am still wondering, for our information, how did you update our plugin initially? “Just” by updating via the WordPress backend?

@rafalabrador thanks. That error seems to be caused by to some missing database settings that should have been applied during the update of our plugin. Can you:

– tell me how you update your plugins, in this case the Yoast plugin? Was this done via a 3rd party (management) tool, or via the WordPress backend?
– verify that installing the Yoast Test Helper plugin and resetting the indexables and migrations does not solve this issue? Because this should completely recreate the necessary tables including all needed settings.