• I made the fatal error to update the plugin to 9.2 and everything on my pages in the editor is now blank. The site still seems to load but the pages are destroyed. How can I possibly explain this mess to my client in the morning? Please do a better job troubleshooting before releasing these updates. This is the second time I’ve trusted it was okay to update and will be stuck now rebuilding a website for days. Nightmare.

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)
  • The Gutenberg plugin is experimental with many beta features. If you want stability, deactivate the plugin and use the Gutenberg (Block Editor) which is part of the default WordPress installation. This version is a few months old, but has been beta tested on millions of websites and is stable. The plugin is not needed to use Block Editor! The plugin is for experimental features that could break your site!

    To diagnose your error, we need more information. What error messages are displayed in the console when you visit your pages that are blank?

    One way to quickly solve your issue is to deactivate Gutenberg plugin via FTP or your hosting dashboard. Or downgrade to the previous version if you are already using the latest beta features in your theme.

    You do not need to “be stuck now rebuilding a website for days. Nightmare.” as the data is all there, nothing has changed. You’ve simply upgraded a plugin which is incompatible with your theme or system, and once removed or downgraded, everything will still be there.

    Let me know how you get on

    Gutenberg Blocks and Template Library doesn’t compatible with 9.2

    Gutenberg Blocks and Template Library doesn’t compatible with 9.2

    This is incorrect

    Thread Starter flohcreative

    (@flohcreative)

    Hi James @bonkerz

    Indeed, thank you for the follow-up. Just catching up with it now.

    Actually, I went in after posting and turned off the plugin. Which allowed me to see the content of the pages again in the block editor.

    The issue with the update showed up in the block editor without an error — rather it conflicted with every other plug-in in use and turned every bit of the content in the editor — photos or text — invisible. There was no way to select the boxes or to see the content. The only part of the site which was unaffected was the background. lol lovely.

    At any rate — perhaps I sounded a bit emotional. I was indeed in the moment when commenting and definitely have experienced this before thus the “nightmare” statement. Yet it’s important to convey the experience so it can be resolved. I meant nothing personal toward you or anyone else, simply lamenting what had been heaped upon me to do as a result of a one-click update to the plugin.

    Perhaps it would be wise to post possible known conflicts in the notes when supplying the updates. Although it’s well known this could happen, it seems that the studio where Gutenberg Blocks is being created would be aware of these things? I’m suggesting to share more info not less, that’s all.

    Thanks so much for the reply and the recommendation. I can confirm that deactivating the 9.2 plug-in resolved the issue I was experiencing. 9.1 had no issues or conflicts what-so-ever so it a bit shocking to have things fall apart so quickly.

    All is Well.

    The issue with the update showed up in the block editor without an error — rather it conflicted with every other plug-in in use and turned every bit of the content in the editor — photos or text — invisible. There was no way to select the boxes or to see the content. The only part of the site which was unaffected was the background. lol lovely.

    Sounds super weird. I hope the Gutenberg developers make a better system to help tell or show users when something goes wrong like this.

    Perhaps it would be wise to post possible known conflicts in the notes when supplying the updates.

    I think the point of the Gutenberg plugin is to test it out and find the bugs, as its not feasible for a developer to test it themselves on millions of different configurations. They have no idea what combination of plugins you are using.

    Every few months the stable elements of the plugin are merged in to the core WordPress, so by that time, the bugs you experience (probably) don’t exist.

    I think a better approach could be to rename or heavily warn users that using this Gutenberg plugin is probably going to break their site. And I will be suggesting this at the next developers meeting.

    Upgrading plugins on a live site could always give you problems – this is not just a Gutenberg problem. If your host gives the options to have a staging site or development site, you should copy your site from live to staging to test the upgrades before doing on your live site. This way you can catch any issues, and not panic about your site being broken.

    Glad you got it resolved anyway!

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Updated to 9.2 and all my blocks disappeared. Unable to edit anything’ is closed to new replies.