{"id":17392,"date":"2024-06-18T16:37:33","date_gmt":"2024-06-18T16:37:33","guid":{"rendered":"https:\/\/wordpress.org\/news\/?p=17392"},"modified":"2024-07-17T08:22:10","modified_gmt":"2024-07-17T08:22:10","slug":"wordpress-6-6-beta-3","status":"publish","type":"post","link":"https:\/\/wordpress.org\/news\/2024\/06\/wordpress-6-6-beta-3\/","title":{"rendered":"WordPress 6.6 Beta 3"},"content":{"rendered":"\n


WordPress 6.6 Beta 3 is here! Please download and test it.<\/p>\n\n\n\n

This beta version of the WordPress software is under development. <\/strong>Please do not install, run, or test this version of WordPress on production or mission-critical websites\u2014you risk unexpected results if you do.<\/p>\n\n\n\n

Instead, test Beta 3 on a local site or a testing environment in any of these four ways:<\/p>\n\n\n\n

Plugin<\/th>Install and activate the WordPress Beta Tester<\/a> plugin on a WordPress install. (Select the \u201cBleeding edge\u201d channel and \u201cBeta\/RC Only\u201d stream).<\/td><\/tr>
Direct Download<\/th>Download the Beta 3 version (zip)<\/a> and install it on a WordPress website.<\/td><\/tr>
Command Line<\/th>Use this WP-CLI<\/a> command:
wp core update --version=6.6-beta3<\/code><\/td><\/tr>
WordPress Playground<\/th>Use a 6.6 Beta 3 WordPress Playground instance<\/a> to test the software directly in your browser. This might be the easiest way ever\u2014no separate sites, no setup. Just click and go!\u00a0<\/td><\/tr><\/tbody><\/table>
Four ways to test WordPress Beta 3.<\/figcaption><\/figure>\n\n\n\n

The target release date for WordPress 6.6 is July 16, 2024<\/strong>. Your help testing Beta and RC versions over the next four weeks is vital to making sure the final release is everything it should be: stable, powerful, and intuitive.<\/p>\n\n\n\n

If you find an issue<\/h2>\n\n\n\n

If you run into an issue, please share it in the Alpha\/Beta area<\/a> of the support forums. If you are comfortable submitting a reproducible bug report, you can do so via WordPress Trac<\/a>. You can also check your issue against a list of known bugs<\/a>.<\/p>\n\n\n\n

The bug bounty doubles in the beta period<\/h2>\n\n\n\n

The WordPress community sponsors a financial reward for reporting new, unreleased security vulnerabilities.<\/a> 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\u2019s responsible-disclosure practices detailed on this HackerOne page<\/a> and in this security white paper<\/a>.<\/p>\n\n\n\n

The work continues<\/h2>\n\n\n\n

Catch up with what’s new in 6.6:<\/strong> check out the Beta 1 announcement for the highlights.<\/a><\/p>\n\n\n\n

Beta 3 packs in more than 50 updates to the Editor since the Beta 2 release, including 39 tickets for WordPress core<\/a>:<\/p>\n\n\n\n