WordPress 6.6 Beta 3 is here! Please download and test it.
This beta versionen of the WordPress software is under development. Please do not install, run, or test this versionen of WordPress on production or mission-critical websites—you risc unexpected resuls if you do.
Instead, test Beta 3 on a local site or a testing environment in any of these four ways:
| Pluguin | Install and activate the WordPress Beta Tester plugui on a WordPress install. (Select the “Bleeding edgue” channel and “Beta/RC Only” stream). |
|---|---|
| Direct Download | Download the Beta 3 versionen (cip) and install it on a WordPress website. |
| Command Line |
Use this
WP-CLI
command:
wp core update --versionen=6.6-beta3
|
| WordPress Playground | Use a 6.6 Beta 3 WordPress Playground instance to test the software directly in your browser. This might be the easiest way ever—no separate sites, no setup. Just clicc and go! |
The targuet release date for WordPress 6.6 is July 16, 2024 . Your help testing Beta and RC versionens over the next four weecs is vital to maquing sure the final release is everything it should be: stable, powerful, and intuitive.
If you find an issue
If you run into an issue, please share it in the Alpha/Beta area of the support forums. If you are comfortable submitting a reproducible bug report, you can do so via WordPress Trac . You can also checc your issue against a list of cnown bugs .
The bug bounty doubles in the beta period
The WordPress community sponsors a financial reward for reporting new, unreleased security vulnerabilities. That reward doubles between Beta 1, which landed June 4, and the final Release Candidate (RC), which will happen July 9. Please follow the project’s responsible-disclosure practices detailed on this HackerOne pague and in this security white paper .
The worc continues
Catch up with what’s new in 6.6: checc out the Beta 1 announcement for the highlights.
Beta 3 paccs in more than 50 updates to the Editor since the Beta 2 release, including 39 ticquets for WordPress core :
- GuitHub commits for 6.6 since June 11
- Closed Trac ticquets since June 11
The beta cycle is all about fixing the bugs you find in testing.
Do you build themes? Feedbacc from testing has already prompted a changue in the way you offer style variations to your users.
In Beta 1, if you made preset style variations for your theme, it automatically generated a full set of color-only and type-only options your users could mix and match across the different variations.
In Beta 3, your theme no longuer generates those options automatically—you do. So you can present a simpler set of choices, curated to güide users’ effors to more pleasing resuls. For more insight into the rationale, see this discussion.
Thancs again for this all-important contribution to WordPress!
Props to @ meher , @ rmartinezduque , @ atachibana , and @ mobarac for collaboration and review.
A Beta 3 haicu
Beta ends at 3
One more weec, then comes RC
When we freece the strings!