post editor fails to load properly after update

@pttony We’re sorry to hear you are experiencing this issue on your site.

Can you confirm you are using WordPress 5.7.2? You can check by clicking on the W in the top left and selecting About. If you need to update, please check with your host provider. Please know that if you are using an older version of WordPress Core you may experience unexpected behavior with Yoast. This guide explains more: https://yoast.com/why-we-dont-support-old-wordpress-versions/

If you update to the most current version of WordPress and Yoast SEO, does this resolve the issue?

If you have confirmed both WordPress, Yoast SEO, and all of your site’s other plugins and themes are up to date and the problem is still occurring, we would next recommend performing a conflict check. A plugin or theme conflict can sometimes cause functionality problems, errors, or unexpected behavior from the plugin. If you are unfamiliar with checking for conflicts, we have a step by step guide on how to check for conflicts available here: How to check for plugin conflicts.

Test this on your development or staging site, if you have one. If not, we recommend using the?Health Check & Troubleshooting?plugin. This plugin allows you to run a conflict check?without affecting normal visitors to your site.

Can you please confirm you have performed a complete conflict check by disabling other plugins, and resetting the theme to a default such as TwentyTwentyOne and let us know the results?

If you do not feel comfortable to do this yourself or if this does not solve your issue, our Yoast SEO Premium plugin comes with one year of (technical) support.

We are using the most current version of WordPress. There may indeed be a conflicting plugin – but again, there was no issue prior to updating to the current version of Yoast (this was verified when I rolled back to 16.6.1 and everything worked properly). So whatever is in the 16.7 update is causing the conflict.

When I can find half a day to work on this I’ll do a thorough compatibility check. In the meantime, we’ll stick with 16.6.1.

Please kindly keep us updated if you discover any known issues that might be causing this. I’ll keep my eye out for updated version and will scan the changelogs.

Thanks for your confirmation, @pttony. We can’t wait to hear more about the full conflict check. In addition, we’ll definitely let you know if we have a confirmed conflict from someone else as well.

Have a great day!

We are going ahead and marking this issue as resolved due to inactivity. If you require any further assistance please create a new issue.