-
Notifications
You must be signed in to change notification settings - Fork 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
Edited Reusable Block Bug Breaks Post/Page and Calypso - Site - Posts/Pages (no posts/pages appear) #38929
Comments
Got a similar case here 2649686-zen |
Another one in 3124526-hc |
Another similar case in 18426919-hc: |
@mrfoxtalbot I'm not following. Was that meant for another issue perhaps? |
I am sorry, @kriskarkoski! I meant to add this comment on a different issue, please disregard my comment. |
Confirmed this issue is still present and self-referencing also makes the Reusable Blocks option disappear when adding blocks on a new post and saving to fail on the post if you open the editor, edit the reusable block to self-reference, and then try to save a post with it present. I also tested on a core install and was able to reproduce issues there, specifically fatal errors due to timeouts in /wp-includes/class-wp-block-parser.php on line 417 and /wp-includes/class-wp-block-parser.php on line 417. @scosgro Do you want to open the issue on https://github.com/WordPress/gutenberg/issues? |
Posted here: WordPress/gutenberg#21117 |
Another report here: |
This is a duplicate of WordPress/gutenberg#18704. I'm going to leave it open to make it easier to find. |
Another case in 3655674-zen |
WordPress/gutenberg#18704 has been closed. |
I'm not 100% sure about how the user whose site this bug was affecting reached this conclusion, but I've found a way to replicate the bug (or something very much like it).
Steps to reproduce
<!-- wp:block {"ref":BLOCK-NUMBER-HERE} /-->
What I expected
I'm not totally sure the workflow the user went through to get to this point. They didn't seem like they were too sure either. There has to be an easier way to do it, but I haven't found it. This was only the way I could replicate it based on what I saw on their site.
Expected the reusable block to not break the post/Calypso.
What happened instead
The Block breaks the post/Calypso once updated in this way.
Browser / OS version
All.
Screenshot / Video
.gif is a bit long, but shows the full workflow, including the aftermath.
https://cloudup.com/co-14A0XSOg
Context / Source
#reallife #painpoint.
#user-report
The text was updated successfully, but these errors were encountered: