I’m encountering the same issue. The error disappears when I downgrade the core version to 6.7.2.
My server is running PHP version 8.3.20.
Hello @jeffmart, I’m sorry about your experience.
Clear WordPress Cache
First, if your site uses a cache plugin or service, like Cloudflare, please clear the site and server caches. The plugin or service’s support team and your web host can help you clear the cache from these services. After you remove the other caches on your site, you can use this guide to clear your browser cache: How to clear your WordPress cache.
Hi @maybellyne,
Clearing the caches (yes, we have multiple caching strategies in place), then disabling them completely, logging into the backend from an incognito browser window, and then doing the same process in a completely new instance of another browser that was just installed specifically for this task were the first tests we did before I came here to report the issue. So, well, I’m pretty sure it’s not a cache-related issue…
Often, we see problems occur in combination with another plugin or theme. The fastest way to rule out any conflict is to deactivate all non-Yoast plugins and switch to a standard theme like Twenty Twenty-Two.
Please test this on your development or staging site if you have one. If not, we recommend using the Health Check & Troubleshooting plugin. This plugin has a troubleshooting mode, which does not affect normal visitors to your site.
If you’re unfamiliar with checking for conflicts, we’d like to point you to a step-by-step guide that will walk you through the process: How to check for plugin conflicts
If you feel uncomfortable doing this yourself or if this does not solve your issue, our Yoast SEO Premium plugin comes with one year of (technical) support.
The issue has been fixed in version 25.0. Thank you very much!
Thank you for your attention, Maybellyne,
Unfortunately, our site operates in a high availability segment, and we currently do not have a parallel development environment, so none of the options are viable for me. The Health Check & Troubleshooting plugin, which you mentioned, has received many complaints about causing problems to sites, so I cannot risk taking our site offline.
In any case, considering that during this entire period we have not changed any plugins and the problem started precisely when we updated Yoast and WordPress in the same week, even if it is another plugin causing this, we will have to find an alternative, since we would have difficulty deactivating any of the (few) other plugins, since they operate on features delivered directly to visitors, on the frontend.
I upgraded to version 6.8 and had the same issue.
Clearing the cache didn’t solve the issue, but taking other plugins offline and enabling them did.
