New Release: WordPress 5.4

WordPress 5.4 has been released to the VIP Platform. Named “Adderley” in honor of jazz trumpeter Nat Adderley, this latest release includes many new features for Gutenberg alongside accessibility improvements and various developer-focused changes.

The Highlights

WordPress 5.4 merges ten releases of the Gutenberg plugin, including the most recent, Gutenberg 7.5. This means there’s a long list of exciting features including two new blocks—social links and buttons. The former lets you add social media links anywhere within a post. The latter makes it easy to add buttons side by side within a post.

The new release also adds new color customization options including gradients in the Buttons and Cover blocks, toolbar access to color options in Rich Text blocks, and for the first time, color options in the Group and Columns blocks.

For accessibility, WordPress 5.4 introduces clearer block navigation with block breadcrumbs plus better tabbing and focus when using keyboard navigation.

Developers can look forward to many features and improvements including two new actions related to custom menus:

  • On the Menus admin screen, wp_nav_menu_item_custom_fields fires just before the move buttons of a nav menu item in the menu editor.
  • In the Customizer, wp_nav_menu_item_custom_fields_customize_template fires at the end of the menu-items form-fields template.

Block styling is also simplified. Negative margins and default padding are gone! Now you can style blocks the way you need them.

Fullscreen Mode Enabled by Default in the Editor

Beginning with WordPress 5.4, Gutenberg opens in fullscreen mode by default the first time the editor is opened in a new installation or on a new device.

Individual users can disable this setting by switching modes in the editor menu.

This editor preference is stored locally for now, which means it will reset to fullscreen mode any time the editor is used on a new device or in incognito mode or if user preferences are reset.

We understand some users may want to disable this option, preferring to default to the traditional editor view. The following code snippet can be adjusted and added to any site’s theme files to disable the fullscreen mode default. Please note, this only applies to sites using the Gutenberg editor; the classic editor will be unaffected.

function disable_editor_fullscreen_by_default() {
  $script = "jQuery( window ).load(function() { const isFullscreenMode = wp.data.select( 'core/edit-post' ).isFeatureActive( 'fullscreenMode' ); if ( isFullscreenMode ) { wp.data.dispatch( 'core/edit-post' ).toggleFeature( 'fullscreenMode' ); } });";
  wp_add_inline_script( 'wp-blocks', $script );
}
add_action( 'enqueue_block_editor_assets', 'disable_editor_fullscreen_by_default' );

Learn More

For more details about the 5.4 release (including specific changes), please see the announcement post and Field Guide.

Questions?

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

WordPress 5.3: Final Deployment Update

WordPress 5.3 was released to the general public on November 12, 2019, and we’ve already rolled out the latest release across the WordPress.com VIP platform. This update specifically pertains to sites running on VIP Go and includes a final call for testing and deployment timeline.

WordPress 5.3 Deployment Timeline on VIP Go

We’ll be upgrading all sites across the VIP Go platform to WordPress 5.3 on Tuesday, December 3, 2019 at 8pm UTC / 3pm ET / 12pm PT.

As with all upgrades, this date is subject to change if critical issues are discovered during testing. If the upgrade date does move, we’ll keep you updated through additional Lobby posts.

Final Call for Testing

In a recent Lobby post, we detailed the many enhancements included in the latest WordPress release. If you haven’t reviewed that post already, we encourage you to do so.

For local environments, we highly recommend updating to the beta release using the Beta Tester plugin or updating to track 5.3 via either the Subversion or GitHub repos. (If you’re using VVV, one of the default sites will already be tracking 5.3. For Chassis users, you can switch your install to a separate checkout.)

WordPress 5.3 is also available for development environments on VIP Go. If you would like to have non-production sites switched to 5.3 for testing purposes, please open a ticket, and we can set that up for you.

How Should I Surface Issues?

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

Call for Testing: WordPress 5.3

WordPress 5.3, named “Kirk” in honour of jazz multi-instrumentalist Rahsaan Roland Kirk, is now publicly available. For sites on WordPress.com VIP, we’ve already rolled out the bulk of the enhancements in the new release. For VIP Go sites, we’re still on track to upgrade all sites on Tuesday, December 3, 2019.

Today, we want to share updates on the enhancements in WordPress 5.3 to help you test your application ahead of the new release.

Enhancements in WordPress 5.3

A large portion of the enhancements in WordPress 5.3 is directed at the block editor originally introduced in WordPress 5.0.

Improved Speed in Block Editor

WordPress 5.3 brings enormous speed improvements to the block editor, particularly when working with posts that have hundreds of blocks. Here’s a benchmark of the performance increase with the upcoming release for a post containing ~1,000 blocks and ~36,000 words.

A table illustrating the performance improvements for Gutenberg in 5.3

Upgrades to Existing Blocks

Many existing blocks received an upgrade. For example, the Columns Block now includes additional layout options and the ability to set the width on a per-column basis.

An example of the Columns Block in WordPress 5.3

Other blocks receiving an upgrade include:

  • Table Block – You can now add header/footer rows directly in the block customization options.
  • Button Block – You’ll have more control over color selection and border radius.
  • Latest Post Block – You’ll be able to add excerpts (and control their length) of your latest posts.

New Gutenberg Blocks

The WordPress 5.3 release adds a new social icons block that enables you to place social sharing icons virtually anywhere within a post or page.

An example of the Social Link Block from WordPress 5.3

You can also group blocks together and interact with them as a group, making it easier to design reusable sections and templates for your content.

An example of how you can group blocks together and call up a group within WordPress 5.3

Accessibility Improvements

WordPress 5.3 introduces many accessibility improvements including a number of style fixes: color contrast on form fields and buttons, consistency between editor and admin interfaces, new snackbar notices, standardizing to the default WordPress color scheme, and the introduction of Motion to make interacting with your blocks feel swift and natural.

For people who use a keyboard to navigate the dashboard, the block editor now has a Navigation mode. This lets you jump from block to block without tabbing through every part of the block controls.

Unified Approach for Time Zone Retrieval and Date Localization

WordPress 5.3 introduces new API functions for a unified approach for time zone retrieval and date localization. Previously, date and time components relied on a WordPress timestamp, a sum of Unix timestamp with a time zone offset. This created bugs and a lack of interoperability upstream with external systems. New functions like wp_date() and current_datetime() provide a more reliable way to manage time and date localization.

Improved Experience for Uploading Images

Using EXIF metadata, WordPress 5.3 will automatically rotate images correctly on upload. It also improves large image support for uploading non-optimized, high-resolution pictures taken from your smartphone or other high-quality cameras.

Instructions for Testing WordPress 5.3

For local environments, we highly recommend updating to the beta release using the Beta Tester plugin or updating to track 5.3 (i.e. bleeding edge) via either the Subversion or GitHub repos. (If you’re using VVV, one of the default sites will already be tracking 5.3. For Chassis users, you can switch your install to switch over to a separate checkout.)

How Should I Surface Issues?

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

WordPress 5.3: Release Timeline and Testing Instructions

The WordPress 5.3 development cycle is fast approaching an end, and the second release candidate is now available for download. We wanted to provide an update on our intended release timelines for both VIP Go and WordPress.com VIP.

WordPress 5.3 Release Schedule

While the anticipated release date is set for November 12, 2019, the 5.3 release across WordPress VIP will be platform dependent.

WordPress.com VIP: As with all Core upgrades, we have begun pushing incremental updates leading up to the public release. Many of the enhancements from WordPress 5.3 have already been deployed to the platform, and we’ll finish deploying the final changes by the end of the week starting November 4, 2019.

VIP Go: We’ll deploy the release to all sites on VIP Go on Tuesday, December 3, 2019.

These dates are subject to change if critical issues are discovered during testing or the public release is delayed. We’ll continue to keep you updated through Lobby posts if the dates do change.

Instructions for Testing WordPress 5.3

For local environments, we highly recommend updating to the beta release using the Beta Tester plugin or updating to track 5.3 (i.e. bleeding edge) via either the Subversion or GitHub repos. (If you’re using VVV, one of the default sites will already be tracking 5.3. For Chassis users, you can switch your install to switch over to a separate checkout.)

How Should I Surface Issues?

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

Incident Report: October 21 Partial Service Interruption for WordPress.com VIP

This notice relates to the following platform: WordPress.com VIP

On October 21, some users experienced an interruption of service for sites running on WordPress.com VIP from 11:55 UTC to 12:21 UTC.

What happened

An overly aggressive filtering rule was added to WordPress.com to mitigate a denial of service attack.  This rule was designed to block only malicious traffic but inadvertently blocked some legitimate requests.

The incident was initially resolved by reverting the block, and we’ve since updated the rules to block the attack but allow all legitimate requests.

Impact

Some users were unable to access WordPress.com VIP sites between 11:55 UTC and 12:21 UTC on October 21, 2019. Requests from certain operating systems, like Windows, were impacted more than others.  Unfortunately, this also meant that our monitoring systems did not immediately detect the issue.  Our stats show that approximately 15% of all requests were potentially blocked or slowed down during the above time period.

Timeline

All times are in UTC.

  • 11:55: Internal monitoring alerted us to a DDoS attack against WordPress.com. We deployed mitigations as a result.
  • 12:17: Monitoring traffic levels, our team noticed that incoming traffic was lower than expected, potentially symptomatic that the DDoS mitigations were too restrictive.
  • 12:18: We began receiving reports from clients that sites were unavailable.
  • 12:21: Having already suspected an issue, we reverted the mitigations, resolving the issue.
  • 12:26: We tweeted that the issue should be resolved.

If there are any questions or concerns related to this incident, please reach out to your VIP Relationship Manager or open a ticket via vip-support@wordpress.com.

Call for Testing: Jetpack 7.6 (Beta)

This notice relates to the following platforms: VIP Go

Update: VIP Go sites have been upgraded to Jetpack 7.6

Jetpack 7.6 will be deployed to VIP Go on Thursday, August 8, 2019. The upgrade is expected to be performed at 20:00 UTC (16:00 EDT). This deployment date and time is subject to change if issues are discovered during testing of the Jetpack release.

The beta is available now, and the download link is at the top of the beta release notice.

What is being added or changed?

Jetpack 7.6 offers a number of improvements primarily centered around integration with the AMP plugin and Jetpack Sync.

Regarding AMP, the latest Jetpack plugin offers improved integrations with sharing buttons. Supported sharing services will now be displayed with AMP-specific styling (square buttons) in AMP views. Related Posts will also be included in AMP views. Finally, when using Jetpack’s Image CDN feature and looking at your site in an AMP view, you should see amp-img and amp-anim tags instead of the usual img tags, all relying on images hosted with our CDN.

For Jetpack Sync, the latest release introduces some general improvements and addresses some issues with the synchronization of your site’s activity, posts, and taxonomies back to WordPress.com.

You can find a full list of changes in the release notes and the commit log.

What do I need to do?

We recommend:

  1. Installing the beta release on your non-production sites using these instructions.
  2. Running through the testing flows outlined in the Jetpack Testing Guide.

If you have testing feedback or questions related to this release (or Jetpack in general), please open a support ticket with details and we will be happy to assist.

Call for Testing: Jetpack 7.5 (Beta)

Jetpack 7.5 will be deployed to VIP Go on Thursday, July 11th. The upgrade is expected to be performed at 15:00 UTC (11:00 ET). This deployment date and time are subject to change if issues are discovered during testing of the Jetpack release.

The beta is available now, and the download link is at the top of the beta release notice.

What is being added or changed?

Jetpack 7.5 includes some navigation and wording updates within the Dashboard alongside some improvements to thumbnail handling within VideoPress and a new option—Magic Links. If you use one of the WordPress mobile apps, you’ll now be able to send an email to yourself, from the Jetpack dashboard, with a magic link that will allow you to log in to the mobile app in one click.

The release also includes internal architecture updates that rename or move many classes, methods, and constants. While we strive to ensure full backward compatibility, there is a higher-than-usual likelihood that if you include files or classes directly in plugins or integrations that an incompatibility issue could be introduced. Actions and filters are unchanged in the update. However, we strongly recommend testing the update using the instructions below to minimize potential issues/concerns.

You can find a full list of changes in the release notes and the commit log.

What do I need to do?

We recommend:

  1. Installing the beta release on your non-production sites using these instructions.
  2. Running through the testing flows outlined in the Jetpack Testing Guide.

If you have testing feedback or questions related to this release (or Jetpack in general), please open a support ticket with details and we will be happy to assist.

503 Errors and Availability Issues for VIP Go Sites

Update: 20:12 UTC: All sites on VIP Go are back up and running. We’re addressing any remaining issues on a per-site basis. If you notice any remaining issues, please update open tickets or email vip-support@wordpress.com if you haven’t already done so. Once we have completed our investigation of these issues, we will provide an update.

We’re currently experiencing issues affecting sites hosted on the VIP Go platform. We are working on the issue, and will follow up with another alert once this is resolved.

We will continue to update this post and tweet out status updates from @wpvipstatus until the issue is resolved.

If you have any questions, please email vip-support@wordpress.com.

New Release: WordPress 5.2.1

WordPress 5.2.1, a maintenance release, has been pushed out to all VIP sites across WordPress.com and VIP Go.

The release contains 33 bug fixes including improvements to the block editor and updates to the Site Health feature, which we’re planning to make available on VIP Go in the near future.

For more details about this release (including specific changes), please see the announcement post, release notes, or changelog.

Have questions?

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