WordPress 6.0 Beta 2 is now accessible for testing!
This model of the WordPress software program is beneath growth. Please don’t set up, run, and take a look at this model of WordPress on a manufacturing or mission-critical web site. Instead, it is strongly recommended that you just take a look at Beta 2 on a take a look at server and website.
You can take a look at the WordPress 6.0 Beta 2 in 3 ways:
Option 1: Install and activate the WordPress Beta Tester plugin (choose the “Bleeding edge” channel and “Beta/RC Only” stream).
Option 2: Direct obtain the beta version here (zip).
Option 3: Use WP-CLI to check:
wp core replace --version=6.0-beta2
Do not use this feature in case your filesystem is case-insensitive.
The present goal for the ultimate launch is May 24, 2022, which is about 5 weeks away.
Additional info on the total 6.0 release cycle is available.
Check the Make WordPress Core blog for 6.0-related developer notes within the coming weeks, which can element all upcoming modifications.
What’s New In Beta 2
Since Beta 1, contributors have fastened 209 tickets in WordPress 6.0, together with 110 new features and enhancements. More bug fixes are on the best way along with your assist by means of testing. Here are just a few of the modifications you’ll discover in Beta 2:
- Block Editor: Prevent kinds from being added to the location editor (#55567)
- Patterns REST API: Add ‘inserter’ to the schema (#55567)
- Don’t load distant patterns twice in WP_REST_Block_Patterns_Controller::get_items (#55567)
- Add the flexibility to filter the entire notification e-mail in retrieve_password (#54690)
- Avoid translating empty plugin headers (#54586)
Note on Webfonts API
Last week’s announcement for WordPress 6.0 Beta 1 features a reference to “Webfonts API: Manage local fonts with PHP or theme.json,” as a characteristic that may be included within the launch. This particular performance was not included in Beta 2 however could also be accessible at RC.
How to Help
Testing for points is crucial for stabilizing a launch all through its growth. Testing can be a good way to contribute to WordPress. If you might be new to testing, try this detailed guide that may stroll you thru find out how to get began.
If you assume you have got run into a problem, please report it to the Alpha/Beta area within the help boards. If you might be snug writing a reproducible bug report, you possibly can file one on WordPress Trac. This can be the place yow will discover an inventory of known bugs.
Thank you to the next contributors for collaborating on this publish: @dansoschin, @annezazu, @costdev, @priethor
And now a WordPress Haiku:
We code fervently
A breathless pause for the take a look at
‘Collaborative community’ to the rescue
Key tapping resumes