Call for Testing: WordPress 5.9 RC 1

The WordPress 5.9 Release Candidate 1 is now available on VIP for sites running 5.9 branch. Open a ticket if you’d like to have your non-production sites switched to WordPress 5.9 for testing.

WordPress 5.9 is slated for release on January 25, 2022, but your help is needed to get there—if you haven’t tried 5.9 yet, now is the time!

“Release Candidate” means that the new version is ready for release, but with millions of users and thousands of plugins and themes, it is possible something was missed. So far, contributors have fixed 346 tickets in WordPress 5.9 including 109 new features and enhancements, and more bug fixes are on the way.

What is being added or changed?

The WordPress 5.9 RC 1 Release Article provides a full list of changes; below you’ll find some of the changes that are most likely to impact the Enterprise WordPress space. As with any release, testing your application prior to release will ensure compatibility with the latest features and security.

WordPress 5.9 will mark the first version where all major Full Site Editing features are available for use. WordPress 5.9 also introduces the next generation of themes in the form of block themes that allow for greater customization and simpler site and content building. Some features in 5.9 (such as Full Site Editing) are only available with a block theme.

In addition, all themes will see exciting changes in the form of design tools, UX improvements, pattern improvements, performance enhancements, and more.

Watch a video demo: 4-minute walkthrough and 11-minute walkthrough

  • Block themes – Block themes allow you to use blocks to edit your entire site. After enabling a block theme, expect to see a new menu item under Appearance called “Editor (beta)” with some unique flows in place to help you navigate between template, template parts, and your homepage.
  • Theme.json Improvements – theme.json provides a consolidated and canonical way to manage features and styles, reducing the need for many theme support flags or alternative methods. With this release, it’s even easier to enable/disable features and set default styles for both your entire site and individual blocks.
  • Styles interface – 5.9 introduces a beautiful interface to interact directly with various style properties. This system works hand in hand with theme.json to provide a sense of “global styles”, allowing you to easily switch up the entire look and feel of your site without switching themes.
  • Navigation block – The Navigation Block enables you to edit your site’s navigation menu, both in terms of structure and design. With full control of your site’s navigation in terms of look, feel, and placement, you have the ability to build out more complex menus with elements like search blocks, social icons, site icon, and more.
  • Block Pattern enhancements – These include a more cohesive experience for exploring patterns and Featured Patterns now appearing first in the Inserter… making it easier to find rich, robust patterns. You can even submit your very own patterns to the pattern directory with open submissions.
  • Design Tools – New options, a revamped interface, and more allow you create vastly different layouts from a few simple slight changes to more radical and complex options… whether it’s a featured image you want to size correctly, or being able to adjust your social icons for an automatic best-fit, or a paragraph you want in a different size.
  • Focused Template Part Mode – This new view creates a space to focus specifically on editing a single template part, like a header or footer.
  • Locking at the block level – This new feature allows you to do things like lock a pattern so folks on your site can customize the pattern with their content but keep the integrity of the pattern itself in place. Alongside template level locking, now you can lock individual blocks to prevent moving or removing them.
  • Post Comments Block – The Post Comments block displays all comments for a post or page along with a form for folks to submit comments. Future iterations will provide greater levels of customizations and a separate Post Comments Form block.
  • JQuery UI and Rest API changes – The JQuery UI is updated to 1.13.0; we recommend reviewing the changes in the update. ${appUrl}/wp-json/wp/v2/menus is now supported via Rest API, which may be useful to customers developing headless or decoupled solutions.

How to test

  1. We recommend updating your local development environment to the release candidate using the Beta Tester plugin or updating it to track 5.9 (i.e. trunk) via either the Subversion or GitHub repos.
  2. You can have your non-production sites switched to WordPress 5.9 now. If this is something you’re interested in, please open a ticket and we can set it up for you.

Testing is a vital part of polishing the release and a great way to contribute. ✨

Questions?

If you have testing feedback or questions, related to this release, please open a support ticket and we will be happy to assist.

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.

WordPress 5.0: New release date announced

This notice relates to the following platforms: WordPress.com VIP, VIP Go

December 6th is the new target date for the WordPress 5.0 public release and announcement. We’ve been working behind the scenes to test scenarios and sharpen our plans for a smooth release process for all VIP’s. Here’s what that means for WordPress VIP sites:

WordPress.com VIP

As you know, the merge process on WordPress.com is a gradual release and the progress to date already closely matches what is in 5.0. There are still a few items to take care of and we’re hoping to have that work complete by the end of the week. As a reminder, your publishing experience will remain the same as it is in 4.9.8, with the Classic Editor. So basically, things should remain business as usual when 5.0 is fully merged in.

VIP Go

We are targeting Tuesday, December 11th (starting at 2000UTC) as the release date for our VIP Go hosting platform. This will allow an additional few days for testing while also avoiding a Friday or Monday release. Whether or not you’re already using Gutenberg, your publishing experience will remain the same as it is in 4.9.8.

Testing on VIP Go

If you are already using the Gutenberg plugin, the safest path for the update is to first test against and then use the latest version of the plugin, ahead of the WordPress 5.0 release. Gutenberg will not be detected and properly activated if you’re using a version of the plugin older than 4.1. Additionally, version 4.6.1 introduces a fix for block parsing that protects against malformed content breaking sites (originally introduced in 4.4). 

As always, we recommend testing out plugin version updates on a non-production site first before updating your production site. 

Help with the Release Candidate Testing

WordPress 5.0 RC3 came out today. If you’d like to help out with testing, follow the instructions here or drop a note to your VIP support team.

What’s Next?

5.0.1 will open for commits soon, and you can expect minor version updates to be more frequent. As before, if new information arises that indicates the software is not stable, we will adjust or remove the target date. Follow the VIP Lobby to stay up to date.

If you’ve been waiting for 5.0 to really start experimenting with Gutenberg, get ready! We’re excited to see what amazing things get created with the new WordPress editor on VIP!

WordPress 5.0: Timing update

This notice relates to the following platforms: WordPress.com VIP, VIP Go

The first WordPress 5.0 Release Candidate was made available on November 23rd, an important milestone as we near the release of WordPress 5.0. This was a few days after the original target date, and it has been stated that the November 27th release date will be shifted back based on the feedback received from the Release Candidate.

This news means different things depending on which VIP platform you’re on:

WordPress.com VIP

WordPress 5.0 implementation is proceeding as scheduled this week. As mentioned before, the biggest change in WordPress 4.9.8 for most people is that the editor known as Gutenberg will become the default editor. For WordPress.com VIP clients, your publishing experience will remain the same as it is in 4.9.8, with the Classic Editor. So basically, things should remain business as usual when 5.0 is fully merged in.

VIP Go

We had previously announced that VIP Go would update to WordPress 5.0 on November 28th, one day after the previous WordPress 5.0 target release date. With the target release date postponed, we’re also postponing the update on VIP Go.

We’ll announce the new update date once a new WordPress 5.0 release date has been announced. It will likely be 1-2 business days after that date. This separate Lobby post will provide VIP Go-specific loading scenarios and instructions for those clients already taking advantage of the new editor.

More time for testing

A silver lining of the delayed release is that this gives VIP Go sites more time to test WordPress 5.0 ahead of its release. If you’re on VIP Go, we can update any of your non-production environments to the 5.0 release candidate branch now. Just open a Support ticket or contact your VIP account manager.

Alternatively, on VIP Go, you can continue to test your existing sites using the Gutenberg plugin.

WordPress 5.0: Deployment plans and what to test for

This notice relates to the following platforms: WordPress.com VIP, VIP Go

Based on the current release schedule, WordPress 5.0 is expected on November 27. This post runs down how and when we plan to deploy 5.0 on our platforms, and what to expect.

When will the changes be deployed?

WordPress.com VIP: We will be deploying incremental updates leading up to the public release with the bulk of the enhancements pushed out during the week of November 27, 2018.

VIP Go: The release will be deployed to all Go sites on November 28, 2018.

Please note that the deployment dates are subject to change if critical issues are discovered during testing or the public release is delayed. We’ll post updates to the Lobby if the dates do change.

What’s changing?

WordPress 5.0 includes only one major change: the introduction of the highly anticipated new block editor, known as Gutenberg. But don’t worry, we have configured our platforms to keep your current editor choice intact even after WordPress 5.0 is deployed.

On both platforms, we will have Gutenberg Ramp in place, which means that your editor of choice will not change with WordPress 5.0. If you are currently using the default (classic) WordPress editor, you will continue to see it in your admin.

Gutenberg Ramp plugin update

VIP Go users: As part of WordPress 5.0 preparations, we have also updated the Gutenberg Ramp plugin. The main change to be aware of is that the selective loading that Ramp is designed for will only work with versions of the Gutenberg plugin that are version 3.5 or newer. As a reminder, it’s best to be using – or to have at least tested against – the Gutenberg 4.2 plugin version prior to the WordPress 5.0 update. Learn more about Gutenberg plugin versions and how to best prepare for the transition.

What do I need to do?

We highly recommend updating your local development environments to the beta release using the Beta Tester plugin or updating it to track the 5.0 branch via either the Subversion or GitHub repos. (For example, Chassis users can switch their installs to a separate checkout.) Learn more about Beta testing.

For sites on VIP Go, you can have your development sites switched to the 5.0 branch as well. If this is something that interests you, please reach out and we can set it up for you.

What if I find Issues?

If you have testing feedback or questions related to this release, please open a support ticket with details and we will be happy to help.

Gutenberg users: Stay current with the plugin ahead of WordPress 5.0

This notice relates to the following platforms: VIP Go

As previously announced, the WordPress 5.0 update is targeting a November 19th merge. Many of you are already using the Gutenberg plugin (loaded by Ramp) on your sites, and we applaud you! We specifically built Ramp to support the development needs of those early adopters of Gutenberg, as well as maximize the opportunity to test out the new editor. However, as we near the WordPress 5.0 release, there is an action item for you early adopters:

Because of the way WordPress 5.0 loads the new editor (Gutenberg), all sites currently using the Gutenberg plugin must be using version 4.1 or higher. Gutenberg 4.1 release candidate is already available, and there is an expected UI freeze with this version. Gutenberg 4.2 is expected to signal the API freeze, and mark what is expected to be the final version of the editor that gets included in WordPress 5.0.

Recommended approach

To minimize risk of unexpected incompatibilities with the editor that ships in WordPress 5.0, we recommend getting your site updated to the latest version of the plugin now, and planning to update again with each incremental release. It’s imperative to be updated to at least Gutenberg 4.1 ahead of the WordPress 5.0 release, as previous versions will become incompatible.

Rather than waiting for Gutenberg 4.2 and just updating then, we recommend updating to 4.0 or 4.1 (release candidate available) now so you have more time to test this version and make any updates if needed. This is increasingly important for those currently running versions of the plugin that are more than a few releases behind (3.6 and older). Then, the update to 4.2 should be a very minimal update.

But everything will stay the same, right?

Yes! After the 5.0 merge, your editorial experience will stay the same. Gutenberg’s functionality will be opt-in for VIP clients.

For those that still haven’t tried out the new editing experience, you can try it out here to learn more about the block-based editing experience of the (near) future. If you decide you want to enable Gutenberg, you’ll be able to take advantage of our Ramp plugin, which allows you to selectively enable Gutenberg via post type or post ID.

For everybody, keep an eye out for future Lobby posts with more WordPress 5.0 details as well as VIP News for exciting things some of our clients are doing with the new editor.

WordPress 5.0 Proposed Timeline

This notice relates to the following platforms: WordPress.com VIP, VIP Go

Before we dive into the exciting news, let’s first clarify that no action is required. 

It’s hard to believe it’s been almost a year since we first mentioned Gutenberg, the new visual editing experience for WordPress! Since then, we’ve been working hard to inform, educate, prepare, and generate excitement for the possibilities that this will bring to editors.

It’s understandable if Carly Simon’s “Anticipation” song is running through your head. 

For those as excited as we are, we have great news… WordPress 5.0 – the first version of WordPress to have Gutenberg available as the default editing experience – will be here soon! The project’s timeline and features can be tracked on the main core blog. The proposed dates for the public release are below. Please note that both WordPress.com and VIP Go will be updated shortly after the public release:

Beta 1: October 24, 2018
Release Candidate 1: October 30, 2018
Release: November 19, 2018

As with any software release, last minute changes may happen and these dates may shift a few days. If it needs to be bumped back more than 8 days, this would be the second proposed release schedule:

Secondary Release Candidate 1: January 8, 2019
Secondary Release: January 22, 2019

Click here to view a continuously updated and more detailed date breakdown.

What does that mean for your VIP site(s)?

After the 5.0 merge, your editorial experience will stay the same. Gutenberg’s functionality will be opt-in for VIP clients. If you decide you want to enable Gutenberg, you’ll be able to take advantage of our Ramp plugin, which allows you to selectively enable Gutenberg via post type or post ID.

For those that still haven’t tried out the new editing experience, you can try it out here to learn more about the block-based editing experience of the (near) future. For everybody, keep an eye out for future Lobby posts with more WordPress 5.0 details as well as VIP News for exciting things some of our clients are doing with the new editor.

Note: updated to reflect the Beta 1 release on October 24. The other dates have remained unchanged.