-
Notifications
You must be signed in to change notification settings - Fork 4.7k
Block Editor: Standardize loading default block editor settings #30245
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
Conversation
|
Size Change: 0 B Total Size: 1.43 MB ℹ️ View Unchanged
|
dc9c498 to
f3903a2
Compare
0b121d5 to
8296b33
Compare
a279f7e to
66a4d39
Compare
|
I copied over some of the methods developed in WordPress/wordpress-develop#1118 and prefixed them with As mentioned in WordPress/wordpress-develop#1118:
@youknowriad or @nosolosw, what do you think? |
|
Let's move forward with those changes. For now only |
Description
Related WordPress/wordpress-develop#1118.
In preparation for support multiple types of screens that use the block editor, I propose we add a shim for a new function
get_default_block_editor_settingsthat is going to be backported to WordPress core. I'd like to confirm that it works seamlessly with the$postobject that is mostly set tonulloutside of the edit post page. Otherwise, we will need to find a more sophisticated method to ensure we can filter the allowed block types.How has this been tested?
All editors still load:
Types of changes
Checklist: