{"id":17289,"date":"2024-06-04T17:44:29","date_gmt":"2024-06-04T17:44:29","guid":{"rendered":"https:\/\/wordpress.org\/news\/?p=17289"},"modified":"2024-07-17T08:22:26","modified_gmt":"2024-07-17T08:22:26","slug":"wordpress-6-6-beta-1","status":"publish","type":"post","link":"https:\/\/wordpress.org\/news\/2024\/06\/wordpress-6-6-beta-1\/","title":{"rendered":"WordPress 6.6 Beta 1"},"content":{"rendered":"\n

WordPress 6.6 Beta 1 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, install Beta 1 on local sites and testing environments 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 1 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-beta1<\/code><\/td><\/tr>
WordPress Playground<\/th>Use a 6.6 Beta 1 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! <\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

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

How important is your testing? <\/h2>\n\n\n\n

Features in this Beta release may be changed or removed between now and the final release.<\/strong> Early attention from testers like you is critical to finding and reporting potential bugs, usability issues, or compatibility problems to make sure developers can address them before the final release. You don’t need any contribution experience, and this is a fantastic way to begin your WordPress contributor story!<\/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

Want to know more about testing in general, and how to get started? Follow the testing initiatives in Make Core<\/a> and join the #core-test channel<\/a> on Making WordPress Slack<\/a>.<\/p>\n\n\n\n

Like every version since 5.0 in 2018, WordPress 6.6 will integrate a host of new features from the last several releases of the Gutenberg plugin. Learn more about Gutenberg updates since WordPress 6.5 in the What\u2019s New in Gutenberg<\/a> posts for versions 17.8<\/a>, 17.9<\/a>, 18.0<\/a>, 18.1<\/a>, 18.2<\/a>, 18.3<\/a>, and 18.4<\/a>. The final version will also include Gutenberg 18.5; the Beta 2 post will link to that.<\/p>\n\n\n\n

WordPress 6.6 Beta 1 contains 97 enhancements and 101 fixes for the editor, in a total of about 206 tickets for WordPress 6.6 Core<\/a>.<\/p>\n\n\n\n

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

The WordPress community sponsors a monetary reward for reporting new, unreleased security vulnerabilities.<\/a> That reward doubles during the period between Beta 1 on June 4 and the final Release Candidate (RC) that will happen June 25. Please follow the project’s responsible-disclosure practices detailed on this HackerOne page<\/a> and in this security white paper<\/a>.<\/p>\n\n\n\n

What\u2019s coming to WordPress 6.6?<\/h2>\n\n\n\n

This year\u2019s second major release is about polish and finesse. Features that landed in the last few releases have new flexibility and smoother flows\u2014and a few new tricks. And of course there are a few brand-new features.<\/p>\n\n\n\n

Data Views updates<\/h3>\n\n\n\n

Part of the groundwork for phase 3, Data Views get new and improved experience of working with information in the Site Editor. A new layout consolidates patterns and template parts, gets you to general management views in fewer clicks, and packs in a wide range of refinements.<\/p>\n\n\n\n

Overrides in synced patterns<\/h3>\n\n\n\n

What if you could keep a synced pattern\u2018s look and feel<\/em> everywhere it appears\u2014keeping it on brand\u2014but have different content<\/em> everywhere it appears?<\/p>\n\n\n\n

For instance, maybe you\u2018re building a pattern for recipes. Ideally, you want to keep the overall design of the recipe card consistent on every post that will have a recipe. But the recipe itself\u2014the ingredients, the steps, special notes on technique\u2014will be different every time.<\/p>\n\n\n\n

And perhaps, in the future, other people might need to change the design of the recipe pattern. It would be nice to know they can do that, and that the content in existing recipes will stay right where it is.<\/p>\n\n\n\n

In version 6.6, you can make all that happen, and overrides in synced patterns are the way you do it.<\/p>\n\n\n\n

See all the blocks<\/h3>\n\n\n\n

Up to now, when you had a block selected and then opened the block Inserter, you only saw the blocks you were allowed to add to your selected block. Where were all the others?<\/p>\n\n\n\n

In 6.6, when you have a block selected, you get two lists. First, there’s the list of blocks you can insert at your selected block. Then you get a list with all the other blocks. So you can get an idea of what you can use in your selected block, and what other blocks you could use in another area. In fact, if you select a block from that second list, WordPress 6.6 will add it below your block, to use in whatever you build next.<\/p>\n\n\n\n

A new publish flow<\/h3>\n\n\n\n

Version 6.6 brings the post and site editors closer together than ever. So whether you\u2019re writing for a post in the post editor or a page in the Site Editor, your experience will be about the same.<\/p>\n\n\n\n

Style variations<\/h3>\n\n\n\n

If a block theme comes with style variations, 6.6 vastly expands your design options right out of the box, without installing or configuring a single thing. Because in 6.6, your theme pulls the color palettes and typography style sets out of its installed variations to let you mix and match for a whole world of expanded creative expression.<\/p>\n\n\n\n

Section styles <\/h3>\n\n\n\n

Do you build themes? Now you can define style options for separate sections of multiple blocks, including inner blocks.<\/p>\n\n\n\n

Then your users can apply those block style variations to entire groups of blocks, effectively creating branded sections they can curate across a site.<\/p>\n\n\n\n

A note about CSS specificity<\/h4>\n\n\n\n

To make it easier for your variations to override the global styles CSS, those styles now come wrapped in `:root`. That limits their specificity. For details, read the full discussion on GitHub.<\/a><\/p>\n\n\n\n

A native Grid layout<\/h3>\n\n\n\n

Grid is a new variation for the Group block that lets you arrange the blocks inside it as a grid. If you’ve been using a plugin for this, now you can make your grids natively.<\/p>\n\n\n\n

Better pattern management in Classic themes<\/h3>\n\n\n\n

You heard right: You can do everything with patterns in Classic themes that you can in a block theme. You can see all the patterns available to you in a single view and insert a pattern on the fly. <\/p>\n\n\n\n

Negative. Margins.<\/h3>\n\n\n\n

They’re here: negative margin values, so you can make objects overlap in your design. As a guardrail, you can only set a negative margin by typing an actual negative number, not by using the slider. That\u2019s to keep people from adding negative values they didn’t intend.<\/p>\n\n\n\n

Rollback auto-updates<\/h3>\n\n\n\n

Now you can have the convenience of setting all your plugins to auto-update and the inner peace you get from knowing that if anything goes wrong, 6.6 will do a rollback. Automatically.<\/p>\n\n\n\n

This post reflects the latest changes<\/em><\/strong> as of June 4, 2024.<\/em><\/strong> <\/p>\n\n\n\n

Again, the features in this first beta may change, based on what testers like you find.<\/strong><\/p>\n\n\n\n

Get an overview of the 6.6 release cycle<\/a>, and check the Make WordPress Core blog<\/a> for 6.6-related posts<\/a> in the next few weeks for further details.<\/p>\n\n\n\n

Just for you: a Beta 1 haiku<\/h3>\n\n\n\n

Negative margins
Embellish all the new ways
To design and build <\/p>\n\n\n\n

Thanks very much to @<\/span>meher<\/a>, @<\/span>audrasjb<\/a>, @<\/span>fabiankaegy<\/a>, @<\/span>colorful-tones<\/a>, <\/em>@<\/span>davidbaumwald<\/a>, @<\/span>dansoschin<\/a>, @<\/span>desrosj<\/a>, @<\/span>atachibana<\/a>, @<\/span>ehtis<\/a>, @<\/span>adamsilverstein<\/a>, @<\/span>joedolson<\/a>, and @<\/span>webcommsat<\/a> for reviewing and collaborating on this post!<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

WordPress 6.6 Beta 1 is here! Please download and test it. This beta version of the WordPress software is under development. Please do not install, run, or test this version of WordPress on production or mission-critical websites\u2014you risk unexpected results if you do. Instead, install Beta 1 on local sites and testing environments in any […]<\/p>\n","protected":false},"author":8210271,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"episode_type":"","audio_file":"","cover_image":"","cover_image_id":"","duration":"","filesize":"","date_recorded":"","explicit":"","block":"","filesize_raw":"","jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[5,14],"tags":[559,184,409],"class_list":["post-17289","post","type-post","status-publish","format-standard","hentry","category-development","category-releases","tag-6-6","tag-development","tag-releases","mentions-adamsilverstein","mentions-atachibana","mentions-audrasjb","mentions-colorful-tones","mentions-dansoschin","mentions-davidbaumwald","mentions-desrosj","mentions-ehtis","mentions-fabiankaegy","mentions-joedolson","mentions-meher","mentions-webcommsat"],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/pZhYe-4uR","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/posts\/17289","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/users\/8210271"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/comments?post=17289"}],"version-history":[{"count":31,"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/posts\/17289\/revisions"}],"predecessor-version":[{"id":17328,"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/posts\/17289\/revisions\/17328"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/media?parent=17289"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/categories?post=17289"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/tags?post=17289"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}