Yoast
Classicpress compatibilty
Context: Why was this issue created?
ClassicPress is a wordpress 6.2 fork that does not switch to Gutenberg blocks. This issue aims to bring full compatibility with ClassicPress.
What is the goal of this issue?
This issue aims to bring full compatibility with the future ClassicPress 3.0.0.
What needs to be done to achieve the goal?
Fix two deprecations in wp-admin used scripts: wp-api and moment
Does the issue still need UX or research?
no
If available: what are the tips for fixing the problem or possible solutions?
What is the expected result/behavior?
no deprecation warnings in debug mode
Should documentation be added or updated for this change? and if so, where?
no
Hi @8ctopus, Thanks for creating the issue. At this time, Yoast SEO has been developed specifically for WordPress, and we haven't checked the support and compatibility of ClassicPress.
What's next? Our product team will assess the severity of this problem regarding other open bug reports and new features. Based on their assessment, the bug report will be prioritized. Our developers work on the highest priority issues first. Unfortunately, this means we cannot give you an estimate of when they'll start working on your report.
If the ClassicPress community is interested in contributing compatibility improvements via a pull request, we’re open to reviewing them, as long as they don’t negatively impact the plugin’s performance or compatibility with WordPress.
Yoast works fine from what I can tell so far. These are just deprecation notices for the future classicpress 3.0.0. I'm not fluent enough in wordpress, to create a PR myself.
UPDATE: The classicpress migration plugin does not report Yoast SEO as incompatible, but once migrated, ClassicPress itself says that Yoast is not a compatible plugin. I have reported the discrepancy to the classicpress developers. See https://github.com/ClassicPress/ClassicPress-Migration-Plugin/issues/114