Opened 3 years ago
Last modified 3 years ago
#53085 new defect (bug)
Gutenberg editor and Chrome stopped working after 5.7
Reported by: | thaikolja | Owned by: | |
---|---|---|---|
Milestone: | Awaiting Review | Priority: | normal |
Severity: | blocker | Version: | 5.7 |
Component: | Editor | Keywords: | needs-patch |
Focuses: | Cc: |
Description
I have a problem with Gutenberg since upgrading to the version above 5.7
, including 5.7.1
, which seems like a bug to me. If I refresh, sometimes it works, but usually not.
All plugins have been deactivated, including /mu-plugins/
, and a shipped theme activated. Same issue in Google Chrome and Chrome Canary. Safari works, but it takes several seconds for the UI to be clickable.
Downgrading to 5.6
works, too, but this can't be the right solution.
Here is [the error log](https://paste.ee/p/NRCuh) that was logged when Gutenberg didn't react.
Change History (8)
#2
@
3 years ago
- Severity changed from normal to blocker
Hi @vdwijngaert and thanks for your reply.
You're right, Yoast SEO was active when I copied the log. However, the exact same log (without the Yoast part) appears when all plugins are deactivated. As I said before, I reduced everything to the most native state I could, changing the theme to one that WP ships, no plugins at all, no /mu-plugins/
. I've been working with WP professionally for +12 years, so I know what might influence WP's core.
I can't tell you how to reproduce it. Sometimes, I refresh and it works. Then I refresh again and it doesn't. It's like there's no logic behind it.
One thing I haven't said: I'm using it locally, via valet-plus, and an SSL certificate (but I also tried deactivating that). Can this have anything to do with that?
The weird part is that it works fine in WP 5.6
, but not in 5.7.0
or 5.7.1
, which, to me, clearly leads to a change in WP core, that's why I posted it here and not as a general help support ticket. It seems to be a bug that, if I google, other users also seem to have.
Thanks for your support!
#3
@
3 years ago
Thanks for clarifying that. I did some more digging around and find this issue that might be related: #52790.
Just in case it isn't related, some more questions:
- Does this happen regardless of the editor's content? Are you perhaps also using reusable blocks?
- Can you share a dump of your editor content using the code editor? (ctrl+alt+shift+m)
- When you say "it doesn't work", is there any more details you can give me as to what exactly doesn't work? Is there a visible error? Does the editor just stay blank?
#4
@
3 years ago
Hi @vdwijngaert,
No, this ticket does not reflect my problem.
Yes, I'd say pretty much regardless, I have ~800 posts under my custom post type, and I checked several of them randomly, and all had the same issue. Sometimes the Gutenberg UI works, sometimes not. It's just a matter of how often I hit refresh.
I have uploaded a video demonstrating this weird behavour.
You can see the video here:
https://streamable.com/88e2gf
If you see the console log, you'll see some extensions, i.e. Grammarly, are active, but I also tested it without any edxtensions or plugins and with standard themes. I also bulk-converted all posts to blocks, which gives me the following markup in the code view:
<!-- wp:paragraph --> <p>Lorem ipsum...</p> <!-- /wp:paragraph -->
This ticket was mentioned in Slack in #core-editor by vdwijngaert. View the logs.
3 years ago
#7
@
3 years ago
Hey @thaikolja, have you tried installing the Gutenberg plugin, as suggested in my first comment? That's the feature plugin containing the latest version of Gutenberg that's not already bundled in core. Your issue might already have been solved there.
#8
@
3 years ago
Hi @vdwijngaert,
Please excuse the late reply.
Yes, unfortunately, the bug also exists using the Gutenberg plugin. I wish I could find a way to have you guys replicate it, but I'm totally in the dark here. It's just posts, 90% of them only text, created with the classic editor from WP < 5.0. A few of them have a gallery embedded or a Tweet, most don't. It must have something to do with the changes made to Gutenberg after 5.6.
Hey there, thanks for reporting this issue. In order for us to be able to help you, we'll need a bit more information.
First of all, in your error log, I noticed this line:
This gives me the impression not all plugins were deactivated at the time of testing. Can you follow these steps for me?
If the issue still persists, can you try to reproduce it in a new environment, and provide us with a more detailed explanation of the problem you're experiencing and how we can reproduce it?
Thanks!