About Us   |   Advertise

Heads Up for Small Businesses Running WordPress, Huge Changes Coming with 5.0 Gutenberg



Heads Up for Small Businesses Running WordPress: Huge Changes in 5.0 WordPress Gutenberg Editor

Developers love change. Making something “new” and “better” excites them. They are really excited that WordPress (WP) as we know it is going away.

But for small business owners, managers and personnel, change means lost productivity, expenses and a new learning curve. It will cost you time and/or money to make this transition.

And it is claimed that it will eventually be mandatory.

Hold on to your device because everything about creating content in WordPress is about to change — unless you opt out. Opting out is a current option, but for how long?

WP 4.9.8 is expected to be released on July 31, 2018 and will include the Gutenberg Callout encouraging people to install it and update.

Do NOT allow Gutenberg to go live until you read this because it may cause issues on your site. Test first!





This video from 7/10/18 has the latest information:

This is NOT a minor change they’re making. And once you migrate to the new layout, you cannot uninstall it. You would have to restore your original site from the backups.



Expect Delayed Support from Many Hosting Companies

Only 22% of all WordPress sites are running on the latest version. That means that many WordPress users probably rarely log in or never look at updates.

When Automattic sends the notification in a 4.9.x release with an invitation to install either the Gutenberg or the Classic Editor plugin, they won’t see it or may even ignore it. [These plugins are explained later in this content.]



Other sites that are on the latest version may have automated updates turned on and not see it. What this means is that the majority of WordPress users may not realize this huge change is coming.



When they wake up one day and their site has issues, their first point of contact is likely to be their hosting company, causing their support lines to become very busy.

Do Hosting Companies Know About Gutenberg?

How much hosting companies know about this change is going to vary widely. The largest hosts are aware it is coming, but how well they will have their support personnel trained to answer questions on it remains to be seen.



Even if they are all well-trained, the sheer volume of calls is going to impact wait time to speak with support.

Please share this information with everyone you know that uses WordPress so they’re prepared.



WordPress specific hosting companies including WpEngine, Synthesis and DreamPress are often actively involved in WordPress development so they are likely to be familiar with the upcoming changes.



For example, WordPress Developer Mika Epstein is an expert on htaccess and multi-site. She is a WordPress plugin review team representative who works on DreamPress for DreamHost.

She is actively involved in testing and evaluating plugin compatibility with Gutenberg. And she was kind enough to offer her insights and clarification used to create this article.

What If Your Hosting Company Is No Help?

You may find your hosting company has no idea why you are calling. First, try installing the Gutenberg plugins to opt-out.





If you still have issues, it could be a good time to consider moving to a WordPress-optimized hosting company or at least one more familiar with WordPress changes.

Some of the advantages of using a hosting company that is specifically designed to host WordPress only are:

  • They are Faster. On average these companies are 30-40% faster than shared hosting partly due to improved caching.
  • They have better firewalls. Because they only host WordPress, they can block many security issues immediately and close avenues not used by WordPress to keep out hackers.
  • They have automated backups. Though these are also available on other managed hosting services.
  • They offer other safeguards. Some limit which plugins can be used to reduce security and server load issues.

If you want to build a low maintenance WordPress site, follow these tips. Carefully vet any hosting companies you consider and note the age of the reviews and comparisons you read.

How to Vet Hosting Companies

Keep in mind that some companies offer large affiliate commissions which provide an incentive for writers to recommend them over their competitors. Those recommendations may or may not be based on actual results.





Beware of sites only recommending the top three hosting companies which also happen to pay the highest commissions.

Instead, seek out comparison sites that provide factual analysis or many reviews without affiliate links. Here is an example of a HostingFacts review based on testing speed and uptime.

Their thorough reviews make it easier to compare hosting plans and costs. Another excellent source for reviews is G2 crowd’s hosting section.

Switching hosting companies can be simple or complicated. Some offer free migration services while others charge to move your site.



If you have database or loading issues, paying can be worthwhile to resolve those problems at the same time. Evaluate how serious you are about your site.

Now could be a good time to go all-in with your site. Switch to https (if you haven’t already). And consider changing to the fastest, most secure hosting possible to fully grow your business.

Remember to ask whether https is included in the price or the hosting company charges an extra fee for it. Some are still charging while others include it.

What Is WordPress Gutenberg?

Gutenberg changes how you create blog posts and how they appear when published. The best way to understand is to actually see it.

Because Gutenberg has been continually changing to this point, this is the most recent demo as of now. Hopefully, it will still look similar when you see it.

WordPress Developer Will Patton explains that it is necessary to update WordPress because “as it is currently, it cannot take advantage of advances in modern browser features. The new Gutenberg editor works better and faster in the browser.”

WordPress Developers Need to Provide Guidance

Non-technical site owners are not going to know how to do any of the steps mentioned above. Developers may be inundated with calls about every site they have ever built.

Because it is unlikely you have the bandwidth to handle the questions you are going to get, you need a plan. First, create a post similar to this how to start a blog with step-by-step instructions, but specific to Gutenberg.

Even better, create video tutorials, courses, or ebooks. Use these to walk past clients through how to prepare for Gutenberg themselves or to educate them while they’re waiting for you to be able to assist.

If your past clients can watch on their phone while doing the action steps you provide, maybe they won’t need personal assistance. If you don’t have time to make your own, find videos others have made and share those.

Create your own walk-through how-tos using Screencast-o-matic. There is a forever free plan or upgrade to one of their very inexpensive premium plans for additional editing features.

Providing how-tos in text, audio and video can benefit your customers and past clients more than talking to them on the phone or via email. Protect your time by notifying them in advance so they are not caught unprepared.

Freelance Income Opportunities

Many small businesses and freelancers are not going to want to do the testing themselves. Developers with experience, hosting companies, and even students can create portfolios showing their experience and start pitching owners of WordPress sites.

Some site owners will only want someone to install the Gutenberg related plugins. You could help many site owners, doing a high volume for a low price that generates a nice income.

Randy A. Brown put Gutenberg into perspective: “The future of WordPress will not put developers and designers out of business.”

If you know developers who want to be ahead of the demand, they need to learn Gutenberg and React. Many developers will not be able to troubleshoot their own code because they won’t learn React.

Gutenberg Plugin Confusion

Sorting out the plugins related to Gutenberg is not easy. There are already 19 pages of plugins showing up on a search for Gutenberg in the official plugin repository.

But these three are the ones you need to consider:

  1. Classic Editor plugin: install this before Gutenberg goes live to stay on the existing editor.
  2. Gutenberg plugin: install this to test Gutenberg now before it is merged into the WordPress core.
  3. Gutenberg Ramp: “adds a settings screen where you can enable Gutenberg selectively (for specific post types). For even greater control, you can specify Gutenberg loading behavior in code. Ramp works with both the plugin version of Gutenberg, and the core version, providing a seamless transition.”

While there are many other plugins to disable or alter the behavior of Gutenberg and restore the classic editor, the plugins above are recommended by the WordPress plugin development team.

Use this post or the video below to understand how to use the Gutenberg Ramp plugin.

Why WordPress 5.0 May Break Your Site

The current plan is for WordPress 5.0 to default to Gutenberg automatically. There will be many shocked site owners who have auto-update turned on who wake up to broken sites when this happens.

Before 5.0 is released, it is important to have a current backup and the classic editor plugin installed on your site. It allows sites to revert to the existing editor.

Note that the information on this plugin currently says, “Warning: This is beta software, do not run on production sites!

Gutenberg was originally expected to have already rolled out. As of now, a firm date for the release of 5.0 is not set. But the best estimate at this time is August, 2018.

Be Sure to Do This BEFORE 5.0 Rolls Out

Not everything in an existing WordPress installation is going to run on WordPress 5.0, code name Gutenberg. Before they roll out 5.0, each site’s configuration should be tested using the Gutenberg plugin which is already available.

They do NOT recommend installing it on a live site. It would be wise to install a test site on your computer’s hard drive or at a hosting company to use for testing.

Note that there is still a small chance that Gutenberg could run fine on a clone of your site, but cause an issue on the live site. This is because versions of PHP, MySQL or MariaDB, or HTTPS support could be different.

Non-technical business personnel, bloggers and freelancers may need to hire someone to deal with testing. Use these cloning instructions or the video below or pay someone else to do before 5.0 rolls out:

Once you have an identical copy of your site installed, carefully check to see what works and what doesn’t. This could be challenging because you may not know what to test.

Check to see if videos still work, images display properly, contact forms work, and anything in widgets appears. Read to the end for more advanced recommendations on how to deal with this major change.

Existing Themes Are Not Fully Compatible

Theme Forest themes will probably all be updated and work fine. They are helping their developers push through compatibility updates where needed. 50 of their themes are currently listed as ready.

Some WordPress theme frameworks have major work to do while others feel they are ready for the rollout. There are over 56 frameworks whose status is unknown.

Genesis is on top of the changes and feels their framework and themes will be ready.

StudioPress has no information about Gutenberg on their site. Chris Pearson responded:

“The only thing Thesis 2 will need is a Box that specializes in outputting content produced in the Gutenberg editor.

Thesis 2 will get whatever treatments end up being necessary; existing T2 Skin users may need to update their templates to “use” Gutenberg.”

Thesis 1 will not be updated. Sites running on Thesis 1 will need to stay on the old editor for now and make changes before it is phased out.

Elegant Themes is aware and has published multiple blog posts about Divi vs Gutenberg. This video explains how WordPress used to work and how Gutenberg is similar to builders like Divi:

What to Do if Your Existing Theme or Framework is Not Compatible

What if you are running Thesis 1 or any other framework or any other untested theme? Asked what site owners should do, Web developer and WordPress specialist Donna Cavalier told us:

“Leaving Thesis might be a huge deal, or it might be no big deal at all. If you’ve got a lot of custom code going on, you might want to rethink everything. Do you really need it all? Why? Would another approach be better?

Each use case will be different. Some will only need to change themes and make a few adjustments. Others may need a complete site overhaul.

WordPress Gutenberg Editor Might Mess Up Some Sites

Image source: Screen capture from above Envato video.

The best way to find out is to clone the site, change themes on the clone, and see what happens. That half-hour experiment is worth months of wondering.”

She offers additional advice in Gutenberg Will Confuse The Crap Out Of Almost Everyone.

Will Your Plugins Work with Gutenberg?

The Gutenberg compatibility chart shows that as of 7/23/18 an estimated 80.46% of the 55,433 plugins in the WordPress repository have not been tested to be compatible with Gutenberg.

Some popular plugins have announced they are ready:

  • Contact Form 7 and Gravity Forms have Gutenberg blocks built.
  • Caldera Forms is listed as ready.
  • Yoast is working on compatibility.

According to Epstein, most plugins are not expected to have issues because they rarely modify the editor. She estimates only 15% of plugins will be affected.

This includes my own GrowMap anti-spambot plugin and the popular plugin CommentLuv. A cursory review showed they seem to be safe to continue using even though Andy Bailey, the developer of CommentLuv is not available to update them.

Epstein commented that they seemed well-coded, so even though they have not been updated, they post little security risk.

Gutenberg Impact on Ecommerce Platforms

Ecommerce platforms have complex challenges, complicated by changes the Gutenberg development team keeps making. But recently, a feature freeze was made so that third parties can work on compatibility.

Woocommerce has released a Gutenberg block as a plugin. Read about their solution here and search for “Wootenberg” to find future information on it.

Hopefully, other ecommerce solutions using WordPress will also provide migration paths.

Rush to Mobile Negatively Impacts PC Experience

How sites display on mobile devices is over-riding the optimum design for experiencing them on desktop and laptop. A 28″ monitor has a viewing space of about 24.5″ wide by 13.5″ tall.

Gutenberg removes sidebars. Sites will be one large viewing space. Give some consideration to what the optimum width will be and what your sites will look like on large PC monitors.

It can be difficult to read text that is very wide. So most likely, PC users will be viewing many sites that are a narrow strip down the middle of their monitor with nothing on either side.

What Happens to Old Content in Gutenberg?

When a site gets converted to Gutenberg, it attempts to break all the components up into blocks. But if it runs into an error, it will put the entire post or page into one block.

Sites running the Gutenberg Ramp plugin may have some post types running in the old editor and other post types using the new editor.

Never Volunteer to Be on the Bleeding Edge

We had a saying among IBM Customer Engineer (CE) computer technicians: do not volunteer to be on the bleeding edge. What that means is it is best to not test changes on your live site.

Wise CEs did not install new software on live systems until it had run for a while on other systems and the worst bugs were already fixed. Some systems (hospitals, police, fire, banking) were more critical than others.

This is good advice to remember for small businesses running WordPress, too. If your site generates income and downtime would cause serious financial implications, hold off for a while.

RECOMMENDATION: Install the Classic Editor plugin and wait until Gutenberg has been more thoroughly tested, bugs resolved, and themes and plugins have a chance to improve to match it.

Follow this advice especially if you have an ecommerce site. Apply change management strategies to minimize your risk.

Do your research first to find out if what manages ecommerce on your WordPress site is ready for Gutenberg.

It won’t hurt to stay on the old editor for at least several months. Some may choose to stay on it as long as that is possible.

Photo via Shutterstock 20 Comments ▼


Gail Gardner


Gail Gardner Gail Gardner is the Small Business Marketing Strategist who founded GrowMap.com and co-founded the Blogger Mastermind Skype group. She mentors small businesses and freelancers, especially writers and social media marketing managers.

20 Reactions

  1. Alex Yong

    Great conclusion. Honestly, Automattic should give users the choice to stay on the Classic Editor forever. If that’s the compromise, it’s one I can live with. “I love having something forced down my throat!” said no one ever. I have brought this great article to the attention of Automattic’s CMO. Thank you.

    • Gail Gardner

      Hi Alex,

      You’re not alone in that request. Some believe that is actually what will happen. But many feel that eventually the old editor will have to go away and everyone will have to move to Gutenberg.

      But that is down the road. Will Patton tells me that the old editor can’t take advantage of newer features in browsers. So there is actually a technical reason why we will want to convert sites over time.

      The key thing is to not jump in before you’re ready if your site is important to how you make a living. They have said it is going into core and it is going to default to on. When and if that happens, a lot of people are going to be in for a surprise.

      • Gail,

        I will show this post to my web maker. He has told me about the upcoming changes. I like how they named Gutenberg. ­čśë

        It will be interesting to follow along the developments of WordPress.

  2. Aira Bongco

    I hope it doesn’t hurt my sites. Most of my sites are on WordPress.

    • Gail Gardner

      Hi Aira,

      It depends on what is on your sites. The safest thing to do is go ahead and install the Classic Plugin on each of them. Eventually, Gutenberg will default to on and that is when a site may have issues. The link to the plugin is in the content under the sub-heading “Gutenberg Plugin Confusion”.

      The Classic Plugin ensures you don’t switch to Gutenberg until you’re ready. With it, you stay in the editor we have now.

      You can also click through to the page that shows which plugins are known to be compatible.

  3. This is big. Thanks for the heads up.

    I see a future headache in my future.

    • Gail Gardner

      Hi Robert,

      Yes, this is really huge. To see how different it is, check out the videos that show it in action featured in this post. But at least people actively using their blogs should see the prompts giving them a heads-up about it. Those are expected to roll out on 7/31/18 for the first time.

      Unfortunately, many who do see the prompt may ignore it because they don’t understand what it means for them. And the majority of WordPress site users may not log into their dashboards at all.

      Even WordPress developers I contacted who are actively managing sites for others were not aware it is coming. Meanwhile, those active in the Gutenberg community seem to think that everyday users are active in their community. Most ordinary users don’t even know where it is.

      The biggest issues will be:

      1) Slow response times at hosting companies hit by enormous call volumes. That can be mitigated by taking more time to default to Gutenberg to spread out the transitions.

      2) A shortage of developers available to troubleshoot any issues with React. They are being told they won’t need to learn it. But some, notably Envato’s Dom Hennequin, expect to need React experts.

      So developers interested in income opportunities should position themselves as being available to assist with Gutenberg issues NOW and start learning to troubleshoot potential problems in React. There is a link in the post to resources for learning React under the Freelance Income Opportunities sub-heading.

      • Gail Gardner

        And I forgot to mention that anyone interested in assisting site owners TESTING with Gutenberg should hang out their shingles and pro-actively start offering.

        They need to install the Classic plugin for them and add “Gutenberg testing” as a service on their sites. Start reaching out to WordPress users offering to ensure their sites are ready to migrate.

        Even though it is tempting to stay on the original editor forever, the new editor is expected to load faster in browsers and uses capability not available in the old one. So we will want to move important sites over sooner or later.

  4. Thanks for a great article and looking at Gutenberg from so many different angles including some I hadn’t considered.

    Due to the sheer magnitude of WordPress sites worldwide and so many probably running old, unsupported themes and plugins, I am wondering if WordPress will organically split off into two versions like Magento 1x vs 2x.

    • Gail Gardner

      Hi Linda,

      There have been scattered requests for a fork, but I haven’t seen anyone volunteering to undertake the upkeep of the existing version.

      Some feel that the Classic Editor plugin should never go away. But Matt Mullenweg at Automattic has been pretty clear that they want everyone to migrate.

      What is unknown is how long that may take. Many sites, specifically those running Thesis 1, will have to do something in order to move to Gutenberg.

      All sites should test (although many may just try it, and if they break, then decide what to do.)

  5. For some reason the page wants to reload before I can complete a comment. The number of ads on this site make it much more difficult to use than Gutenberg. I’ll try to be brief.

    There’s an important correction I need to make to this article. Gutenberg does NOT affect your existing content until and unless you edit it. You can leave those hundreds of past blog posts alone, and they should be just fine.

    Good hosting companies (and you should be using one: isn’t your business worth $30/month?) let you create a staging site (a copy of your site for doing tests on) easily. Make a copy of your site, install Gutenberg, and see what happens.

    I’ve been testing Gutenberg for almost a year, and it’s a MUCH NICER experience than using the current WP visual editor. Much. Much. Nicer. Even at the beginning when it was really buggy. No more ugly, confusing shortcodes. If the plugin developer hasn’t created a block yet, put your shortcode into the generic shortcode block and watch it expand before your eyes, to show you what a website visitor sees.

    Yes, it’s possible there will be some conflicts, especially if you use plugins that haven’t been updated. But there’s no need to take an alarmist approach. We won’t see WordPess 5.0 until Gutenberg has been tested extensively and the team behind it is confident that they’re not going to break 30% of the Internet by introducing it. (Which means, oh, sometime in 2019, I’d think.)

    Try Gutenberg. Please. Get your developer to test it if it’s not easy for you to create a staging site yourself. (If your developer doesn’t know what Gutenberg is, get another developer.) Don’t try it in production yet, but try it.

    • Gail Gardner

      Hi Sallie,

      I had the content reviewed by 2 developers on the Gutenberg team and another developer who has tested Gutenberg on sites. I don’t believe I said it did anything to existing content except to attempt to put it into blocks.

      But some themes are not compatible so there is no telling what will happen if they’re not tested and it goes live.

      Developers just can’t seem to understand that most WordPress users have NEVER installed WordPress. They have never installed a Theme. They may or may not have ever installed a plugin. They have NO IDEA how to create a test site or do backups or clone a site.

      No matter how many times I tell them that USERS only USE WordPress and that’s it, they either can’t conceive of the concept or don’t want to believe it.

      And honestly, most users need to leave their sites alone. One comma in the wrong place or one file edited incorrectly can take down a site. It makes more sense to have an expert tweak your CSS which will take them 10 minutes than it takes to crash your site and then scramble to find a tech who might take hours to figure out what you messed up.

      I know that people who love drag-and-drop editors feel that Gutenberg is “a MUCH NICER experience”. But that is an opinion based on their preferences and background.

      Personally, I detest using site builders. I’m a wordsmith. I don’t want to waste time playing with layouts and designs. I want to research, organize, and present necessary information in the most efficient way possible.

      Trying to find a block for every little thing is a painful experience for someone like me. And because I am decades past 40, tiny fonts typed into little boxes is even more annoying than trying to figure out where someone put what I need.

      Another misconception that developers have is that typical blogs use shortcodes. I had blogged on WordPress for 8 years before I ever needed to find out what the heck a shortcode was. That was for a membership site. That is the one and only time I have ever used a shortcode. And no, I didn’t install that, either.

      I have no idea what it is developers think we are using shortcodes for as I have contributed on dozens of sites and have never seen them in use on any of them.

      Over 80% of plugins still aren’t tested as compatible. But, fortunately, Mika Epstein has explained that most plugins will not be affected.

      It is not alarmist to not want to find out the hard way that the site you rely on to make a living is going to break. I have known programmers personally since the very first IBM PC. They would have a hard drive full of nothing but applications they were playing with and no data and did no actual production.

      Developers are like engineers. They like to install and tweak and break and learn to fix what they broke. But users are not developers. We just want our sites to work. We do NOT want to lose productivity, spend hours frustrated, or pay developers if we can help it. That is the part that the team behind Gutenberg doesn’t seem to understand.

      Yes, we are going to have to eventually pay someone to test Gutenberg on our sites. And if our sites won’t run it, we will eventually have to pay someone to change the site to make it work. That is money we have to earn first.

      I am fortunate that I know developers and can earn more money if I need it. But many users do not have a developer and do not know any. They have to hire someone blind or on someone else’s recommendation they HOPE knows what they’re doing. Maybe they do; maybe they don’t; you never know until you actually work with someone.

      Will Patton tells me that getting off the existing editor is necessary to take advantage of new features in browsers. So someday in the future, the old editor will probably go away. This post is an attempt to make people aware so they can start planning what they must do. And so that they get the Classic Editor plugin installed – for now.

  6. FYI WordPress auto-updates only happen for *minor* releases, like 4.9.6 to 4.9.7.
    Major releases, like 4.9.7 to 5.0.0, will not happen automatically. The site owner needs to choose to do a major update.
    So folks shouldn’t wake up to a broken site.

    • Gail Gardner

      Hi Michael,

      Thank you. That is good news. But they still need to understand that before they accept an update that defaults to Gutenberg being in core, that is isn’t just another major release.

      This one, they really need to have the Classic Editor running first unless they have had their site thoroughly tested and know everything in it works with Gutenberg.

      They also need to learn a completely different way of creating content, ideally not when they’re up against a deadline to publish. It is going to take many people quite a while to sort it out at least the first time.

  7. Hi Gail,

    My name is Bjorn, from WPLearningLab and creator of the second video embedded in this post.

    First, thanks for sharing my video!

    Second, great job on this article. It is the most thorough Gutenberg write up I’ve seen. Thanks for taking the time to create it!

    Third, thanks for sharing responsible advice about hosting. You should see my recent video about BlueHost (owned by EIG) and SiteLock (partially owned by EIG). If you check it out pay special attention to the comments on the video. It could make for a good blog post.

    • Gail Gardner

      Hi Bjorn,

      Thank you for taking the time to read and comment. The research took a really long time, especially since some aspects were changing while I was trying to write it. I can just imagine all the people calling their hosting companies when something in their site doesn’t work – and the hosting company’s customer service having no idea where the issue is.

      Yes, EIG keeps buying up hosting companies which is usually not a good thing because corporations’ primary responsibility is to increase profits wherever they can. I’ll look for your video.

      Your videos are very educational. I’m glad you didn’t mind me using one in this post. I actually watch every video beginning to end before choosing the very best to use in content I write.

  8. Hi
    I have tried the Gutenberg plugin on a test site and not really impressed as it looks half finished to me. I hope they are going to add more blocks in the core version.

    I use Shortcodes Ultimate on some websites and Bootstrap 3 Shortcodes on another 2 websites and there is no way you can add the shortcodes in Gutenberg. That means my websites will have to be redesigned or edited with the new code.

    Also in Editor or HTML view there’s no basic Code Editor which can save time.

    I use Mesmerize theme that has a built in builder and looks far better and is easier to use adding blocks. The version I am using is the free version so I can only use the builder on the Home page. Once I installed Gutenberg on this website I wondered what impact did it have on the home page. Well everything is alright as it just wants to use the Customizer but the other pages are using Gutenberg.

    But if I bought the full version of Mesmerize theme then all my pages would be using the theme’s built in builder so can’t see the point with Gutenberg….

    Also noticed that blocks are too close to one and another especially one below 2 columns so trying to select a block in a above right column was very difficult. In the end I had to add an empty block to do it.

    This is not ready for Version 5 especially this year or until it is sorted out. I know there will be bugs with it being new but there’s many things wrong with it.

    Installed Classic editor for now until they sort it out….

    • Gail Gardner

      Hi Colin,

      Sorry, I must have missed the email letting me know you commented. Yes, other builders like Divi and the one you use are much better. And some of us aren’t fans of page builders, anyway, so the last thing we want is to try to write in one.

      I’m glad you tested and it didn’t break your site too badly. I suspect there will be a very large percentage of WP users who hope that classic editor will never go away as they have no desire to ever switch.

  9. Gail Gardner

    UPDATE: Gutenberg is set to roll out 12/06/18. If you do not want to lose the existing WordPress editor, install the Classic Editor plugin NOW. There are still many bugs in Gutenberg.

Leave a Reply

Your email address will not be published. Required fields are marked *

*