-
Notifications
You must be signed in to change notification settings - Fork 4.6k
Block Editor: fix BlockSwitcher to prevent transforms on reusable blocks #71661
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
Block Editor: fix BlockSwitcher to prevent transforms on reusable blocks #71661
Conversation
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
| const isReusable = isSingleBlock && isReusableBlock( blocks[ 0 ] ); | ||
| const hasPossibleBlockTransformations = | ||
| !! possibleBlockTransformations.length && canRemove && ! isTemplate; | ||
| !! possibleBlockTransformations.length && | ||
| canRemove && | ||
| ! isTemplate && | ||
| ! isReusable; |
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.
Let's generalize the check and update the comment above; otherwise, it looks outdated.
Here's an example diff:
diff --git a/packages/block-editor/src/components/block-switcher/index.js b/packages/block-editor/src/components/block-switcher/index.js
index 8bd02e9357d..537d919c270 100644
--- a/packages/block-editor/src/components/block-switcher/index.js
+++ b/packages/block-editor/src/components/block-switcher/index.js
@@ -102,18 +102,16 @@ function BlockSwitcherDropdownMenuContents( {
selectForMultipleBlocks( transformedBlocks );
}
/**
- * The `isTemplate` check is a stopgap solution here.
+ * The `isSynced` check is a stopgap solution here.
* Ideally, the Transforms API should handle this
* by allowing to exclude blocks from wildcard transformations.
*/
const isSingleBlock = blocks.length === 1;
- const isTemplate = isSingleBlock && isTemplatePart( blocks[ 0 ] );
- const isReusable = isSingleBlock && isReusableBlock( blocks[ 0 ] );
+ const isSynced =
+ isSingleBlock &&
+ ( isTemplatePart( blocks[ 0 ] ) || isReusableBlock( blocks[ 0 ] ) );
const hasPossibleBlockTransformations =
- !! possibleBlockTransformations.length &&
- canRemove &&
- ! isTemplate &&
- ! isReusable;
+ !! possibleBlockTransformations.length && canRemove && ! isSynced;
const hasPossibleBlockVariationTransformations =
!! blockVariationTransformations?.length;
const hasPatternTransformation = !! patterns?.length && canRemove;c76417a to
785399a
Compare
Mamaduka
left a comment
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.
Thanks for working on this, @shrivastavanolo!
What?
Closes #67710
This PR updates the BlockSwitcher component to disable block transformations for reusable (synced) blocks. Template parts were already excluded; now reusable blocks will also hide transform options in the dropdown.
Why?
Currently, the BlockSwitcher allows transformations on reusable blocks. Transforming a reusable block can cause unexpected behavior, since all instances of the block are linked. Preventing transforms for these blocks ensures consistency across instances and prevents accidental data loss.
See #67710 (comment)
How?
Testing Instructions
Screenshots or screencast
Before
Screen.Recording.2025-09-15.at.5.25.00.PM.mov
After
Screen.Recording.2025-09-15.at.5.24.30.PM.mov