-
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
Site Editor breaks when no color, gradient or font-size is configured #31986
Comments
Hi |
Hi, Thank you for your suggestion. Unfortunately, that breaks the site-editor as well in my situation. |
|
That doesn't break the site-editor, but at the same time it also doesn't disable the color controls (which is what I'm trying to test). The default colors are shown. |
I experience the same issue. Also, if I use theme.json, I cannot disable editor color palettes anymore in functions.php as theme.json enjoys precedence. |
It's not just the site editor that breaks when I got the following Fatal error just visiting the site when I set
|
I think there's some unclear expectations what values are expected for theme.json which could be minimized, in part by better documentation. Some objects' values in theme.json expect arrays; other objects' value expect binary true/false; Null is a valid value for JSON, additional reference source from json.org |
@erikjoling to answer your question, how to remove all color panels including the default ones provided by Gutenberg, I believe the following works:
|
You are right. The problem is solved since WP5.8. Closing this issue. Thanks for the useful information everyone! |
Description
When I try to disable colors, gradients or font-sizes I can't enter the Site Editor.
Step-by-step reproduction instructions
Disable through theme-support:
or disable through theme.json:
Expected behaviour
Have the controls disabled and being able to enter the site-editor.
Actual behaviour
Have the controls disabled and not being able to enter the site-editor.
WordPress information
Device information
The text was updated successfully, but these errors were encountered: