Skip to content
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

Converting a Pullquote Block into a Quote Block causes Gutenberg to Crash #67876

Closed
masperber opened this issue Sep 15, 2022 · 4 comments
Closed
Labels
[Closed] Resolved Issue is resolved. Use for issues that can be closed but did not have an explicit fix with a PR. Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". [Feature] Core Blocks Blocks that come with Gutenberg. [Feature Group] Editor Experience Features related to Gutenberg integration on WordPress.com. [Platform] Atomic [Platform] Simple [Pri] High Address as soon as possible after BLOCKER issues [Product] WordPress.com All features accessible on and related to WordPress.com. [Status] Core Fix Needed A fix within the Core WordPress or Gutenberg project is required to resolve this issue. Triaged To be used when issues have been triaged. [Type] Bug When a feature is broken and / or not performing as intended

Comments

@masperber
Copy link

Quick summary

When using the Block conversion feature, attempting to convert from a Pullquote Block to a Quote Block will cause Gutenberg to crash.

There was previously a similar bug when trying to convert from an Image or Gallery block to a Carousel Block, but a link to this issue escapes me at the moment.

Steps to reproduce

  1. Add a Pullquote Block to a page or post
  2. Click on the block icon to convert to another block
  3. Mouse over the "Quote" block option in the menu

What you expected to happen

You should be able to convert to a Quote block

What actually happened

As soon as you mouse over the Quote block option in the block conversion menu, Gutenberg crashes.

Context

Customer report: 36579084-hc

Platform (Simple, Atomic, or both?)

Simple, Atomic

Theme-specific issue?

No response

Browser, operating system and other notes

No response

Reproducibility

Consistent

Severity

All

Available workarounds?

Yes, difficult to implement

Workaround details

Instead of converting blocks, you can delete the block and make a new one.

@masperber masperber added [Type] Bug When a feature is broken and / or not performing as intended User Report labels Sep 15, 2022
@github-actions github-actions bot added [Platform] Atomic [Platform] Simple [Pri] High Address as soon as possible after BLOCKER issues labels Sep 15, 2022
@masperber
Copy link
Author

  • 5560822-zen for customer followup when resolved.

@github-actions
Copy link

Support References

This comment is automatically generated. Please do not edit it.

  • 5560822-zen

@cuemarie
Copy link

cuemarie commented Sep 21, 2022

📌 SCRUBBING : RESULT

📌 FINDINGS/SCREENSHOTS/VIDEO

  • Replicated just as described across all test environments.

Example from Self-Hosted Site

Screen.Capture.on.2022-09-20.at.17-43-10.mov

📌 ACTIONS

@cuemarie cuemarie added the Triaged To be used when issues have been triaged. label Sep 21, 2022
@cuemarie
Copy link

cuemarie commented Oct 5, 2023

WordPress/gutenberg#44307 is resolved, and I retested today and could not replicate:

wGUA3K.mp4

📌 ACTIONS

  • Closed as resolved

@cuemarie cuemarie closed this as completed Oct 5, 2023
@cuemarie cuemarie added [Status] Core Fix Needed A fix within the Core WordPress or Gutenberg project is required to resolve this issue. [Closed] Resolved Issue is resolved. Use for issues that can be closed but did not have an explicit fix with a PR. [Product] WordPress.com All features accessible on and related to WordPress.com. [Feature Group] Editor Experience Features related to Gutenberg integration on WordPress.com. [Feature] Core Blocks Blocks that come with Gutenberg. labels Oct 5, 2023
@github-actions github-actions bot added the Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". label Oct 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Closed] Resolved Issue is resolved. Use for issues that can be closed but did not have an explicit fix with a PR. Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". [Feature] Core Blocks Blocks that come with Gutenberg. [Feature Group] Editor Experience Features related to Gutenberg integration on WordPress.com. [Platform] Atomic [Platform] Simple [Pri] High Address as soon as possible after BLOCKER issues [Product] WordPress.com All features accessible on and related to WordPress.com. [Status] Core Fix Needed A fix within the Core WordPress or Gutenberg project is required to resolve this issue. Triaged To be used when issues have been triaged. [Type] Bug When a feature is broken and / or not performing as intended
Projects
Development

No branches or pull requests

2 participants