-
Notifications
You must be signed in to change notification settings - Fork 885
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Yoast is blocking post editor from getting iFramed #20535
Comments
I'd also like to point out that this issue has been present in previous WordPress versions also. Just only for block-based themes such as twentytwentyone, twentytwentytwo, and twentytwentythree |
Experiencing this issue as well. Are there plans to solve this? |
This issue is soon to be outdated per the Make post Roadmap to 6.7. The editor iframe will be used even with classic meta boxes. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please give us a description of what happened
As of WordPress 6.3, the post editor is finally also getting rendered in an iFrame for non block-based themes if all registered blocks support apiVersion 3 and there are no classic metaboxes registered. (See the Dev Note)
Sadly Yoast still uses this method for integrating into the edit post screen and is therefore blocking us from finally being able to use the iframed post editor.
To Reproduce
Step-by-step reproduction instructions
twentytwenty
)Expected results
Actual results
Screenshots, screen recording, code snippet
If possible, please provide a screenshot, a screen recording or a code snippet which demonstrates the bug.
The code in core controlling whether the editor gets loaded in an iframe is located here: https://github.com/WordPress/gutenberg/blob/trunk/packages/edit-post/src/components/visual-editor/index.js#L357C7-L364C8 As you can see, it checks whether there are any traditional metaboxes rendered in the editor and if so bails out.
Technical info
Used versions
The text was updated successfully, but these errors were encountered: