WordPress 5.0 and Gutenberg on VIP Go

This notice relates to the following platforms: VIP GoVIP Go VIP Go – a hosting environment separate from WordPress.com for VIP sites

Quick preview:

  • Plan to keep using Classic Editor? No action needed
  • Plan to use the version of Gutenberg that is part of WordPress 5.0? Use our simple helper function to enable Gutenberg on areas you choose.
  • Plan to keep using the plugin for Phase 2 updates? Make sure you’re using at least v4.6.1 of the plugin and add one line of code to vip-config.php
  • When will this happen? Tuesday, December 11 starting at 2000UTC   

Learn more about WordPress 5.0

Last week, we at VIP all cheered as WordPress 5.0 was released to the community. It was an exciting day and we’re equally excited to bring WordPress 5.0 and Gutenberg, the new WordPress block editor, to our VIP Go clients. As mentioned before, we will be updating our VIP Go sites to WordPress 5.0 on Tuesday, December 11th starting 2000 UTC

We’ve been committed to maintaining our clients’ editor preference as part of the 5.0 update, in an effort to allow you to plan your integration of the new editor at your own pace. Because not all clients want to use the new editor in the same way, we have options for how you can use it going forward:

Still not quite ready for the new editor?

No problem! If you haven’t had the Gutenberg plugin installed with WordPress 4.9.8, you’ll continue to use the Classic Editor. No action needed… but you really should check out the new editor soon!

You’ve been using Gutenberg and are ready to stop worrying about plugin version updates:

Even better! With Gutenberg included as the core editor in WordPress 5.0, you can stop worrying about keeping plugin versions up to date and simply use the new core editor. Make sure you have tested your site against at least version 4.2 of the Gutenberg plugin for compatibility. If you go one step further and test against the newest version (4.6.1), that will give you the best indication that all of your custom blocks are compatible. Next, make sure you are using at least version 4.1 to avoid compatibility issues and conflicts with WordPress 5.0 (we highly recommend at least v4.6.1). As long as you’re running at least the Gutenberg 4.1 plugin, no action is needed to keep using those beautiful blocks with WordPress 5.0.

You’ve been using Gutenberg and want to keep using the plugin to stay current with Phase 2 progress:

Phase 2 is about thinking outside the box, namely the post and page box, to allow Gutenberg to handle entire-site layouts. We will replace widgets with blocks, so any block will be able to be used in any registered “sidebar” for legacy themes, and we will upgrade “menus” to a navigation block.

Matt Mullenweg

Rock stars! We can’t blame you for wanting to get in early on the Phase 2 action. In order to keep using the Gutenberg plugin rather than the new WordPress block editor, you need to be using at least Gutenberg version 4.5.1 and then add the following line of code to /vip-config/vip-config.php:

define( 'GUTENBERG_USE_PLUGIN', true );

While 4.5.1 is the minimum version needed to keep using the plugin, we strongly urge you to use at least 4.6.1, which introduces some parsing improvements. 

Phase 2 leads have been announced and you can expect to hear more about the future phases of Gutenberg right here in the VIP Lobby. 

Wait, I have more questions!

And we have answers! You can check out our documentation to learn more about Gutenberg at VIP overall, including best practices for loading Gutenberg on VIP. As always, reach out to us in Zendesk if you’re still not quite finding what you need.