An Update to My Gutenberg Experience

Not long after I published my experience with Gutenberg, developers reached out to me to work on some of the issues I mentioned. Riad Benguella figured out why meta boxes were not collapsing or expanding.

It turns out that some meta boxes depend on the post script which has a side effect of calling the window.postboxes.add_postbox_toggles( postType ) twice, causing meta boxes to break.

Gutenberg 2.6 released earlier this week, fixes the issue and all meta boxes function properly again. This also fixes the issue I had with the Telegram for WordPress plugin.

Public Post Preview still doesn’t work in Gutenberg but the plugin’s developer, Dominik Schilling, shared some experiments he has conducted with adding support for Gutenberg on Twitter.

In the preview video, you can see Public Post Preview’s options added to the sidebar and in addition to generating a link, you can choose when that URL expires which is better than what’s currently available in the plugin.

I mentioned how Tags would sometimes disappear and there overall behavior was inconsistent. This pull request that made it into Gutenberg 2.6, fixes the issue by only including the term in the Tag selector if it’s known.

Although I’m still bummed that certain plugins are not yet compatible with Gutenberg, I’m pretty happy that two of the major pain points I experienced have been fixed. Thanks to Riad, Tammie Lister, and others for helping to solve these problems so quickly.

8 Comments


  1. Problem is, you are just one “random” (well, not really, but that’s not the point) user with your own set of tools/habits.

    There are millions of others with other types of workflow, and many bugs are still yet to be found.

    It will take a little while, but it’s definitely worth it.

    Report


    1. Another reason why slapping this into core is a bad idea.

      Report


    2. Jeff has been a fairly vocal suporter of Gutenberg and only recently posted his story on his use of it.

      Even if Gutenberg isn’t ready for core just yet it is slowly getting to the point where it needs to take user feedback into account. The fact that Jeff wrote a fairly neutral article about current pain points in transitioning to Gutenberg is nothing but good for the project. Not all feedback fits in clearly defined GitHub issues and simple patches.

      For the record, I am very much in favour of Gutenberg and its inclusion in core once ready and stable.

      Report


      1. It looks like the option has been restored, along with other link related items in the 2.7 release:

        Several updates to link insertion interface:
        *Restore the “Open in new window” setting.
        *Remove the Unlink button. Instead, links can be removed by toggling off the Link button in the formatting toolbar.
        *Move link settings to the left.
        *Update suggested links dropdown design.
        *Allow UI to expand to fit long URLs when not in editing mode.
        *Improve visibility of insertion UI when selecting a link

        Yea!

        Report


  2. I tried it and did not like it at all.

    I found it to be confusing and difficult to work with.

    I truly hope they give us a choice between it and the classic view.

    Report

Comments are closed.