Working with Gutenberg: The New WordPress Editor

18 Feb Working with Gutenberg: The New WordPress Editor

WordPress 5.0 is leaps and bounds better than its predecessor, in terms of functionality. The primary purpose for this automatic software update was introducing the Gutenberg Block Editor, a new, block-based editing system that will now serve as the “default post editor” for all WordPress websites. To its credit, Gutenberg allows users to edit and embed a wide range of content in posts and pages, ultimately giving them more flexibility than WordPress Classic Editor did. Although Gutenberg has simplified the website editing experience in the long run, many people are struggling to adjust to the new interface. And in some cases, websites have broken because of the sudden transition to WordPress 5.0. But fear not – everything is fixable.

So what, exactly, is causing these issues?

Here’s the CliffsNotes version: Gutenberg lacks the ability to work with legacy plug-ins and themes, as well as the existing site editing framework. As the default post editor, Gutenberg overrides any existing visual editor plug-in that is currently installed on your website, such as Visual Composer. While your website’s plug-ins and content are still there, you may have noticed that when you open a page to edit it, it will display code instead of the Visual Editor you’re accustomed to. In other words, with Gutenberg it is harder to edit pages and content if you don’t know how to code. Gutenberg is breaking Visual Composer and other Visual Editors. If your website is built with Visual Composer, your website probably broke when the update happened.

Gutenberg is still a drag-and-drop editor, similar to Visual Composer, but it’s not as user-friendly and intuitive for the layman.

Gutenberg has left many users in the dark as to how they can go about fixing their broken sites, testing existing plug-ins, and editing themes to work with the new editor. With over 60,000 unique plug-ins and an abundance of themes to choose from, the original creators of those plug-ins and themes will have to test their compatibility with Gutenberg and fix them. If that was the case, you probably didn’t notice any difference in the display or functionalities of your website. As for plug-ins and themes that have been abandoned by their creators, users were left to test the compatibility themselves. Most people don’t know how to do that unless they are a developer.

Since the automatic update, many users have reported issues editing the website, accessing editing capabilities, and even accessing the site itself. WordPress has given users the ability to install the WordPress Classic Editor as a stand-in solution for fixing broken websites for the time being. However, Gutenberg will still be the default editor going forward, and it is unclear how long the Classic Editor will remain accessible to users. However, the Classic Editor will be phased out by 2021. So, you have until then to have your website fixed or made compatible.

Its possible that the developers behind visual composer will manage to bring their plug-in to a point where it is fully compatible with Gutenberg. But, at the moment, it’s only partially compatible.

Having problems adjusting to the new editor or have a website in need of repair? We can help you resolve an immediate problem and maintain your website in the future. This includes SEO, content creation for better rankings, customization, and hosting. So don’t let Gutenberg get the best of your website. Let’s talk!