[wp-trac] [WordPress Trac] #52790: Reusable blocks disappeared
WordPress Trac
noreply at wordpress.org
Fri Apr 23 09:18:06 UTC 2021
#52790: Reusable blocks disappeared
-------------------------------+-----------------------
Reporter: jordiparera | Owner: (none)
Type: defect (bug) | Status: reopened
Priority: normal | Milestone: 5.7.2
Component: Editor | Version: 5.7
Severity: blocker | Resolution:
Keywords: reporter-feedback | Focuses:
-------------------------------+-----------------------
Comment (by jagenda):
Not sure if this is related but I've noticed a couple of changes that
allow users to accidentally break their Reusable Blocks.
The block validation now strips content from Reusable Blocks that have
other Reusable Blocks inside them. This is fine, but I find it odd that
you're still allowed to add those nested blocks instead of preventing
users from doing so in the first place.
Not only that but previously Reusable Blocks were not editable in the page
editor, which meant that you were relatively safe from mistakes. What
happens now though, is that the Add New Block (+) button inside Reusable
Blocks is indistinguishable from the page content's Add New Block buttons
and users keep adding nested Reusable Blocks by accident. The previous
heading for Reusable Blocks is also missing, which would make it clearer,
along with a clear outline, where a Reusable Block begins and where it
ends.
My suggestion would be to disable the ability to add nested Reusable
Blocks altogether, and to prevent Reusable Block edits inside pages. If
not the latter then at least clarify which content belongs inside the
Reusable Block and which is current page content. Adding a clear heading
and border that does not require selecting the block and in fact makes it
easier to click on.
Again, these may be separate issues but the outcome is definitely the same
and has caused grief among clients who do not know how to check if a block
is Reusable before adding more Reusable blocks into it. I understand there
is a new Post Update system to select which content you want to save but
it's been poorly documented (no mention of it anywhere in the patch notes)
and this does not help less tech savvy end-users from adding content in
the wrong place and having to fix it later, wasting valuable time.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/52790#comment:35>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list