-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Editor: Render editPost slots only in the post editor (same for site editor) #62531
Editor: Render editPost slots only in the post editor (same for site editor) #62531
Conversation
Size Change: +64 B (0%) Total Size: 1.76 MB
ℹ️ View Unchanged
|
The Jetpack plugin does just that, and I can confirm that this patch solves the issue ; slots that are meant for the post editor are no longer displayed in the site editor.
I'd love to see a dev note or a post on the developer blog that would go into more details about the different solutions that will be available to us starting in WordPress 6.6. |
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.
To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Yes, definitely on my todo list. |
I just tested with Stackable and Block Visibility.
Block Visibility currently uses:
With this PR, the menu item does not display in the Site Editor. I think this approach makes sense. As soon as I update it to:
it does display as expected. Overall, I think this is a great PR since it retains the current experience for extenders. Everyone should migrate to The last piece of the puzzle will be to document how you can use |
…editor) (WordPress#62531) Co-authored-by: youknowriad <youknowriad@git.wordpress.org> Co-authored-by: ellatrix <ellatrix@git.wordpress.org> Co-authored-by: jeherve <jeherve@git.wordpress.org> Co-authored-by: ndiego <ndiego@git.wordpress.org>
…editor) (#62531) Co-authored-by: youknowriad <youknowriad@git.wordpress.org> Co-authored-by: ellatrix <ellatrix@git.wordpress.org> Co-authored-by: jeherve <jeherve@git.wordpress.org> Co-authored-by: ndiego <ndiego@git.wordpress.org>
…editor) (#62531) Co-authored-by: youknowriad <youknowriad@git.wordpress.org> Co-authored-by: ellatrix <ellatrix@git.wordpress.org> Co-authored-by: jeherve <jeherve@git.wordpress.org> Co-authored-by: ndiego <ndiego@git.wordpress.org>
I just cherry-picked this PR to the wp/6.6-beta-3 branch to get it included in the next release: 79c00ca |
…editor) (#62531) Co-authored-by: youknowriad <youknowriad@git.wordpress.org> Co-authored-by: ellatrix <ellatrix@git.wordpress.org> Co-authored-by: jeherve <jeherve@git.wordpress.org> Co-authored-by: ndiego <ndiego@git.wordpress.org>
Related #52632
What?
It seems that some plugins are using the old editPost and editSite slots in the same script files and might also be using these script files in site editor even if they're meant only for post editor (or vice versa). While obviously there are better solutions for these plugin authors to avoid loading the slots and scripts were not needed, this PR tries to mitigate the slots unification effects on this kind of scripts.