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. Instead, it is recommended you evaluate Beta 3 on a test server and site.

You can test WordPress 6.7 Beta 3 in four ways:

The current target date for the final release of WordPress 6.7 is November 12, 2024. Get an overview of the 6.7 release cycle, and check the Make WordPress Core blog for 6.7-related posts in the coming weeks for more information.

Catch up on what’s new in WordPress 6.7: Read the Beta 1 and Beta 2 announcements for details and highlights.

How to test this release

Your help testing the WordPress 6.7 Beta 3 version is key to ensuring everything in the release is the best it can be. While testing the upgrade process is essential, trying out new features is equally important. This detailed guide will walk you through testing features in WordPress 6.7.

If you encounter an issue, please report it to the Alpha/Beta area of the support forums or directly to WordPress Trac if you are comfortable writing a reproducible bug report. You can also check your issue against a list of known bugs.

Curious about testing releases in general? Follow along with the testing initiatives in Make Core and join the #core-test channel on Making WordPress Slack.

Vulnerability bounty doubles during Beta/RC

Between Beta 1, released on October 1, 2024, and the final Release Candidate (RC) scheduled for November 5, 2024, the monetary reward for reporting new, unreleased security vulnerabilities is doubled. Please follow responsible disclosure practices as detailed in the project’s security practices and policies outlined on the HackerOne page and in the security white paper.

Beta 3 updates and highlights

WordPress 6.7 Beta 3 contains more than 26 Editor updates and fixes since the Beta 2 release, including 18 tickets for WordPress core.

Each beta cycle focuses on bug fixes; more are on the way with your help through testing. You can browse the technical details for all issues addressed since Beta 3 using these links:

• GitHub commits for 6.7 since October 9, 2024
• Closed Trac tickets since October 9, 2024

A Beta 3 haiku

Code in motion hums,
New features bloom, bugs retreat,
6.7 calls.

Props to @joedolson and @jeffpaul for proofreading and review, and haiku from @colorful-tones.

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. Instead, it is recommended you evaluate Beta 2 on a test server and site.

You can test WordPress 6.7 Beta 2 in four ways:

The current target date for the final release of WordPress 6.7 is November 12, 2024. Get an overview of the 6.7 release cycle, and check the Make WordPress Core blog for 6.7-related posts in the coming weeks for more information.

Catch up on what’s new in WordPress 6.7: Read the Beta 1 announcement for details and highlights.

How to test this release

Your help testing the WordPress 6.7 Beta 2 version is key to ensuring everything in the release is the best it can be. While testing the upgrade process is essential, trying out new features is equally important. This detailed guide will walk you through testing features in WordPress 6.7.

If you encounter an issue, please report it to the Alpha/Beta area of the support forums or directly to WordPress Trac if you are comfortable writing a reproducible bug report. You can also check your issue against a list of known bugs.

Curious about testing releases in general? Follow along with the testing initiatives in Make Core and join the #core-test channel on Making WordPress Slack.

Vulnerability bounty doubles during Beta/RC

Between Beta 1, released on October 1, 2024, and the final Release Candidate (RC) scheduled for November 5, 2024, the monetary reward for reporting new, unreleased security vulnerabilities is doubled. Please follow responsible disclosure practices as detailed in the project’s security practices and policies outlined on the HackerOne page and in the security white paper.

Beta 2 updates and highlights

WordPress 6.7 Beta 2 contains more than 18 Editor updates and fixes since the Beta 1 release, including 28 tickets for WordPress core.

Each beta cycle focuses on bug fixes; more are on the way with your help through testing. You can browse the technical details for all issues addressed since Beta 1 using these links:

• GitHub commits for 6.7 since October 2, 2024
• Closed Trac tickets since October 2, 2024

A Beta 2 haiku

Beta 2 arrives,
October’s code settles in,
Change rustles like leaves.

Props to @jeffpaul for proofreading and review.

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. Instead, set up a test environment or a local site to explore the new features.

How to Test WordPress 6.7 Beta 1

You can test Beta 1 in any of the following ways: 

The scheduled final release date for WordPress 6.7 is November 12, 2024. Your help testing Beta and RC versions over the next six weeks is vital to ensuring the final release is everything it should be: stable, powerful, and intuitive.

How important is your testing?

Testing for issues is a critical part of developing any software, and it’s a meaningful way for anyone to contribute—whether or not you have experience.

If you encounter 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 check your issue against a list of known bugs.

Curious about testing releases in general and how to get started? Follow along with the testing initiatives in Make Core and join the #core-test channel on Making WordPress Slack.

WordPress 6.7 will include many new features that were previously only available in the Gutenberg plugin. Learn more about Gutenberg updates since WordPress 6.7 in the What’s New in Gutenberg posts for versions 18.5, 18.6, 18.7, 18.8, 18.9, 19.0, 19.1, 19.2, and 19.3.

What’s New in WordPress 6.7 Beta 1

WordPress 6.7 Beta 1 contains over 500 enhancements and over 500 bug fixes for the editor, including more than 200 tickets for WordPress 6.7 Core. Here’s a glimpse of what’s coming:

Meet the Twenty Twenty-Five theme

Launching with WordPress 6.7, the new default theme, Twenty Twenty-Five, embodies ultimate flexibility and adaptability, showcasing how WordPress empowers you to tell your story with a rich selection of patterns and styles. Inspired by glimpses of natural beauty and ancestry heritage, it evokes ideas of impermanence, the passage of time, and continuous evolution–mirroring life’s journey. Experience effortless site creation with Twenty Twenty-Five and follow its progress or report issues on this GitHub repo.

Zoom Out to Compose with Patterns

The Zoom Out view simplifies your editing experience by allowing you to create and edit at the pattern level rather than focusing on individual blocks. Easily toggle this view from the toolbar to streamline your site-building process, making it faster and more intuitive to design pages using patterns.

Media improvements 

Now supporting HEIC image uploads–automatically converted to JPEG for maximum compatibility–you can add high-quality images without worrying about browser support. Plus, enjoy auto-sizing for lazy-loaded images and expanded background image options at both individual and global levels, giving you greater control over your site’s visuals and performance. 

Expanding Block Supports

Several blocks now come with expanded support options, enabling even more design possibilities. Notably, the long-requested shadow support for Group blocks has been added, a big win for designers and theme developers!

Preview Options API 

The latest WordPress release enhances the Preview Options in the block editor, empowering developers to customize content previews. A new API allows plugins and themes to add custom items to the preview dropdown menu, enabling users to see content in different formats or environments. This flexibility enriches the editing experience while maintaining the existing familiar Preview dropdown structure.

Refined Data Views

The Data Views introduced in 6.5 continue to be improved. This release is focused on refining the experience with a few new features aimed at making these views more flexible for customization and more functional to use. 

Manage Block Bindings Directly

Updates to this API in 6.7 polish and open most of the underlying APIs, improving the overall user experience, and add a user interface (UI) that allows you to connect attributes with custom fields to their binding sources. This new UI makes it possible to create bindings directly in a block instead of needing to use the Code Editor. By default admin and editor users can create and modify bindings, but this can be overridden with `block_editor_settings_all or map_meta_cap` filters.

Simplified and Smarter Query Loop Block

The Query Loop block is improved, as it now automatically inherits the query from the template by default, eliminating the need for manual configuration. This means your posts display immediately in both the editor and on the front end, streamlining the process so users can focus on content without extra configuration needed.

Edit and Control Font Size Presets

An enhanced Styles interface allows for greater flexibility when creating, editing, removing, and applying font size presets. You can now easily modify the presets provided by a theme or create your own custom options. A key feature is the ability to toggle fluid typography, which enables responsive font scaling with additional options for finer control over responsiveness.

View Meta Boxes in the iframed Post Editor

A new split view option has been introduced that allows you to access both the editor canvas and metaboxes while editing. This change will provide a consistent WYSIWYG experience between the editor and front end views.

Template Registration API

With this release, developers can now more easily register custom block templates without complex filters. Streamline your development process and create custom templates with ease. 

The features included in this first beta may change before the final release of WordPress 6.7, based on what testers like you find.

Get an overview of the 6.7 release cycle and check the Make WordPress Core blog for 6.7-related posts in the next few weeks for further details.

Vulnerability bounty doubles during Beta & Release Candidate

The WordPress community sponsors a monetary reward for reporting new, unreleased security vulnerabilities. This reward doubles during the period between Beta 1 on October 1, 2024 and the final Release Candidate (RC) scheduled for November 5, 2024. Please follow responsible disclosure practices as detailed in the project’s security practices and policies outlined on the HackerOne page and in the security white paper.

Just for you: a Beta 1 haiku

Lines of code arise, 
Testing shapes the future path,  
WordPress grows once more.

Props to @annezazu, @cbringmann, @colorful-tones, @courane01, @desrosj, @marybaum, and @priethor or reviewing and collaborating on this post!

This minor release includes 15 bug fixes in Core and 11 in the Block Editor, addressing issues like unexpected CSS specificity changes in certain themes. For a full summary of the maintenance updates, you can refer to the Release Candidate announcement.

WordPress 6.6.2 is a short-cycle release. The next major release will be version 6.7 planned for November 12, 2024.

If you have sites that support automatic background updates, the update process will begin automatically.

You can download WordPress 6.6.2 from www.remarpro.com, or visit your WordPress Dashboard, click “Updates”, and then click “Update Now”.

For more information on this release, please visit the HelpHub site.

Thank you to these WordPress contributors

This release was led by Tonya Mork and Vicente Canales, with Aaron Jorbin mentoring us.

WordPress 6.6.2 would not have been possible without the contributions of the following people. Their asynchronous coordination to deliver maintenance fixes into a stable release is a testament to the power and capability of the WordPress community.

Aaron Jorbin, Aaron Robertshaw, Adam Silverstein, Aki Hamano, Akira Tachibana, Akshat Kakkad, Alexandru Horeanu, Amit Raj, andreiglingeanu, Andrew Serong, Ankur Vishwakarma, Anthony Hortin, apmeyer, Ari Stathopoulos, Benjamin Denis, bernhard-reiter, Brian Alexander, Bruno Freiberger Garcia, Carolina Nymark, Colin Stewart, Daniel Richards, David Ballarin Prunera, David Baumwald, David Herrera, Dean Sas, DEBARGHYA BANERJEE, Dennis Snell, George Mamadashvili, Greg Zió?kowski, James Rosado, Jason LeMahieu (MadtownLems), Jb Audras, Jeremy Herve, Joe Dolson, Jon Surrell, Jos Klever, karan4official, Kelly Choyce-Dwan, Kowsar Hossain, kracked888, luisherranz, Marius L. J., mariushosting, Mark Howells-Mead, mattraines, michaelwp85, Mukesh Panchal, munyagu, Narendra Sishodiya, Nick Diego, Nithin John, Nithin SreeRaj, Omar Alshaker, Paal Joachim Romdahl, Pamela Ribeiro, Pascal Birchler, Paul Biron, Peter Wilson, presstoke, ramonopoly, Riad Benguella, Scott Reilly, Sergey Biryukov, Shail Mehta, smerriman, Stephen Bernhardt, Tonya Mork, Vicente Canales, wongjn, ytfeLdrawkcaB

How to contribute

To get involved in WordPress core development, head over to Trac, pick a ticket, and join the conversation in the #core and #6-7-release-leads channels. Need help? Check out the Core Contributor Handbook.

As a reminder, please see this post for the upcoming security changes for plugin and theme authors on www.remarpro.com.

Props to @jorbin, @cbringmann, @audrasjb, and @sergeybiryukov for proofreading.

This minor release features 7 bug fixes in Core and 9 bug fixes for the Block Editor. You can review a summary of the maintenance updates in this release by reading the Release Candidate announcement.

WordPress 6.6.1 is a short-cycle release. The next major release will be version 6.7 planned for November 2024.

If you have sites that support automatic background updates, the update process will begin automatically.

You can download WordPress 6.6.1 from www.remarpro.com, or visit your WordPress Dashboard, click “Updates”, and then click “Update Now”.

For more information on this release, please visit the HelpHub site.

Thank you to these WordPress contributors

This release was led by Tonya Mork and Ella.

WordPress 6.6.1 would not have been possible without the contributions of the following people. Their asynchronous coordination to deliver maintenance fixes into a stable release is a testament to the power and capability of the WordPress community.

Aaron Jorbin, Aaron Robertshaw, Aki Hamano, Amit Raj, Akira Tachibana, Andrea Fercia, Andrew Serong, annezazu, Art Smith, Brian Gardner, Carolina Nymark, cbirdsong, Ciprian, Clark, Courtney Robertson, Daniel Richards, David Baumwald, Dennis Snell, Dion Hulse, Ella, Eric-Oliver M?chler, Fabian K?gy, George Mamadashvili, Jarda Snajdr, Jb Audras, Joe Dolson, Joen A., Jon Surrell, laurelfulford, Marco Ciampini, Mario Santos, Mark Howells-Mead, Mukesh Panchal, neotrope, Pascal Birchler, Paul Biron, ramonopoly, Raquel, Riad Benguella, Rich Tabor, Robert Anderson, Sergey Biryukov, Scott Reilly, Sourav Pahwa, Stephen Bernhardt, SunilPrajapati, Tonya Mork, up1512001

How to contribute

To get involved in WordPress core development, head over to Trac, pick a ticket, and join the conversation in the #core and #6-7-release-leads channels. Need help? Check out the Core Contributor Handbook.

Say hello to WordPress 6.6 “Dorsey,” named after the legendary American Big Band leader, Tommy Dorsey. Renowned for his smooth-toned trombone and compositions, Dorsey’s music captivated audiences with its emotional depth and vibrant energy.

Let your heart swing, sing, and sway to the deep brass notes of Dorsey’s Big Band sound as you explore the new features and enhancements of WordPress 6.6.

Hello, 6.6!

WordPress 6.6 delivers on the promise of a better web by bringing style, finesse, and a suite of creative possibilities to your site-building experience. This version helps you do more with ease, putting enhanced tools at your fingertips and giving you unprecedented power behind the scenes. You will find more ways to create beautiful, coherent design elements across your site, a new layout for quick page previews in the Site Editor, and the safety of automatic rollbacks for failed plugin auto-updates—among many other highlights.

In addition to the new features, “Dorsey” continues to deliver the performance and accessibility gains you can expect from every WordPress release. Explore what WordPress 6.6 has to offer and get ready to let its features take your sites to new heights.

What’s inside

Add more design options to block themes

Create color or font sets to multiply design combinations across one theme. These sets offer more contained design possibilities, allowing visual variety within the site’s broader styling guidelines.

Simplify your workflow with a new layout for pages in the Site Editor

See all of your pages and a preview of any selected page with the new side-by-side layout in the Site Editor.

Auto-update your plugins with peace of mind

Enjoy the convenience of plugin auto-updates with the safety of rollbacks if anything goes wrong—offering your site a new level of security, enhanced functionality as it becomes available, and almost no time or bandwidth from you to make it happen.

Customize content in synced patterns

Make content changes in each instance of a synced pattern while maintaining a consistent style across them. Set these overrides for Heading, Paragraph, Button, and Image blocks when placed in a synced pattern.

Performance

WordPress 6.6 features important updates like removing redundant WP_Theme_JSON calls, disabling autoload for large options, and eliminating unnecessary polyfill dependencies. Other highlights include lazy-loading post embeds, a new data-wp-on-async directive, and templates in the editor that load approximately 35% faster overall.

Accessibility

This release includes 58 accessibility fixes and enhancements. These focus on foundational aspects of the WordPress experience, particularly the data views component powering the new site editing experience and areas like the Inserter, which provide a key way of interacting with blocks and patterns.

And much more

Visit the feature showcase for a full overview of all the new features and enhancements in WordPress 6.6.

Learn more about WordPress 6.6

Explore Learn WordPress for quick how-to videos, online workshops, and other free resources to level up your WordPress knowledge and skills.

The WordPress 6.6 Field Guide contains detailed technical information and developer notes to help you build with WordPress and get the most out of this release. Don’t forget to subscribe to the Developer Blog for updates, tutorials, and other helpful WordPress content for developers.

For information about installation, file changes, fixes, and other updates, read the 6.6 release notes.

The 6.6 release squad

Every release comes to you from a dedicated team of enthusiastic contributors who help keep things on track and moving smoothly. The team that has led 6.6 is a cross-functional group of contributors who are always ready to champion ideas, remove blockers, and resolve issues.

• Release Lead: Matt Mullenweg
• Release Coordinator: Meher Bala
• Core Tech Lead: Jb Audras
• Editor Tech Leads: Ella van Durpe, Vicente Canales
• Core Triage Leads: Olga Gleckler, Nazmul Hasan Robin
• Editor Triage Leads: Fabian K?gy, Damon Cook 
• Documentation Leads: JuanMa Garrido, Jenny Dupuy, Josep Morán
• Marketing & Communications Lead: Mary Baum
• Test Lead: Anne McCarthy
• Design Lead: Rich Tabor
• Performance Lead: Adam Silverstein

Thank you, contributors

The mission of WordPress is to democratize publishing and embody the freedoms that come with open source. A global and diverse community of people collaborating to strengthen the software supports this effort.

WordPress 6.6 reflects the tireless efforts and passion of more than 630 contributors in at least 51 countries. This release also welcomed over 150 first-time contributors!

Their collaboration delivered more than 1,900 enhancements and fixes, ensuring a stable release for all—a testament to the power and capability of the WordPress open source community.

!Benni · 1naveengiri · Aaron Jorbin · Aaron Robertshaw · aatanasov · abditsori · Abdulrahman Alani · Abha Thakor · abhi3315 · Abhijit Rakas · abitofmind · Adam Harley (Kawauso) · Adam Silverstein · Adam Zieliński · adamhorne · Adel Tahri · adrianduffell · aduth · Aezaz Shekh · Ahmed Kabir Chaion · ajfleming · Ajit Bohra · Ajith R N · Akash Dhawade · Aki Hamano · Akira Tachibana · akmelias · Akshat Kakkad · Alan Fuller · Albert Juhé Lluveras · alesflex · Alex Cicovic · Alex Concha · Alex Kozack · Alex Lende · Alex Stine · Alexandre Buffet · Alexandru Horeanu · alexminza · allilevine · Alvaro Gómez · amanias1977 · Amber Hinds · Amir Abbas · amisiewicz · Amit Raj · Anamarija Papi? · Anders Norén · Andre Ribeiro · Andrea Fercia · Andrea Roenning · Andrei Draganescu · Andrei Lupu · andreiglingeanu · Andrew Hayward · Andrew Hutchings · Andrew Nacin · Andrew Ozz · Andrew Serong · André Maneiro · Andy Fragen · Aneesh Devasthale · Angela Jin · Angela R.L · Anil Vaza · Ankit K Gupta · Ankit Panchal · Ankur Vishwakarma · Anne McCarthy · Anthony Burchell · Anthony Hortin · Antoine · Anton Vlasenko · apmeyer · Ari Stathopoulos · Armando J. Perez Carreno · Art Smith · Artemio Morales · Arthur Chu · Artur Piszek · Arun Sharma · Arunas Liuiza · Ashesh Magar · Asiqur Rahman · Asish Chandra Mohon · Aslam Doctor · asmittle · Aurooba Ahmed · Ayesh Karunaratne · Béryl de La Grandière · Balu B · bangank36 · Bart Kalisz · Beatriz Fialho · Beau Lebens · Ben Dwyer · Ben Keith · Ben Ritner - Kadence WP · Benjamin Denis · Benjamin Gosset · Benjamin Pick · Benjamin Zekavica · benjpw · bernhard-reiter · Birgit Pauli-Haack · bissy · Bjarne Oldrup · Blackbam · Blockify · blogography · bnewboldbsky · bnjunge · Brad Jorsch · Brennan Goewert · Brian Alexander · Brian Coords · Brian Gardner · Brian Gosnell · Brian Haas · Bridget Willard · bridgetwes · Brooke · Bruno Freiberger Garcia · Bruno Tritsch · burnuser · Caleb Burks · Candy · Carlos Bravo · Carlos G. P. · Carolina Nymark · cbirdsong · Chad Chadbourne · Charlie Merland · Chloe Bringmann · Chouby · Chris Reynolds · chrisdotdotdot · Christoph Daum · Christopher · Ciprian · Clark · Colin Stewart · ColinD · colle · Colleen (Ohia) Thompson · comecaramelos · Constantine Vasilyev · CookiesForDevo · Corey McKrill a11n · Courtney Robertson · Craig Francis · crazytonyli · Cullen Whitmore · Curdin Krummenacher · cyrus11 · Dale du Preez · Damon Cook · Damon Cook · Dan Soschin · Dan Sullivan · Dani Guardiola · Daniel Richards · darerodz · Darren Ethier (nerrad) · Darshit Rajyaguru · dav4 · Dave Page · David · David A. Kennedy · David Ballarin Prunera · David Baumwald · David Biňovec · David Bowman · David Calhoun · David Herrera · David Jensen · David Levine · David Rozando · David Smith · davideferre · De'Yonté W. · Dean Sas · DEBARGHYA BANERJEE · Deep Patel · Deepak Vijayan · Denis ?oljom · Dennis Snell · Derek Blank · Derek Smart · designsimply · Devin Curtis · Dharmesh Patel · Dhrumil Kumbhani · Dhruval Shah · Dhruvang21 · dhruvkb · DiedeExterkate · diegosomar · Dilip Bheda · Dion Hulse · DJ · DjZoNe · dmpinder · Dominik Schilling · Drew Jaynes · drrxbracho · Earle Davies · Elena Brescacin · Ella van?Durpe · Emily Clarke · Emmanuel Hesry · Enej Bajgori? · Eneko Garrido · enodekciw · Enrico Battocchi · Enrico Sorcinelli · Eric-Oliver Mächler · Erik · erikiva · Estela Rueda · evanltd · Fabian K?gy · Fabian Todt · Faisal Alvi · Fanly · Farhan Ahmed · Felix Arntz · Firoz Sabaliya · Flavia Bernárdez Rodríguez · Florian TIAR · Franz Josef Kaiser · fushar · Gabor Lippert · Gajendra Singh · Gal Baras · Gale Wallace · Garth Mortensen · Gary Jones · George Mamadashvili · George Stephanis · Gerardo Pacheco · gierand · Glen Davies · Glenn Ansley · Grant M. Kinney · Greg Zió?kowski · Guido Scialfa · Héctor Prieto · hakre · hanneslsm · Hans-Gerd Gerhards · Harit Panchal · Harsh Gajipara · Haz · heinvv · HelgaTheViking · Hinnerk Altenburg · Hit Bhalodia · Hitendra Chopda · humanify · huubl · Huzaifa Al Mesbah · iamthomasbishop · Ian Belanger · ignatiusjeroe · Imran · inwerpsel · Ipstenu (Mika Epstein) · Isabel Brison · IT Path Solutions · Ivan Ottinger · Jaap Weijland · Jack Stevens · jaclync · Jacob Smith · James Koster · James Rosado · James Wesley Goedert · Jamie Speller · Jan Boddez · Jansen Tolle · janthiel · Jarda Snajdr · Jarek Mazurczak · jarekmorawski · Jaroslav "Dero" Polakovic · Jason Adams · Jason Crist · Jason Johnston · Jason LeMahieu (MadtownLems) · Javier Casares · jayanthparthsarathy · jbinda · jdekhtiar · Jean-Baptiste Audras · Jeff Chi · Jeff Ong · Jeffrey Paul · Jeffro · jeflopo · Jenny Dupuy · Jeremy Felt · Jeremy Herve · Jeremy Pry · Jerry Jones · Jesús Amieiro · Jess · Jessica Lyschik · jhned · Jigar Bhanushali · Jigar Panchal · Jip Moors · JiveDig · Joe Dolson · Joe McGill · Joen Asmussen · Johannes Jülg · John Blackbourn · John Espiritu · John Godley · John Hooks · John James Jacoby · Jon Surrell · jon092 · Jonathan · Jonathan Bossenger · Jonathan Desrosiers · Joni Erkkilä · Jonny Harris · jordesign · Jorge Costa · Jos Klever · Jose Varghese · Josep Morán · Joseph Scott · Joshua Goode · Jossnaz · Juan Aldasoro · JuanMa Garrido · jules · Julie Moynat · Juliette Reinders Folmer · Julio Potier · Justin Tadlock · justnorris · Jyolsna J E · K. Adam White · KafleG · Kai Hao · Kajal Gohel · Kamran Hussen · Kapil Paul · Karan Gupta · Karlijn Bok · Karol Manijak · Karthik Thayyil · Kathryn Presner · keithdevon · Kellen Mace · Kelly Choyce-Dwan · keoshi · Kevin Hoffman · Khokan Sardar · killua99 · Kira Schroder · kitchin · Kite · Kjell Reigstad · kkmuffme · kmvan · Knut Sparhell · Konstantin Kovshenin · koodii · Kowsar Hossain · kracked888 · kristastevens · kristenfisher427 · Krupa Nanda · Krupal Panchal · Kushang Tailor · kyleak · Lae · Lanre Smith · Lars Gersmann · Laura Byrne · laurelfulford · Lauren · Lauren Stein · Laurent MILLET · Laurent Naudier · leemon · Lena Morita · Leonidas Milosis · Liam Gladdy · Linkon Miyan · liviopv · Louis Wolmarans · Lovekesh Kumar · Luan Ramos · luboslives · Lucas · Luigi Teschio · Luis · Luis Martins · Luis Molina (interdevel) · luisherranz · Lyon Müller · Márcio Duarte · Maddie - a11n · madfcat · Madhu Dollu · Maggie Cabrera · Mai · Makdia Hussain · manfcarlo · Manoj Maharrshi · Marc · Marc Armengou · Marcelo de Moraes Serpa · Marcin Pietrzak · Marco Ciampini · Marco Pereirinha · marherumr · Marie Comet · Marin Atanasov · Mario Santos · Marius L. J. · mariushosting · Mark Howells-Mead · Mark Jaquith · Mark Szymanski · Mark Uraine · Martijn van der Klis · Mary Baum · Mat Lipe · Mathieu Viet · Matias Benedetto · Matias Ventura · Matt Cromwell · Matt Medeiros · Matt Mullenweg · Matt Sherman · Matteo Enna · mattraines · maurodf · Md Abul Bashar · Md Sahadat Husain · Md Tofajjal Hossen · MD.NESAR MRIDHA · Meet Makadia · Meet Mehta · megane9988 · Meher Bala · Michael James Ilett · michaelwp85 · Michal Czaplinski · Miguel Fonseca · miguelsansegundo · Mihai Joldis · Miikka · Mikael Korpela · Mike Henderson · Mike McAlister · Mikey Binns · Minal Diwan · Miriam Schwab · Mitchell Austin · miya · mkismy · Mobarak Ali · Mohit Dadhich · Monzur Alam · Morais Junior · mrwweb · Muhibul Haque · mujuonly · Mukesh Panchal · Mumtahina Faguni · munyagu · Musannif Zahir · Mustaque Ahmed · myhro · mykolashlyakhtun · Mykyta Synelnikov · Nadir Seghir a11n · Naeem Haque · Namith Jawahar · Narendra Sishodiya · Naresh Bheda · Nate Gay · Nazmul Hasan Robin · Nazmul Hosen · nboot8 · nendeb · neotrope · Nick Diego · nicmare · Nico · Nicolas Tatarchenko · Nicole Furlan · Nicole Paschen Caylor · nicomollet · nidhidhandhukiya · Niels Lange · Nihar Ranjan Das · Nik Tsekouras · Nilambar Sharma · Nilo Velez · Nirav Sherasiya · Nithin John · Nithin SreeRaj · nkeller15 · Noruzzaman · nosilver4u · obliviousharmony · okat · Old account · Olga Gleckler · Oliver Campion · Oliver Schmid · OllieJones · Omar Alshaker · omerkurd · Paal Joachim Romdahl · Pablo Honey · Pacicio · Pamela Ribeiro · Paolo L. Scala · papijo · Pascal Birchler · Patricia BT · Patrick Lumumba · Paul Bearne · Paul Biron · Paul de Wouters · Paul Kevan · Paul Wilde · Paulo Trentin · Pavan Patil · pavelevap · Pedro Mendonça · peiche · Per Søderlind · perryrylance · Peter Rubin · Peter Wilson · petitphp · petralian · Phi Phan · Pieterjan Deneys · Pinar · Pitam Dey · pkuliga · Pooja N Muchandikar · pooja9712 · Povilas Staškus · ppolo99 · Praful Patel · Pranit Dugad · Prasad Karmalkar · Prashant Baldha · Pratik Londhe · Prem Tiwari · Presskopp · printsachen1 · Priyanshii Vijayvargiya · Prottoy Sarkar Argho · QuietNoise · Rachel Baker · Rafael Gallani · Rafa? Ca?ka · Rajan Lama · Rajin Sharwar · Ramon Ahnert · Ramon Corrales · Ramon James · Raquel · Ravikumar Patel · Ravinder Kumar · Rejaul Alom Khan · Remkus de Vries · Remy Perona · renishsurani · retrofox · Riad Benguella · Rich Collier · Rich Tabor · Richard Korthuis · richardevs · Rishi Mehta · Robert Anderson · Robert Ghetau · Robin Cornett · rodionov201 · Rodrigo Arias · Rodrigo Primo · Roger · Rolf Siebers · Roy Tanck · Ryan McCue · Ryan Urban · Ryan Welcher · Sébastien SERRE · Sérgio Gomes · Sören Wünsch · s0what · Sagar Prajapati · sahilthakur02 · Sakib Mohammed · Sal Ferrarello · Sam Berry · Sam Brockway · samiamnot · Sampat Viral · Samuel Rüegger · Samuel Sidler · Sanne van der Meulen · Sarah Norris · Sarkar Ripon · Sascha Metz · Saulius Vikerta · Saxon Fletcher · Saxon Fletcher · Scott Reilly · scribu · script2see · Sean Fisher · Sergey Biryukov · Seth Miller · Seth Rubenstein · Shail Mehta · Shalin Shah · Shannon Smith · shaunandrews · sheulyshila · Shital Marakana · Shiva Poudel · Shiva Shanker Bhatta · Showrav Hasan · Shreyash Srivastava · Shubham Kumar Bansal · Shuvo Mohajan · Siddharth Thevaril · siliconforks · Simone Maranzana · Siobhan · sirzooro · SJNBham · smerriman · Sneha Patil · Sourav Pahwa · Spencer Finnell · Stefano Minoia · Stephen Bernhardt · Stephen Brook · Stephen Edgar · stephenmiracle · Steve Ariss · Steve Jones · steveblum · strangehill · strarsis · studio28 · studiozerozero · Sudip Dadhaniya · Sumit Bagthariya · Sumit Singh · SunilPrajapati · Suwash · swapnild · syamraj24 · Sybre Waaijer · Syed Balkhi · Tahmid ul Karim · Takashi Irie · Takashi Kitajima · Tammie Lister · Tapan Kumer Das · Taras Dashkevych · Tasnia Rahman Raima · Taylor Gorman · Terence Eden · Teresa Gobble · Thakor Darshil · thelmachido a11n · Thijs · Thirumani Guhan · Thomas Kräftner · threadi · Till Krüss · Tim Brathärig · Tim Nicholson · Tim Nolte · Timo Tijhof · Timothy Jacobs · tmatsuur · tmfhokies · TobiasBg · tobifjellner (Tor-Bjorn “Tobi” Fjellner) · Tom Cafferkey · Tomek · tomepajk · Tomoki Shimomura · tomxygen · Toni Viemerö · Tony G · Tonya Mork · Toro_Unit (Hiroshi Urabe) · Torsten Landsiedel · Tremi Dkhar · Trupti Kanzariya · tunetheweb · twstokes · tybor · u451f · Ugyen Dorji · Umesh Gupta · up1512001 · Vagelis · Valérie Galassi · Vicente Canales · Viktor Szépe · Vinit · Vinita Tandulkar · Vipul Gupta · Vishal Kothari · vivekawsm · vrrobz · WebMan Design | Oliver Juhas · websitegenii · wesatintellitonic · Weston Ruter · whaze · Will Earnhardt · Will Skora · WilliamG · Wojtek Naruniec · wongjn · wpsoul · Yagnik Sangani · yankiara · Yann · Yannis Guyon · ytfeLdrawkcaB · Yui · Yukinobu Asakawa · Yuvrajsinh Sisodiya · Zack Krida · zackkatz · Zafar Kamal · zeelthakkar · Zenaul Islam · zkarj · Zunaid Amin

More than 60 locales have translated 90 percent or more of WordPress 6.6 into their language. Community translators are working hard to ensure more translations are on their way. Thank you to everyone who helps make WordPress available in 200 languages.

Last but not least, thanks to the volunteers who contribute to the support forums by answering questions from WordPress users worldwide.

Get involved

Participation in WordPress goes far beyond coding, and learning more and getting involved is easy. Discover the teams that come together to Make WordPress and use this interactive tool to help you decide which is right for you.

6.6 haiku

Six-point-six is here.
Make it all gorgeous; keep it
On brand, and relax.

This 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. Instead, please evaluate RC3 on a test server or a local environment.

Reaching this phase of the release cycle is a worthy achievement. While release candidates are considered ready for release, your testing is still vital to make sure everything in WordPress 6.6 is the best it can be.

You can test WordPress 6.6 RC3 in four ways:

The target for the WordPress 6.6 release is next Tuesday, July 16, 2024. Get an overview of the 6.6 release cycle, and check the Make WordPress Core blog for 6.6-related posts in the next few weeks for further details.

What’s in WordPress 6.6 RC3?

Thanks to your testing (and many other contributors‘ up to now) this release includes eight bug fixes for the Editor and 18 tickets for WordPress Core.

Get a recap of WordPress 6.6’s highlighted features in the Beta 1 announcement. For more technical information related to issues addressed since RC 2, you can browse the following links:

• GitHub commits for 6.6 since July 2
• Closed Trac tickets since July 2

Want to look deeper into the details and technical notes for this release? You might want to make your first stop The WordPress 6.6 Field Guide. Then, check out this list:

• Roster of design tools per block (WordPress 6.6 edition)
• All 6.6-related developer notes

You can contribute. Here’s how

WordPress is the world’s most popular open source web platform, thanks to a passionate community of people who collaborate on its development in a wide variety of ways. You can help—whether or not you have any technical expertise.

Get involved in testing

Testing for issues is critical to keeping WordPress speedy, stable, and secure. It’s also a vital way for anyone to contribute. This detailed guide will walk you through testing features in WordPress 6.6. If you’re new to testing, follow this general testing guide for more details on getting set up.

If you encounter an issue, please report it to the Alpha/Beta area of the support forums. If you are comfortable writing a reproducible bug report, you can also report it on WordPress Trac. Before you do either, you may want to check your issue against a list of known bugs.

Curious about testing releases in general? Follow along with the testing initiatives in Make Core and join the #core-test channel on Making WordPress Slack.

Please update your WordPress product

If you build themes, plugins, blocks, or patterns, your efforts play an integral role in adding new functionality to WordPress and helping bring new people and ideas to the most vibrant (and massive!) open source community in the world. 

Thanks for continuing to test your products with the WordPress 6.6 betas and release candidates. With RC3, you’ll want to make sure everything is working smoothly, and if it’s a plugin, update the “Tested up to” version in its readme file to 6.6.

If you find compatibility issues, please post detailed information to the support forum.

Help translate WordPress

Do you speak a language other than English? ?Espa?ol? Fran?ais? Русский? 日本語? ??????? ?????? You can help translate WordPress into more than 100 languages.

The RC3 haiku

One week to go. Then:
Open the paintbox! Try the tools!
Play a new jazz tune.

Props to @meher and @audrasjb. for peer review.

This 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. Instead, please evaluate RC2 on a test server or a local environment.

Reaching this phase of the release cycle is a worthy achievement. While release candidates are considered ready for release, your testing is still vital to make sure everything in WordPress 6.6 is the best it can be.

You can test WordPress 6.6 RC2 in four ways:

The target for the WordPress 6.6 release is July 16, 2024. Get an overview of the 6.6 release cycle, and check the Make WordPress Core blog for 6.6-related posts in the next few weeks for further details.

What’s in WordPress 6.6 RC2?

Thanks to your testing and many other contributors‘ up to now, this release includes more than 19 bug fixes for the Editor and more than 20 tickets for WordPress Core.

Get a recap of WordPress 6.6’s highlighted features in the Beta 1 announcement. For more technical information related to issues addressed since Beta 3, you can browse the following links:

• GitHub commits for 6.6 since June 25
• Closed Trac tickets since June 25

Want to look deeper into the details and technical notes for this release? You might want to make your first stop The WordPress 6.6 Field Guide. Then, check out this list:

• Roster of design tools per block (WordPress 6.6 edition)
• Hallway Hangout: Section styles and other block style variation updates
• Recap Hallway Hangout: Exploring Grid Layouts
• Editing custom fields from connected blocks
• Updates to the Interactivity API in 6.6
• All 6.6-related developer notes

You can contribute. Here’s how

WordPress is the world’s most popular open source web platform, thanks to a passionate community of people who collaborate on its development in a wide variety of ways. You can help—whether or not you have any technical expertise.

Get involved in testing

Testing for issues is critical to keeping WordPress speedy, stable, and secure. It’s also a vital way for anyone to contribute. This detailed guide will walk you through testing features in WordPress 6.6. If you’re new to testing, follow this general testing guide for more details on getting set up.

If you encounter an issue, please report it to the Alpha/Beta area of the support forums. If you are comfortable writing a reproducible bug report, you can also report it on WordPress Trac. Before you do either, you may want to check your issue against a list of known bugs.

Curious about testing releases in general? Follow along with the testing initiatives in Make Core and join the #core-test channel on Making WordPress Slack.

Search for vulnerabilities

From now until the final release candidate of WordPress 6.6 (scheduled for July 9), the financial reward for reporting new, unreleased security vulnerabilities doubles. Please follow responsible disclosure practices as detailed in the project’s security practices and policies outlined on the HackerOne page and in the security white paper.

Update your theme or plugin

If you build themes, plugins, blocks, or patterns, your products play an integral role in extending the functionality and value of WordPress for all users.?

Thanks for continuing to test your products with the WordPress 6.6 beta releases. With RC2, you’ll want to finish your testing and update the “Tested up to” version in your plugin’s readme file to 6.6.

If you find compatibility issues, please post detailed information to the support forum.

Help translate WordPress

Do you speak a language other than English? ?Espa?ol? Fran?ais? Русский? 日本語? ??????? ?????? You can help translate WordPress into more than 100 languages.

Release the haiku

6.6 draws near.
In two weeks the final’s here.
Test. Test. Then test more.

Props to @juanmaguitar, @meher, @desrosj and @atachibana for peer review.

This 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. Instead, please evaluate RC1 on a test server or a local environment.

Reaching this phase of the release cycle is a worthy achievement. While release candidates are considered ready for release, testing is still vital to make sure everything in WordPress 6.6 is the best it can be.

You can test WordPress 6.6 RC1 in four ways:

The current target for the WordPress 6.6 release is July 16, 2024. Get an overview of the 6.6 release cycle, and check the Make WordPress Core blog for 6.6-related posts in the next few weeks for further details.

Two notes about changes in the RC period

Hard string freeze: From now until July 16, there is a hard string freeze in place—no strings may change, and no new strings may be committed. That’s to give the Polyglots team time to translate WordPress 6.6 into as many languages as possible before final release.

Two-committer signoff: Commits in the RC period also require two Core committers to sign off on every merge. Since release candidates are supposed to be ready to go, only major fixes and blessed tasks should merge at this late date.

What’s in WordPress 6.6 RC1?

Thanks to your testing and many other contributors‘ up to now, this release includes more than 40 bug fixes for the Editor and more than 40 tickets for WordPress Core.

Get a recap of WordPress 6.6’s highlighted features in the Beta 1 announcement. For more technical information related to issues addressed since Beta 3, you can browse the following links:

• GitHub commits for 6.6 since June 18
• Closed Trac tickets since June 18

Want to look deeper into the details and technical notes for this release? These recent posts cover some of the latest updates:

• WordPress 6.6 CSS Specificity
• Site-wide background images in WordPress 6.6
• Section Styles
• Roster of design tools per block (WordPress 6.6 edition)
• The WordPress 6.6 Field Guide
• All 6.6-related developer notes

How you can contribute

WordPress is open source software made possible by a passionate community of people who collaborate on and contribute to to its development. The resources below outline a wide variety of ways you can help the world’s most popular open source web platform, whether or not you have any technical expertise.

Get involved in testing

Testing for issues is critical to making sure WordPress is speedy and stable. It’s also a vital way for anyone to contribute. This detailed guide will walk you through testing features in WordPress 6.6. If you’re new to testing, follow this general testing guide for more details on getting set up.

If you encounter an issue, please report it to the Alpha/Beta area of the support forums. If you are comfortable writing a reproducible bug report, you can also report it on WordPress Trac. Before you do either, you may want to check your issue against a list of known bugs.

Curious about testing releases in general? Follow along with the testing initiatives in Make Core and join the #core-test channel on Making WordPress Slack.

Search for vulnerabilities

From now until the final release candidate of WordPress 6.6 (scheduled for July 16), the monetary reward for reporting new, unreleased security vulnerabilities doubles. Please follow responsible disclosure practices as detailed in the project’s security practices and policies outlined on the HackerOne page and in the security white paper.

Update your theme or plugin

If you build themes, plugins, blocks or patterns, your products play an integral role in extending the functionality and value of WordPress for all users. 

Thanks for continuing to test your themes and plugins with the WordPress 6.6 beta releases. With RC1, you’ll want to finish your testing and update the “Tested up to” version in your plugin’s readme file to 6.6.

If you find compatibility issues, please post detailed information to the support forum.

Help translate WordPress

Do you speak a language other than English? ?Espa?ol? Fran?ais? Русский? 日本語? ??????? ?????? You can help translate WordPress into more than 100 languages.

Release the haiku

We’re here already?
RC1 means three weeks left.
Have some fun—come test!

Props to @meher, @audrasjb for collaborating on this post.

This release features three security fixes. Because this is a security release, it is recommended that you update your sites immediately. This minor release also includes 3 bug fixes in Core.

You can download WordPress 6.5.5 from www.remarpro.com, or visit your WordPress Dashboard, click “Updates”, and then click “Update Now”. If you have sites that support automatic background updates, the update process will begin automatically.

WordPress 6.5.5 is a short-cycle release. The next major release will be version 6.6 which is scheduled for July 16, 2024.

For more information on WordPress 6.5.5, please visit the HelpHub site.

Security updates included in this release

The security team would like to thank the following people for responsibly reporting vulnerabilities, and allowing them to be fixed in this release:

• A cross-site scripting (XSS) vulnerability affecting the HTML API reported by Dennis Snell of the WordPress Core Team, along with Alex Concha and Grzegorz (Greg) Zió?kowski of the WordPress security team.
• A cross-site scripting (XSS) vulnerability affecting the Template Part block reported independently by Rafie Muhammad of Patchstack and during a third party security audit.
• A path traversal issue affecting sites hosted on Windows reported independently by Rafie M & Edouard L of Patchstack, David Fifield, x89, apple502j, and mishre.

Thank you to these WordPress contributors

This release was led by Aaron Jorbin.

WordPress 6.5.5 would not have been possible without the contributions of the following people. Their asynchronous coordination to deliver maintenance and security fixes into a stable release is a testament to the power and capability of the WordPress community.

Aaron Jorbin, Alex Concha, Andrew Ozz, bernhard-reiter, Colin Stewart, David Baumwald, Dennis Snell, Grant M. Kinney, Greg Zió?kowski, Jb Audras, Jonathan Desrosiers, Matias Ventura, Miguel Fonseca, Peter Wilson, Rajin Sharwar, Scott Reilly, Tonya Mork

How to contribute

To get involved in WordPress core development, head over to Trac, pick a ticket, and join the conversation in the #core Slack channel. Need help? Check out the Core Contributor Handbook.

Already testing WordPress 6.6? The fourth beta is now available (zip) and it contains these security fixes. For more on 6.6, see the beta 3 announcement post. Learn more about testing WordPress 6.6 here.

Props to Paul Kevan, Ehtisham Siddiqui, Alex Concha, Tonya Mork, and Angela Jin for reviewing.