-
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
Why does the pattern editing on "Edit Page" changes? #67600
Comments
From the screenshot, it looks like you are editing a classic block, and not a pattern? The reason why the classic editor opens in a modal is technical. The block editor uses an iframe. The classic editor block does not work in this iframe, and needs to be opened outside it. Can you share the steps you took to get this result? With the help of more detailed instructions, other contributors can try to reproduce it. There may be a conflict between the classic block and your theme or a plugin. When I test the classic block with the themes Twenty Twenty-One and Twenty Twenty-Five, I do not see these broken toolbars with the miss-placed buttons. |
Hi @carolinan, sorry for my late response. Well, it is a theme I developed for my customer who struggles with the usability of Gutenberg editor. I coded some pattern from the scratch but not way of WordPress - less control about the code and this code (generated) is horrible to understand.
The problem is after the update to WP 6.7.x you need to edit classic block in this modals and not more in the page directly and shows this behavior of the classic editor. May you add a setting to the page preferences that you can switch between classic block editing on the page or on the modal? Or is there already a setting possibility? |
I don´t understand why I have to click "Edit" in pattern popup menu to edit a pattern on "Page Edit" and not as expected in Gutenberg editor?
And the "Classic" editor opens and looks like this...
I mean this is far away from usability! Is there an way to change this by settings?
I use the latest WordPress version.
Regards
The text was updated successfully, but these errors were encountered: