The first release candidate for WordPress 5.2 is now available!
This is an important milestone as we progress toward the WordPress 5.2 release date. “Release Candidate” means that the new version is ready for release, but with millions of users and thousands of plugins and themes, it’s possible something was missed. WordPress 5.2 is scheduled to be released on Tuesday, May 7, but we need your help to get there—if you haven’t tried 5.2 yet, now is the time!
Continuing with the theme from the last release, WordPress 5.2 gives you even more robust tools for identifying and fixing configuration issues and fatal errors. Whether you are a developer helping clients or you manage your site solo, these tools can help get you the right information when you need it.
The Site Health Check and PHP Error Protection tools have brand new features, giving you peace of mind if you discover any issues with plugins or themes on your site. There are also updates to the icons available in your dashboard, fresh accessibility considerations for anyone using assistive technologies and more.
Plugin and Theme Developers
Please test your plugins and themes against WordPress 5.2 and update the Tested up to version in the readme to 5.2. If you find compatibility problems, please be sure to post to the support forums so we can figure those out before the final release.
The WordPress 5.2 Field Guide has also been published, which goes into the details of the major changes.
If you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report, file one on WordPress Trac, where you can also find a list of known bugs.
Howdy, RC 1! With tools this interesting, I can hardly wait.
This software is still in development, so we don’t recommend you run it on a production site. Consider setting up a test site to play with the new version.
There are two ways to test the latest WordPress 5.2 beta: try the WordPress Beta Tester plugin (you’ll want to select the “bleeding edge nightlies” option), or you can download the beta here (zip).
WordPress 5.2 is slated for release on April 30, and we need your help to get there! Thanks to the testing and feedback from everyone who tried beta 2, nearly 40 tickets have been closed since then. Here are the major changes and bug fixes:
The new Site Health feature has continued to be refined.
Plugins no longer update if a site is running an unsupported version of PHP (see #46613).
It’s now more apparent when a site is running in Recovery Mode (see #46608).
The distraction free button no longer breaks keyboard navigation in the Classic Editor (see #46640).
Assistive technologies do a better job of announcing admin bar sub menus (see #37513).
Subject lines in WordPress emails are now more consistent (see #37940).
Personal data exports now only show as completed when a user downloads their data (see #44644).
Plus more improvements to accessibility (see #35497 and #42853).
Minimum PHP Version Update
Important reminder: as of WordPress 5.2 beta 2, the minimum PHP version that WordPress will require is 5.6.20. If you’re running an older version of PHP, we highly recommend updating it now, before WordPress 5.2 is officially released.
WordPress 5.2 has lots of refinements to polish the developer experience. To keep up, subscribe to the Make WordPress Core blog and pay special attention to the developers notes for updates on those and other changes that could affect your products.
If you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report, file one on WordPress Trac, where you can also find a list of known bugs.
Would you look at that each day brings release closer test to be ready.
This software is still in development, so we don’t recommend you run it on a production site. Consider setting up a test site to play with the new version.
There are two ways to test the WordPress 5.2 beta: try the WordPress Beta Tester plugin (you’ll want to select the “bleeding edge nightlies” option), or you can download the beta here (zip).
WordPress 5.2 is slated for release on April 30, and we need your help to get there! Thanks to the testing and feedback from everyone who tried beta 1, nearly 100 tickets have been closed since then. Here are the major changes and bug fixes:
We’ve added support for Emoji 12! 🪂
A brand-new wp_body_open() template tag (and corresponding wp_body_open action) will let themes (and plugins!) add content right after the <body> is opened (#12563).
Superfluous paragraph tags will no longer incorrectly appear in dynamic block content (#45495).
The Site Health screens have received several bug fixes, tweaks, and performance improvements.
Crash Protection no longer interrupts plugin editing (#46045).
Custom error handlers now load correctly (#46069).
Minimum PHP Version Update
As of WordPress 5.2 beta 2, the minimum PHP version that WordPress will require is 5.6.20. If you’re running an older version of PHP, we highly recommend updating it now, before WordPress 5.2 is officially released.
WordPress 5.2 has lots of refinements to polish the developer experience. To keep up, subscribe to the Make WordPress Core blog and pay special attention to the developers notes for updates on those and other changes that could affect your products.
If you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report, file one on WordPress Trac, where you can also find a list of known bugs.
The wonderful thing about betas, is betas are wonderful things. 🐯
WordPress 5.2 is targeted for release at the end of this month, and with it comes an update to the minimum required version of PHP. WordPress will now require a minimum of PHP 5.6.20.
Beginning in WordPress 5.1, users running PHP versions below 5.6 have had a notification in their dashboard that includes information to help them update PHP. Since then, the WordPress stats have shown an increase in users on more recent versions of PHP.
The dashboard widget users see if running an outdated version of PHP
Why You Should Update PHP
If your site is running on an unsupported version of PHP, the WordPress updater will not offer WordPress 5.2 to your site. If you attempt to update WordPress manually, that update will fail. To continue using the latest features of WordPress you must update to a newer version of PHP.
When updating to a new version of PHP, WordPress encourages updating to its recommended version, PHP 7.3. The PHP internals team has done a great job making its most recent version the fastest version of PHP yet. This means that updating will improve the speed of your site, both for you and your visitors.
This performance increase also means fewer servers are needed to host websites. Updating PHP isn’t just good for your site, it also means less energy is needed for the 1-in-3 sites that use WordPress, so it’s good for the planet.
How to Update PHP
If you need help updating to a new version of PHP, detailed documentation is available. This includes sample communication to send to your host for them to assist you. Many hosting companies have published information on how to update PHP that is specific for them.
5.6 now, but soon 7+
This is the first increase in PHP required version for WordPress since 2010, but may not be the only increase in 2019. The WordPress core team will monitor the adoption of the most recent versions of PHP with an eye towards making PHP 7+ the minimum version towards the end of the year.
WordPress reached a significant milestone this month. With some exciting developments in Core, an interesting new proposal, and the return of a valuable global event, March was certainly an interesting time.
This growth of WordPress is only made possible by the large team of volunteers working to build the project and community. If you would like to get involved in building the future of WordPress, then check out the Make network for a contributor team that fits your skill set.
With blocks becoming the new way to manage content in WordPress, more and more types of blocks are being developed to cater for different use cases and content types. In an effort to make it easier for content creators to find these block types, there is a proposal for a new type of plugin and a directory to handle it.
The proposal outlines a new type of WordPress plugin that provides blocks and nothing else, named Single Block Plugins. The primary benefit would be to provide content creators with individual pieces of functionality and new types of blocks without the need to search for and install new plugins.
The Single Block Plugins would be hosted in a separate Block Directory section of the Plugin Directory and they would initially be JavaScript-based. Each plugin will register a single block, and they will be searchable and installable from within the editor itself. This puts blocks at the publishers’ fingertips — you no longer have to leave the editor to find them.
On 11 May 2019, the fourth Global WordPress Translation Day will take place. This is a 24-hour global event dedicated to the translation of all things WordPress, from core to themes, plugins to marketing.
Over the course of 24 hours, WordPress communities will meet to translate WordPress into their local languages and watch talks and sessions broadcast on wptranslationday.org. During the last Global WordPress Translation Day, 71 local events took place in 29 countries, and even more communities are expected to take part this time.
With the block editor in WordPress Core, the team has been able to focus on adding some frequently requested features. Version 5.3 of Gutenberg, released this month, includes a new block manager modal, the ability to nest different elements in the cover block, and some UI tweaks to improve the hover state of blocks.
The PHP upgrade notice in WordPress 5.1 has already had a hugely positive effect on thousands of websites.
The Theme Review Team has released their useful Theme Sniffer plugin on the Plugin Directory to help theme developers build more standards-compliant themes.
The Polyglots team has started a discussion about the best way to localize WordPress user documentation.
The schedule for WordCamp Europe 2019 has been published – the event takes place on June 20-22.
A new `wp_body_open` hook has been added to Core in version 5.2, providing more power and flexibility for theme developers.
This software is still in development, so we don’t recommend you run it on a production site. Consider setting up a test site to play with the new version.
WordPress 5.2 is slated for release on April 30, and we need your help to get there. Here are some of the big items to test so we can find as many bugs as possible in the coming weeks.
Block Editor
The block editor has received significant performance improvements since WordPress 5.1, shaving 35% off the load time for massive posts, and cutting the keypress time (how responsive it feels when you’re typing) in half!
Accessibility continues to improve, too. The block editor now supports your browser’s reduced motion settings. The post URL slug has better labelling and help text. The focus styling for keyboard navigating through landmarks is clearer and more consistent. There are a variety of new speak messages, and existing messages have been tweaked for more useful screen-reader behaviour.
We’ve added several new blocks:
An RSS block
An Amazon Kindle embed block
A Search block
A Calendar block
A Tag Cloud block
To help you keep track of these blocks, and only show the ones you need, there’s a new block management tool to switch blocks on and off.
Block Management Modal
We’re constantly working on existing blocks, too. There are hundreds of bug fixes and improvements in the block editor, you can read more about them in the Gutenberg plugin releases: 4.9, 5.0, 5.1, 5.2, and 5.3.
The WordPress Mobile Apps
The block editor isn’t just for websites, either. The WordPress mobile apps now include an experimental version of a built-in block editor. This is still under development, but you can try it out now!
Site Health Check is an ongoing project aimed at improving the stability and performance of the entire WordPress ecosystem.
The first phase of this project (originally scoped for WordPress 5.1) is now included in WordPress 5.2. For the first time, WordPress will catch and pause the problem code, so you can log in to your Dashboard and see what the problem is (#44458). Before, you’d have to FTP in to your files or get in touch with your host.
In addition, we’re adding a new Health Check tool to your Dashboard. Visit the Tools menu and click on Health Check to get information that can help improve the speed and security of your site.
Plugins can now specify the minimum version of PHP that they support, so you can safely modernise your development practices without risking breaking your users’ sites. (#40934)
There’s a new release of Dashicons, the WordPress Dashboard icon font. There are 25 new icons for you to use! (#41074)
You can now pass a label to get_search_form(), improving accessibility. (#42057)
There have been 130 tickets closed in WordPress 5.2 so far, with numerous small bug fixes and improvements to help smooth your WordPress experience.
Keep your eyes on the Make WordPress Core blog for developer notes (which are assigned the dev-notes tag) in the coming weeks detailing other changes in 5.2 that you should be aware of.
If you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report, file one on WordPress Trac, where you can also find a list of known bugs.
With each new release, bearing multiple betas; We fix, then we fly.
WordPress now powers over 1/3rd of the top 10 million sites on the web according to W3Techs. Our market share has been growing steadily over the last few years, going from 29.9% just one year ago to 33.4% now. We are, of course, quite proud of these numbers!
The path here has been very exciting. In 2005, we were celebrating 50,000 downloads. Six years later, in January 2011, WordPress was powering 13.1% of websites. And now, early in 2019, we are powering 33.4% of sites. Our latest release has already been downloaded close to 14 million times, and it was only released on the 21st of February.
WordPress market share on the rise over the last 8 years. Image source: W3Techs.
Over the years WordPress has become the CMS of choice for more and more people and companies. As various businesses use WordPress, the variety of WordPress sites grows. Large enterprise businesses all the way down to small local businesses: all of them use WordPress to power their site. We love seeing that and we strive to continuously make WordPress better for all of you.
We’d like to thank everyone who works on WordPress, which is built and maintained by a huge community of volunteers that has grown alongside the CMS. This incredible community makes it possible for WordPress to keep growing while still also remaining free. And of course, we’d like to thank all of you using WordPress for using it and trusting in it. To all of you: let’s celebrate!
WordPress 5.1.1 is now available! This security and maintenance release introduces 14 fixes and enhancements, including changes designed to help hosts prepare users for the minimum PHP version bump coming in 5.2.
This release also includes a pair of security fixes that handle how comments are filtered and then stored in the database. With a maliciously crafted comment, a WordPress post was vulnerable to cross-site scripting.
WordPress versions 5.1 and earlier are affected by these bugs, which are fixed in version 5.1.1. Updated versions of WordPress 5.0 and earlier are also available for any users who have not yet updated to 5.1.
Props to Simon Scannell of RIPS Technologies who discovered this flaw independent of some work that was being done by members of the core security team. Thank you to all of the reporters for privately disclosing the vulnerabilities, which gave us time to fix them before WordPress sites could be attacked.
Other highlights of this release include:
Hosts can now offer a button for their users to update PHP.
The recommended PHP version used by the “Update PHP” notice can now be filtered.
WordPress 5.1.1 was a short-cycle maintenance release. Version 5.1.2 is expected to follow a similar two week release cadence.
You can download WordPress 5.1.1 or visit Dashboard → Updates and click Update Now. Sites that support automatic background updates have already started to update automatically.
In addition to the security researcher mentioned above, thank you to everyone who contributed to WordPress 5.1.1:
A new version of WordPress, significant security enhancements, important discussions, and much more – read on to find out what has been going on in the WordPress community for the month of February.
Release of WordPress 5.1
Near the end of the month, WordPress 5.1 was released, featuring significant stability and performance enhancements as well as the first of the Site Health mechanisms that are in active development. Most prominent is the new warning for sites running long-outdated versions of PHP.
You can check out the Field Guide for this release for a detailed look at all the new features and improvements. The next release is already in development with plans to improve the Site Health features, PHP compatibility, and a number of other things.
The block editor that is now a part of WordPress core started out as a project named Gutenberg with the lofty goal of creating a whole new site-building experience for all WordPress users. The first phase of Gutenberg resulted in the block editor that was included in WordPress 5.0, but development didn’t stop there – phase 2 of the project is well underway.
This month, one of the initial goals for this phase was reached with all of the core WordPress widgets being converted to blocks – this will go a long way to allowing full sites to be built using blocks, rather than simply post or page content.
Both the iOS and Android apps are open for beta testers, so if you would like to experience the block editor on mobile today, then join the beta program.
One of the goals for 2019 that Matt Mullenweg (@matt) announced in his State of the Word address last year was to form a team who would work to manage the ever-increasing number of tickets in Trac, the bug tracker that WordPress Core employs.
This team, known as the Triage Team, has been announced. Their work will involve coordinating with component maintainers, release leads, project leadership, contributors, and other WordPress related projects with issue trackers outside of Trac to ensure that everyone is empowered to focus on contributing.
The team was formed based on nominations of volunteers to take part and will be led by Jonathan Desrosiers (@desrosj). The other members of the team are Chris Christoff (@chriscct7), Tammie Lister (@karmatosed), Sergey Biryukov (@sergey), and Sheri Bigelow (@designsimply) – all of whom have a strong track record of contributing to WordPress, have exhibited good triaging practices, and are overall good community members.
Further Reading:
In this year alone, the WordPress meetup program has hosted 800 events across the world, all organized by local community members.
Version 5.1 of WordPress, named “Betty” in honour of acclaimed jazz vocalist Betty Carter, is available for download or update in your WordPress dashboard.
Following WordPress 5.0 — a major release which introduced the new block editor — 5.1 focuses on polish, in particular by improving the overall performance of the editor. In addition, this release paves the way for a better, faster, and more secure WordPress with some essential tools for site administrators and developers.
Site Health
With security and speed in mind, this release introduces WordPress’s first Site Health features. WordPress will start showing notices to administrators of sites that run long-outdated versions of PHP, which is the programming language that powers WordPress.
When you install new plugins, WordPress’s Site Health features will check them against the version of PHP you’re running. If the plugin requires a version that won’t work with your site, WordPress will keep you from installing that plugin.
Editor Performance
Introduced in WordPress 5.0, the new block editor continues to improve. Most significantly, WordPress 5.1 includes solid performance improvements within the editor. The editor should feel a little quicker to start, and typing should feel smoother.
Expect more performance improvements in the next couple of releases.
5.1 introduces a new database table to store metadata associated with sites and allows for the storage of arbitrary site data relevant in a multisite / network context.
The Cron API has been updated with new functions to assist with returning data and includes new filters for modifying cron storage. Other changes in behavior affect cron spawning on servers running FastCGI and PHP-FPM versions 7.0.16 and above.
New test config file constant in the test suite, new plugin action hooks
Short-circuit filters for wp_unique_post_slug(), WP_User_Query, and count_users()
A new human_readable_duration function
Improved taxonomy metabox sanitization
Limited LIKE support for meta keys when using WP_Meta_Query
A new “doing it wrong” notice when registering REST API endpoints
…and more!
The Squad
This release was led by Matt Mullenweg, along with Gary Pendergast as Senior Code Reshuffler and Poet. They received wonderful assistance from the following 561 contributors for this release, 231 of whom were making their first ever contribution! Pull up some Betty Carter on your music service of choice, and check out some of their profiles:
Finally, thanks to all the community translators who worked on WordPress 5.1. Their efforts bring WordPress 5.1 fully translated to 34 languages at release time, with more on the way.
