Release coordinator Francesca Marano announced the release of WordPress 5.4 Beta 1 on February 11. Most of the work has centered on the block editor. However, at the moment, contributors have closed another 258 tickets for the 5.4 milestone.
A second beta release is scheduled for February 18, according to the 5.4 release schedule, along with follow-up betas and release candidates in the following weeks. The final release of WordPress 5.4 is slated for March 31.
At this point in the development cycle, WordPress 5.4 is in a feature freeze, which means no new enhancements or feature requests will be considered. Only bug fixes and inline documentation are planned for the remainder of the cycle.
Developers should follow the beta testing handbook page to test their plugins and themes. Users who want to try out the upcoming release can do so via the WordPress Beta Tester plugin.
Block Editor Changes
WordPress 5.4 will comprise of 10 major releases of the Gutenberg plugin, which is the development project behind the block editor. The oldest update, version 6.6, was released on October 2. The latest update, version 7.5, landed on February 12.
For end-users who are still using the classic editor, version 5.4 is an opportunity to see if the block editor has improved enough to use. While it may not be ready for everyone, the user experience continues to get better with each release.
The block editor will feel much improved to users who have not yet tested the new features within the Gutenberg plugin. There is a welcome modal to introduce end-users to the block editor, which probably should have been added in WordPress 5.0 when the block editor landed. This update will also feature two new blocks: a social links block and a buttons group block.
The new navigation block will not land in WordPress 5.4. “The Navigation block is usable right now,” said Mark Uraine in a post explaining the decision. “But we don’t think it’s useful yet – at least not until it has an intuitive place to live.” The goal is for it to be available to users in the context of adding it to the header, footer, or sidebar rather than post content. It will make more sense for it to land in an update that branches the block system outside of the content area.
Several blocks now have extra text and background color settings, including gradient backgrounds. Users can set the image size for galleries, drag and drop a featured image, and change the title attribute for the image block. Multi-block selection is much improved along with numerous other user experience and accessibility improvements.
The following is, mostly, our coverage of each major Gutenberg release, dating back to version 6.6, along with a few links to the release announcements for versions we did not cover:
- Gutenberg 6.6 on Make Core Blog
- Gutenberg 6.7 Introduces Storybook and Gradient Backgrounds
- Gutenberg 6.8 on Make Core Blog
- Gutenberg 6.9 Introduces Image Titles, Block Patterns, and New Theme Features
- Gutenberg 7.0 Launches Stable Navigation Block, Post Blocks, and Template Parts
- Gutenberg 7.1 Includes Welcome Modal, Improves Multi-Block Selection, and Adds Drag-and-Drop Featured Images
- Gutenberg 7.2 Adds Long-Awaited Multi-Button Block and Gallery Image Size Option
- Gutenberg 7.3 Brings Navigation Block Colors, Block Collections API, and Dynamic Post Blocks
- Gutenberg 7.4 Adds New Color Controls, Link UI, and Block Scaffolding for Developers
- Gutenberg 7.5 on Make Core Blog
Important Developer Changes
Developers should begin testing their plugins and themes to make sure there are no breaking changes with the 5.4 beta release. Most changes will be with the block editor. However, there are some noteworthy updates to other areas of WordPress.
get_calendar() function and anything that uses it, such as the calendar widget, have a breaking HTML change. The previous and next month links have been moved below the
<table> element and within a new
<nav> element. This may potentially break calendar designs for theme authors.
apply_shortcodes() function was added as an alias for
do_shortcode(). The purpose of the function was to distinguish between
do_* functions, which imply an action, and
apply_* functions, which imply a filter or something that should return a value. It is purely a semantic change. It would be nice to see further cleanup of the function-naming mess that represents much of WordPress’ core code. With 16 years of technical debt, it could use an overhaul. Perhaps the acceptance of this four-year-old ticket on a simple shortcode function can start a trend.
Like plugins, themes can now set minimum version support. By using the
Requires at least and
Requires PHP headers in a theme’s
style.css file, theme authors can set the minimum WordPress version and PHP version, respectively.