Gutenberg version 19.2 brokes the editor

  • Resolved Rodrigo Lima

    (@rodrigoflausino)


    1 month, 1 week ago

    Hi! I install the new Gutenberg version and the version brokes the web stories editor. It’s generate a critical error and i dind’t receive a email from WordPress editor =(

    I don’t know what its happened, but i revert the Gutenberg plugin for 19.1 version.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Pascal Birchler

    (@swissspidy)

    Congrats, you found a bug in Gutenberg!

    I will report this over at Gutenberg because this is an issue with a change on their side, nothing wrong with Web Stories.

    Thread Starter Rodrigo Lima

    (@rodrigoflausino)

    HI! Thanks! I posted here first because if i post on Gutenberg forums, the devs will suggest to report the same info here, like other devs on other wordpress forums =\

    (or when i try to report the LCP problems in AMP forums in Github, because any devs have any interest to improve this and improve the Core Web Vitals)

    Similar the option to use webstories on tag pages, because some themes its broke the listing if i use filters, like “playstation 5 stories”.

    And i don’t have any new webstories in Google Discover feed, because Google banned my portal without any reasons, and i don’t have any motivation to create much webstories for next weeks and months =(

    (but some weeks i try to create more webstories to gets a hope to my webstories shows in Discover again, but for a entire year i didn’t have any posts in Google Discover anymore)

    Thanks for help and thanks for continuing the minor updates too!

    Plugin Author Pascal Birchler

    (@swissspidy)

    Just a quick update, Gutenberg 19.3 was released today that should resolve the critical error.

    Unfortunately we can’t help with issues related to Discover here, our focus is the WordPress plugin, not the distribution. I recommend asking in the Google Search Central Help Community about that.

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.