The node.field_yoast_seo field needs to be updated.

Hi @tomthorp,
I installed the module in D9 and D10 both but was unable to reproduce the error.

Please explain if I am missing something.

Hi @sarwan,

I should of added when I did the upgrade, there were two other modules I had installed - metatag and schema_metatag. I'll outline from memory the events leading up to the error.

From what I can recall, metatag, schema_metatag and yoast_seo were all installed, enabled and all had an upgrade path to 10.1 prior to upgrading. Once I upgraded using composer to 10.1, in 'available updates' there were updates to metatag (v1.26 => v2.0) and schema_metatag (v2.5 => v3.0). Yoast_seo I believe was on v2.0alpha9 prior to the 10.1 upgrade.

When I tried updating metatag and schema_metatag modules to the new release, yoast_seo would not install unless it was on v1.8 (due to some conflict within composer.) Once Yoast_seo was downgraded to v1.8, that is when the problem arose.

Is there some code that needs to be introduced into the module's .install file to rectify this?

- Tom

Also running into the same issue as @tomthorp. I notice the issue prior to upgrading to Drupal 10. I assume the issue is between upgrading module versions. If there is any way to update?

I also have the same issue after updating 1.7 to 1.8.

I ended up removing field and adding another one, since I did not care about keeping configured 'Focus keyword' values in my case.

I think what @tomthorp is describing, is why this is happening in some cases.

I noticed the same thing on our site and with some digging came to the conclusion that by saving the field_settings, there were references to a "title" on the preview field that caused an error. This "title" is only added in the 2.x version and does not exist in the 1.x version.
Because of the downgrade, there is a mismatch on this field.

I don't know if there is any way to fix this mismatch since the field has been created already and is looking for the "title".

Why this is happening after the upgrade from 1.7 to 1.8 is still not clear to me.

Thank you LRoels for the solution!
I could not figure out how to get rid of this error (screenshot 1) on a project that was recently updated to Drupal 10.
Normally I would just edit and resave the field in similar cases. But now when I tried this (re-saving the yoast field), I got the error from screenshot 2.

Solution was upgrading from version 1.8 to 2.0-alpha10.
After I did that, the error was gone.

Forgot to attach screenshot 2 of the error when resaving the yoast field.