-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Template Part Editor broken after updating to WordPress 6.1.1 #45862
Comments
I'm not sure whether this should be tracked in trac or here in GitHub. So feel free to move over as needed. |
Props: karks88, jeffmcnear, and maurodf for reporting this |
Adding a simple P.S. I would recommend using the Example
|
Thanks @Mamaduka 😀 I do just want to note that adding a theme.json file comes with a few side effects that may surprise someone. For example the inner container div of the group block gets removed which can cause some issues if custom styling depended on the presence of that. |
Thanks @Mamaduka i thought that was a releated theme.json problem cause the others users using this feature included the theme.json into their theme and commented with no problem at all. Tested in my site and all works fine, even with empty theme.json file. |
Could you be so kind to say, what is the target folded for the theme.json, please? |
@ottomen If you didn't figure it out yet, |
After updating to WordPress 6.1.1 the Block Based Template Editor is loading just a blank white screen. No console error or anything.
This issue was originally reported on the make blog https://make.wordpress.org/core/2022/10/04/block-based-template-parts-in-traditional-themes/#comment-44097
@Mamaduka was successfully able to replicate this issue and has narrowed it down to the changes that were made in https://core.trac.wordpress.org/ticket/56945 specifically the lines here: https://github.com/WordPress/wordpress-develop/blob/trunk/src/wp-includes/class-wp-theme-json-resolver.php#L423-L425
The issue happens on both WordPress 6.1.1 without any plugins and also with Gutenberg trunk.
The text was updated successfully, but these errors were encountered: