Gutenberg 2.7 Released, Adds Ability to Edit Permalinks

Gutenberg 2.7 is available for testing and not only does it refine the visuals around block controls, it adds the highly requested ability to edit permalinks.

Editing Permalinks in Gutenberg 2.7

A new pagination block is available that adds a page break, allowing users to break posts into multiple pages. The block is located in the Blocks – Layout Elements section.

There are a number of changes to the link insertion interface. Gutenberg 2.7 brings back the option to have links open in the same window.

Toggle Determines Whether Links Open in a New Window

When editing linked text, the Unlink icon now stays in the toolbar instead of displaying within the link options modal. When adding links, there’s a URL suggestion tool similar to what’s available in WordPress’ current editor.

What will be welcomed news to plugin developers, the PluginSidebar API is exposed and considered final. According to the pull request, this change does the following.

Refactors all the existing Sidebar components to share the same set components and removes duplicated custom CSS styles applied to <PluginSidebar />. There are no changes to the public API of <PublicSidebar /> component, other than it is going to be available under wp.editPost.PluginSidebar.

Grzegorz Ziółkowski

This release, like the others before it, has a changelog that’s a mile long. Please check out the release post for a detailed list of changes and links to issues on GitHub.

8 Comments


  1. Awesome! This was the bug I’d found and reported. Yippee! So glad they figured that one out. It’s been a long time since I reported that you couldn’t edit a permalink!

    Report


    1. I run nginx on my server and Gutenberg works just fine even with pretty permalinks.

      Report


    2. Hey James,

      Thanks for bringing that link to my attention, I’ve commented on the post there, but figured I’d repeat the gist of it here, too. :-)

      Gutenberg generally works with nginx, there are a lot of people using nginx while developing Gutenberg, and for testing release versions. We occasionally see different configurations that don’t work correctly, but we’re always happy to figure out to what’s going on.

      If you do run into problems with Gutenberg, I’d like to help get to the bottom of them. The best way is to open a new issue on the Gutenberg repo, so we can dig into it some more.

      Report


    3. This is a complete nonsense. Gutenberg works fine with NginX here, and I know several other people using NginX with Gutenberg, and its working fine there too. The problems with Gutenberg are self-inflicted, not external, and nothing to do with NginX.

      Report


  2. I’m for one excited about it getting better. It will be interesting to see how it shapes web design and what the other page builders/css grid tools respond in coming years.

    Report

Comments are closed.