Closed ajitbohra closed 2 months ago
Hello!
TSF is compatible with PHP 7.4 ~ 8.3. The other ticket is about increasing the minimum requirements. Our websites currently work with PHP 8.1.
The plugin shouldn't emit warnings on any of the supported versions. But when it does, it's highly likely something on the site isn't working according to the standard APIs.
Here are some scenarios I figured from a dry run (ranked from difficulty to verify). With these scenarios, I expect you can see the warnings on your screen and not only via logs:
the_seo_framework_post_meta_defaults
or the_seo_framework_post_meta
are active and removing required keys. We found that no other public plugins filter these, so the site owner must have done this if this is an issue. I'd be happy to improve the filter.Did any of this help find the cause?
From other reports I've assimilated that there is a plugin active that calls the meta box before WordPress establishes what a post or page is. This meta box, with the SEO Bar embedded, tries to call a non-existing post object's metadata.
This shouldn't be a cause for concern, but it is a bug in another plugin, and it does indeed spawn unwanted errors.
These errors will no longer spawn from TSF v5.0.7 because we'll then always return the defaults: https://github.com/sybrew/the-seo-framework/commit/5bf612fa73298574924390f4a5dd238c7ab884f4. It doesn't resolve the issue where the meta box is called for no good reason, however.
We have plans to upgrade to 8.2 here https://github.com/sybrew/the-seo-framework/issues/644
In the meantime would it be good to fix some warnings on php8.x?