-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Reusable blocks support for widgets editor #26097
Reusable blocks support for widgets editor #26097
Conversation
Size Change: +4.4 kB (0%) Total Size: 1.19 MB
ℹ️ View Unchanged
|
1e24f39
to
80f50d4
Compare
In my testing, this worked as described BUT I get a horrible performance in FF and in console a gazillion of:
|
I've just fixed this, should be ready to test again 😄 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is working well!
I wasn't able to reproduce the maximum update depth error on Firefox, Safari or Chrome. Tested with several reusable blocks on the page, both created in the post editor and in the widgets screen.
Removing from reusable blocks in the widgets screen works, but I noticed the removed block isn't deleted from the widget area like in the post editor.
Performance-wise the reusable blocks are very slow to load, but so are the legacy widgets as compared to normal blocks. It gets worse the more blocks are in each area.
Has this been merged into core WordPress? On the Appearance>Widgets page, I'm not seeing the Reusable tab in the bock inserter, and my reusable blocks don't show up when I search for them by name. Further, if I paste a reusable block into a widget, I get an error: Your site doesn’t include support for the "core/block" block. You can leave this block intact or remove it entirely.. |
Okay 😞 I'll try to figure out some workaround. Thanks for your quick response! |
Description
This PR brings the support for reusable blocks into the widgets editor.
How has this been tested?
Types of changes
New feature (non-breaking change which adds functionality)
Checklist: