Each WordPress release celebrates an artist who has made an indelible mark on the world of music. WordPress 6.7, code-named “Rollins,” pays tribute to the legendary jazz saxophonist Sonny Rollins. Known as one of the greatest improvisers and pioneers in jazz, Rollins has influenced generations of musicians with his technical brilliance, innovative spirit, and fearless approach to musical expression.

Sonny Rollins’ work is characterized by its unmatched energy and emotional depth. His compositions, such as “St. Thomas,” “Oleo,” and “Airegin,” are timeless jazz standards, celebrated for their rhythmic complexity and melodic inventiveness. Rollins’ bold and exploratory style resonates with WordPress’ own commitment to empowering creators to push boundaries and explore new possibilities in digital expression.

Embrace the spirit of innovation and spontaneity that defines Rollins’ sound as you dive into the new features and enhancements of WordPress 6.7.

Welcome to WordPress 6.7!

WordPress 6.7 debuts the modern Twenty Twenty-Five theme, offering ultimate design flexibility for any blog at any scale. Control your site typography like never before with new font management features. The new Zoom Out feature lets you design your site with a macro view, stepping back from the details to bring the big picture to life.

Introducing Twenty Twenty-Five

Endless possibility without complexity

Twenty Twenty-Five offers a flexible, design-focused theme that lets you build stunning sites with ease. Tailor your aesthetic with an array of style options, block patterns, and color palettes. Pared down to the essentials, this is a theme that can truly grow with you.

Get the big picture with Zoom Out

Explore your content from a new perspective

Edit and arrange entire sections of your content like never before. A broader view of your site lets you add, edit, shuffle, or remove patterns to your liking. Embrace your inner architect.

Connect blocks and custom fields with no hassle (or code)

A streamlined way to create dynamic content

This feature introduces a new UI for connecting blocks to custom fields, putting control of dynamic content directly in the editor. Link blocks with fields in just a few clicks, enhancing flexibility and efficiency when building. Your clients will love you—as if they didn’t already.

Embrace your inner font nerd

New style section, new possibilities

Create, edit, remove, and apply font size presets with the next addition to the Styles interface. Override theme defaults or create your own custom font size, complete with fluid typography for responsive font scaling. Get into the details!

Performance

WordPress 6.7 delivers important performance updates, including faster pattern loading, optimized previews in the data views component, improved PHP 8+ support and removal of deprecated code, auto sizes for lazy-loaded images, and more efficient tag processing in the HTML API.

Accessibility

65+ accessibility fixes and enhancements focus on foundational aspects of the WordPress experience, from improving user interface components and keyboard navigation in the Editor, to an accessible heading on WordPress login screens and clearer labeling throughout.

And much more

For a comprehensive overview of all the new features and enhancements in WordPress 6.7, please visit the feature-showcase website.

Learn more about WordPress 6.7

Learn WordPress is a free resource for new and experienced WordPress users. Learn is stocked with how-to videos on using various features in WordPress, interactive workshops for exploring topics in-depth, and lesson plans for diving deep into specific areas of WordPress.

Read the WordPress 6.7 Release Notes for information on installation, enhancements, fixed issues, release contributors, learning resources, and the list of file changes.

Explore the WordPress 6.7 Field Guide. Learn about the changes in this release with detailed developer notes to help you build with WordPress.

The 6.7 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.7 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: David Baumwald
• Core Tech Leads: Peter Wilson, Kira Schroder
• Editor Tech Leads: David Smith, Kai Hao, Robert Anderson
• Core Triage Leads: Stoyan Georgiev, Ahmed Kabir Chaion
• Editor Triage Leads: Nick Diego, Damon Cook
• Documentation Leads: Fabian Kägy, Mumtahina Faguni
• Test Lead: Ankit K. Gupta
• Design Lead: Joen Asmussen
• Performance Lead: Mukesh Panchal
• Default Theme Design Lead: Beatriz Fialho
• Default Theme Development Leads: Carolina Nymark, Juan Aldasoro

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.7 reflects the tireless efforts and passion of more than 780 contributors in countries all over the world. This release also welcomed over 230 first-time contributors!

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

!Benni · 75thtrombone · Aaron Jorbin · Aaron Robertshaw · Aaron Ware · aatanasov · Abha Thakor · abhi3315 · Abhishek Deshpande · Abir · acafourek · Adam Heckler · Adam Silverstein · Adam Wood · Adam Zieliński · Adarsh Akshat · Adrian · aduth · Ahmar Zaidi · Ahmed Kabir Chaion · Ahmed Saeed · Ahsan Khan · Ajit Bohra · Akash Dhawade · Aki Hamano · Akira Tachibana · Akshat Kakkad · Al-Amin Firdows · Alan Fuller · Albert Juhé Lluveras · Alessandro Tesoro · Alessio · Alex Concha · Alex Cuadra · Alex Lende · Alex Stine · alex27 · Alexander Frank · Alexandre Buffet · Alexandru Horeanu · Ali Ali · aliaghdam · allilevine · Alvaro Gómez · Alvi Tazwar · Amin Charoliya · Amir Abbas · Amit Raj · Amjad Ali · Anand Thakkar · Andrea Fercia · Andrea Roenning · Andrei Draganescu · Andrei Lupu · andreiglingeanu · Andrew Hayward · Andrew Ozz · Andrew Serong · Andrey "Rarst" Savchenko · André Maneiro · Andy Fragen · Angelika Reisiger · Aniket Patel · Ankit K Gupta · Ankit K. Gupta · Ankit Kumar Shah · Ankur Vishwakarma · Anne McCarthy · Anthony Burchell · Anthony Hortin · Antoine · Anton Vlasenko · Antonio Sejas · apmeyer · Ari Stathopoulos · Armando J. Perez Carreno · Armands · arnaudbroes · Art Smith · Artemio Morales · Arthur Chu · arypneta · asafm7 · Aslam Doctor · Autumn · Ayesh Karunaratne · Bård Bjerke Johannessen · Béryl de La Grandière · Balu B · Barry Ceelen · Bart Kalisz · Beatriz Fialho · Ben Dwyer · Benjamin Denis · Benjamin Zekavica · Benoit Chantre · Bernhard Kau · Bernhard Reiter · Bernhard Riedl · bernhard-reiter · berubenic · Bhavesh · bijit027 · Birgit Pauli-Haack · blindmikey · bobbyleenoblestudios · Bogdan Nikolic · Brad · brad hogan · Brad Jorsch · Brandon Kraft · Brent Jett · Brett Shumaker · Brian Alexander · Brian Coords · Brian Gardner · Brian Gosnell · Brian Henry · bridgetwes · brobken · Bruno Freiberger Garcia · Cambabutonono · Carlos Bravo · Carlos G. P. · Carolina Nymark · Carsten Bach · cbirdsong · Chirag Mathur · ChriCo · Chris Reynolds · Chris Trynkiewicz (Sukces Strony) · Christoph Daum · Christopher Finke · Christopher Kanitz · Christy Nyiri · Ciprian · codersantosh · Colin Stewart · Corey Worrell · Courtney Robertson · craynor · creativethemeshq · Cullen Whitmore · Cupid Chakma · cweiske · Cyrille · da5f656f · Dademaru · daleharrison · Damon Cook · Damon Cook · Dani Guardiola · Daniel Richards · Daniele Scasciafratte · Danny · dannyreaktiv · darerodz · Dareth NHANG · Darren Ethier (nerrad) · Darshit Rajyaguru · daveagp · David · David Ballarin Prunera · David Baumwald · David Biňovec · David Bowman · David Brown · David Calhoun · David Godleman · David Henriet · David Herrera · David Levine · David Rozando · David Shanske · David Smith · ddewan · Dean Sas · DEBARGHYA BANERJEE · Deepak Rohilla · Deepak Vijayan · Dekadinious · Dennis Snell · Derek Smart · Deryck · designsimply · Devansh Chaudhary · devspace · Dhananjay Kuber · Dharmesh Patel · Dhrumil Kumbhani · Dhruval Shah · Dhruvang21 · Dilip Bheda · Dilip Modhavadiya · Dion Hulse · Divi Banks · dj.cowan · djennez · Doni Kuntoro · Dor Zuberi · Drew Jaynes · Drivingralle · drzraf · Earle Davies · eballeste · eclev91 · Ed Beck · ejnwebmaster · elfu98 · Elio Rivero · Ella van Durpe · Elliott Richmond · Emmanue ATSÉ · Emmanuel Hesry · emmanuel78 · Enrico Battocchi · Enrique Sánchez · Eric Dye · Erik · erikiva · erikyo · Evan Herman · Evan Mullins · Fabian Kägy · Fabio Rubioglio · FahimMurshed · Faisal Ahammad · Faisal Alvi · Faizan Nabi · Farhan Ahmed · Fayyaz · Felix Arntz · Felix Renicks · Fernando Jorge Mota (a11n) · Firoz Sabaliya · Francisco · Fransisca H · fullworks · Gale Wallace · gansbrest · Gareth Elwell · Garrett Hyder · Gary Pendergast · Gaurav Tiwari · gauravsingh7 · Georg · George Mamadashvili · Gerardo Pacheco · Germán Freixinós · gmariani405 · GraemeF · Grant M. Kinney · greentreefrog · GreenWorld · Greg Ziółkowski · Guido Scialfa · Gyurmey · Héctor Prieto · Halil ESEN · hanneslsm · Hans-Gerd Gerhards · Hardip Parmar · Hareesh S · Harper Holsinger · Harsh Gajipara · harshvaishnav · Haz · hectorjarquin · hedgefield · Helen Hou-Sandi · Henrique Iamarino · Himanshu Pathak · hirschferkel · Hit Bhalodia · Hossein · htmgarcia · huubl · Huzaifa Al Mesbah · Ibrahim · Ibrahim Riaz · Imran Hossain (a11n) · Isabel Brison · IT Path Solutions · itapress · Ivan Ottinger · Jack Stevens · Jacob Cassidy · Jacob Smith · jagirbahesh · Jainil Shah · Jakob Trost · James Koster · James Osborne · James Rosado · James Wesley Goedert · Jan Pfeil · janak Kaneriya · Jarda Snajdr · jarekmorawski · Jarko Piironen · Jason Bahl · Jason LeMahieu (MadtownLems) · javad2000 · Javier Arce · Jawad Malik · Jay · Jayadevan k · jbrya029 · JD Ahir · Jean-Baptiste Audras · Jeff Chi · Jeff Ong · Jeffrey de Wit · Jeffrey Paul · Jenil Kanani · Jennifer Farhat · Jenny Dupuy · Jeremy Felt · Jeremy Herve · Jerry Jones · Jesko Bendmann · Jessica Lyschik · Jetal dobariya · Jigar Panchal · jimmyh61 · Joe Dolson · Joe Hoyle · Joe McGill · Joen Asmussen · John Blackbourn · John Espiritu · John Godley · John James Jacoby · John Regan · JohnRDOrazio · Jon Surrell · Jonas · Jonathan Bossenger · Jonathan Desrosiers · Jonny Harris · Jonny Waters · jordesign · Jorge Costa · Jos Klever · Jose Varghese · Josepha · Joshua Goode · Jossnaz · Juan Aldasoro · JuanMa Garrido · julianoe · Julie Moynat · Juliette Reinders Folmer · Juned Sabaliya · Justin Tadlock · K. Adam White · Kaavya Iyer (woo-hc) · Kadim Gültekin · KafleG · Kai Hao · Kajal Gohel · Kamal Hosen · Kamran Hussen · Karan Gupta · Karol Manijak · Karthik Thayyil · Kartik Mehta · Kartik Suthar · kbrownkd (a11n) · Keffr3n · Kel Santiago-Pilarski · Kellen Mace · Kelly Choyce-Dwan · keoshi · Kevin Behrens · Kevin Taron · kevinswalsh · Khokan Sardar · Kira Schroder · Kishan Jasani · kisquian · Kjell Reigstad · kkmuffme · Knut Sparhell · Kowsar Hossain · kracked888 · Krishna Neupane · kristastevens · Krupa Nanda · Krupal Panchal · Kunal Madhak · Kunjan Gohel · Kurt Payne · Kushang Tailor · Lae · Lara Schenck · lastsplash (a11n) · Laura Byrne · laurelfulford · Lauren · Lawrence Joe · leemon · Lena Morita · Liam Gladdy · lifelightweb · Linkon Miyan · Linnea Huxford · liviopv · Louis Wolmarans · Lourens · Love Soni · Lucas · Luigi Teschio · Luis Felipe Zaguini · luisherranz · lukasbesch · Luke Carbis · Madhu Dollu · madpeter · Maggie Cabrera · Mahmudul Haque Nadim · Mai · Makarand G. Mane · manbo · Manesh Timilsina · Manuel Schmalstieg · Manzoor Wani (a11n) · María Anguas · Marc · Marc Armengou · Marcel Tannich · Marcelo de Moraes Serpa · Marcin Pietrzak · Marco Ciampini · Marco Pereirinha · marcwieland95 · Marek Železný · margolisj · Maria Yohana · Marie · Marin Atanasov · Mario Santos · Marius L. J. · mariushosting · Mark Howells-Mead · Mark Parnell · Mark-k · Martijn van der Klis · martin.krcho · marybaum · mat_ · Matias Benedetto · Matias Ventura · Matt Mullenweg · Matt Robinson · Matt Sherman · Matteo Enna · Matthew Boynes · Matthew Riley MacPherson · Matthias Kittsteiner · mattraines · maurodf · Mayank Tripathi · Mayur Prajapati · mcrisp1972 · Md Abul Bashar · Md Hossain Shohel · Md. Istiaq Hossain · mdviralsampat · megane9988 · Mehedi Hassan · Mehul Kaklotar · Mel Choyce-Dwan · meteorlxy · Micha Krapp · Michael Beckwith · Michael Bourne · Michael James Ilett · michaelpick · michaelwp85 · Michal Czaplinski · Michelle Bulloch · Miguel Axcar · Miguel Fonseca · Miguel Lezama · Mikael Korpela · Mike McAlister · Mike Ritter · mikeb8s · Mikey Binns · milamj · Milana Cap · Mitchell Austin · mklusak · mleathem · mlf20 · Mobarak Ali · Mohit Dadhich · Morgan Estes · Mosne / Paolo Tesei · mossy2100 · mreishus · Muhibul Haque · mujuonly · Mukesh Panchal · Mumtahina Faguni · Nadir Seghir a11n · Naeem Haque · Nagesh Pai · Narendra Sishodiya · Naresh Bheda · Nate Finch · Nate Gay · Nazmul Hasan Robin · Nebojša Jurčić · nek285 · nendeb · neo2k23 · neotrope · Nicholas Garofalo · Nick Bohle · Nick Diego · Nick Halsey · Nick the Geek · Nicole Furlan · nidhidhandhukiya · Nihar Ranjan Das · Nik Tsekouras · Nikita Solanki · Niraj Giri · Nirav Sherasiya · Nithin John · Nithin SreeRaj · Noah Allen · Noruzzaman · nurielmeni · obliviousharmony · Olaf Lederer · Olga Gleckler · Oliver Campion · Olivier Lafleur · Omar Alshaker · Oscar Hugo Paz · p15h · Paal Joachim Romdahl · Pablo Hernández · Pablo Honey · Pamela Ribeiro · pander · Paolo L. Scala · Paragon Initiative Enterprises · Parin Panjari · Parth vataliya · Pascal Birchler · Pat O'Brien · Patricia BT · Patrick Lumumba · Paul Bearne · Paul Biron · Paul Kevan · Paul Schreiber · Paul Wilde · paulcline · Paulo Trentin · Pavan Patil · pcarvalho · Pedro Mendonça · perryrylance · Peter Rubin · Peter Wilson · petitphp · pevogam · Phi Phan · Phil Johnston · Philipp Bammes · philwebs · Pieterjan Deneys · Piotrek Boniu · Pitam Dey · Plamen Georgiev · Pooja N Muchandikar · pooja9712 · porg · ppolo99 · Praful Patel · Pranit Dugad · Pratik Kumar · Presskopp · prettyboymp · prionkor · pwtyler · Rachel Baker · Rachel Winspear · Rafael Fischmann · Rafael Gallani · Rafiqul Islam · Rahmat Gumilar · rahulharpal · Raj Patel · Rajin Sharwar · Rajkumar Shashwata Halder · Ramon Ahnert · Ramon Corrales · ramon fincken · Ramon James · Ramswarup Rathod · Raul Martinez · rcneil · realthemes · Rejaul Alom Khan · Renatho (a11n) · reputeinfosystems · retrofox · Riad Benguella · Rich Tabor · Rick Hellewell · Riddhi Patel · Rishi Mehta · Rishi Shah · Rishit Gupta · rithik56 · Robert Anderson · Robert Biswas · Robert Ghetau · rocket.works - Dominik Friedrich · Rodel Calasagsag a11n · Rodrigo · Rodrigo Primo · Rohan Jha · rohitmathur7 · Rostislav Wolný · Roy Tanck · roygbyte · royho · rpf5573 · rslee · Ruchir Goswami · Rufaro Madamombe · Ryan Boren · Ryan Leeson · Ryan Urban · Ryan Welcher · S P Pramodh · Sébastien SERRE · Sérgio Gomes · Sören Wünsch · sadmansh · Saeed Piri · Sagar Tamang · sahiladit · Sainath Poojary · Sakib Mohammed · Sam Toohey · samiamnot · Sampat Viral · Samuel Sidler · Samuel Silva · Sanne van der Meulen · Sarah Norris · sarahricker · Sarthak Nagoshe · Sathiya Venkatesan · Satish Prajapati · Saul Fougnier · Saulius Vikerta · Saxon Fletcher · Sayedul Sayem · scholdstrom · Scott Buscemi · Scott Kingsley Clark · Scott Reilly · Scott Taylor · scottculverhouse · seanavers · Seif Radwane · Sergey · Sergey Biryukov · Serhiy Zakharchenko · Seth Rubenstein · Shail Mehta · Shalin Shah · Sharon Austin · SheulyShila · Shoe · Showrav Hasan · Shreya Agarwal · Silas Köhler · siliconforks · Simone Maranzana · Siobhan · smerriman · Sneha Patil · Sophie - a11n · Souptik Datta · Sourabh Jain · Sourav Pahwa · staurand · Stefano Minoia · stein2nd · Stephen Bernhardt · Steven Lin · Steven Thompson · Stoyan Georgiev · styleshit · Sudip Dadhaniya · Sumit Bagthariya · Sumit Singh · Sunil Prajapati · Sunny · superchlorine · Sybre Waaijer · Syeda Fahima Jannath · Takahashi Fumiki · Takashi Irie · Tammie Lister · Tanbir Ahmod · Tanvirul Haque · Tapan Kumer Das · Taylor Gorman · tdrayson · thejaydip · thelmachido a11n · them.es · Thomas Kräftner · Thrijith Thankachan · Timi Wahalahti · Timothy Jacobs · Tirth Doshi · tmanoilov · toastercookie · TobiasBg · tobifjellner (Tor-Bjorn “Tobi” Fjellner) · Tom Cafferkey · Tom de Visser · Tom J Nowell · Tomas Llobet-Arany · tomhine · Tonya Mork · Toro_Unit (Hiroshi Urabe) · Torsten Landsiedel · tropicalista · Troy Chaplin · Trupti Kanzariya · tunetheweb · twstokes · Ugyen Dorji · Umesh Gupta · Umesh Singh · up1512001 · Uttam Kumar Dash · valer1e · vertisoft · Vicente Canales · Vijaysinh Zala · Viktor Szépe · Vinit · Vipul Ghori · Vipul Gupta · Vipul Patil · Vraja Das · Vrishabh Jasani · wbdv · WebMan Design | Oliver Juhas · webwurm · wesrapyd · Weston Ruter · Will Skora · William Alexander · williampatton · wongjn · WPeople · wpsoul · wzieba · xipasduarte · Yani · Yann · Yannis Guyon · Yogesh Bhutkar · ytfeLdrawkcaB · Yui · Yukinobu Asakawa · Yuvrajsinh Sisodiya · Zack Krida · zeelthakkar · zitaruksergij · Zunaid Amin

More than 40 locales have fully translated WordPress 6.7 into their language making this one of the most translated releases ever on day one. 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.

The third release candidate (RC3) for WordPress 6.7 is ready for download and testing!

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, it’s recommended that you evaluate RC3 on a test server and site.

Reaching this phase of the release cycle is an important milestone. While release candidates are considered ready for release, testing remains crucial to ensure that everything in WordPress 6.7 is the best it can be.

You can test WordPress 6.7 RC3 in four ways:

Plugin	Install and activate the WordPress Beta Tester plugin on a WordPress install. (Select the “Bleeding edge” channel and “Beta/RC Only” stream).
Direct Download	Download the RC3 version (zip) and install it on a WordPress website.
Command Line	Use the following WP-CLI command: wp core update --version=6.7-RC3
WordPress Playground	Use the 6.7 RC3 WordPress Playground instance (available within 35 minutes after the release is ready) to test the software directly in your browser without the need for a separate site or setup.

The current target for the WordPress 6.7 release 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 further details.

What’s in WordPress 6.7 RC3?

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

• GitHub commits for 6.7 since October 29
• Closed Trac tickets since October 29

How you can contribute

WordPress is open source software made possible by a passionate community of people collaborating on and contributing to its development. The resources below outline various ways you can help the world’s most popular open source web platform, regardless of your technical expertise.

Get involved in testing

Testing for issues is critical to ensuring WordPress is performant and stable. It’s also a meaningful way for anyone to contribute. This detailed guide will walk you through testing features in WordPress 6.7. For those 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 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.

Search for vulnerabilities

From now until the final release of WordPress 6.7 (scheduled for November 12, 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.

Update your theme or plugin

For plugin and theme authors, 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.7 beta releases. With RC3, you’ll want to conclude your testing and update the “Tested up to” version in your plugin’s readme file to 6.7.

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

RC3 arrives,
Final polish, last bugs fall,
Six point seven calls.

Thank you to the following contributors for collaborating on this post: @peterwilsoncc, @joedolson, @sabernhardt.

The second release candidate (RC2) for WordPress 6.7 is ready for download and testing!

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, it’s recommended that you evaluate RC2 on a test server and site.

Reaching this phase of the release cycle is an important milestone. While release candidates are considered ready for release, testing remains crucial to ensure that everything in WordPress 6.7 is the best it can be.

You can test WordPress 6.7 RC2 in four ways:

Plugin	Install and activate the WordPress Beta Tester plugin on a WordPress install. (Select the “Bleeding edge” channel and “Beta/RC Only” stream).
Direct Download	Download the RC2 version (zip) and install it on a WordPress website.
Command Line	Use the following WP-CLI command: wp core update --version=6.7-RC2
WordPress Playground	Use the 6.7 RC2 WordPress Playground instance (available within 35 minutes after the release is ready) to test the software directly in your browser without the need for a separate site or setup.

The current target for the WordPress 6.7 release 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 further details.

What’s in WordPress 6.7 RC2?

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

• GitHub commits for 6.7 since October 22
• Closed Trac tickets since October 22

How you can contribute

WordPress is open source software made possible by a passionate community of people collaborating on and contributing to its development. The resources below outline various ways you can help the world’s most popular open source web platform, regardless of your technical expertise.

Get involved in testing

Testing for issues is critical to ensuring WordPress is performant and stable. It’s also a meaningful way for anyone to contribute. This detailed guide will walk you through testing features in WordPress 6.7. For those 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 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.

Search for vulnerabilities

From now until the final release of WordPress 6.7 (scheduled for November 12, 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.

Update your theme or plugin

For plugin and theme authors, 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.7 beta releases. With RC2, you’ll want to conclude your testing and update the “Tested up to” version in your plugin’s readme file to 6.7.

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

Six point seven’s dawn,
RC2 sweeps bugs away,
Sites stand firm and strong.

Thank you to the following contributors for collaborating on this post: @jorbin.

In nearly 1,000 days, the WordPress community has created 1,000 Block themes—coming together to use the full potential of the Site Editor and unleash new creative possibilities for everyone.

First introduced in WordPress 5.9, Block themes have steadily evolved, improving flexibility and functionality for themers, users, and agencies alike. Now, design tools allow customizing almost every detail. With style variations, users can change the overall look of their site in a few clicks. You can even use curation options to customize the editing process itself. But we’re not done! We can’t wait to keep pushing Block themes even further. Thank you to every early adopter who, by embracing early features with passion, helped shape the Block themes we love today with feedback and testing.

If you haven’t yet explored Block themes, check out some of the resources below to get inspired:

• Use one of the 1,000 Block themes available and see what you can create. For an easy way to explore, try WordPress Playground to quickly get started with a temporary site. 
• Read the Theme handbook to understand types of themes, how themes work, and how to get started building. 
• Use the Create Block Theme plugin to streamline Block theme creation with a dedicated tutorial on Learn WordPress that will help you get started.  
• Get inspired by watching and joining community members building themes together. This is a great way for folks new to Block themes to learn, hands-on. 

Let’s celebrate and share our contributions! Please comment on the Theme Team’s post dedicated to highlighting this milestone to share your favorite Block theme and thank those who have contributed along the way. 

Thank you to @kristastevens for editorial help, @beafialho for the featured image, and @kafleg for reviewing.

The first release candidate (RC1) for WordPress 6.7 is ready for download and testing!

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, it’s recommended that you evaluate RC1 on a test server and site.

Reaching this phase of the release cycle is an important milestone. While release candidates are considered ready for release, testing remains crucial to ensure that everything in WordPress 6.7 is the best it can be.

You can test WordPress 6.7 RC1 in four ways:

Plugin	Install and activate the WordPress Beta Tester plugin on a WordPress install. (Select the “Bleeding edge” channel and “Beta/RC Only” stream).
Direct Download	Download the RC1 version (zip) and install it on a WordPress website.
Command Line	Use the following WP-CLI command: wp core update --version=6.7-RC1
WordPress Playground	Use the 6.7 RC1 WordPress Playground instance (available within 35 minutes after the release is ready) to test the software directly in your browser without the need for a separate site or setup.

The current target for the WordPress 6.7 release 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 further details.

What’s in WordPress 6.7 RC1?

Get a recap of WordPress 6.7’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.7 since October 15
• Closed Trac tickets since October 15

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

• New block type registration APIs to improve performance in WordPress 6.7
• Automatic conversion of HEIC images to JPEG in WordPress 6.7
• Auto Sizes for Lazy Loaded Images in WordPress 6.7
• New Plugin Template Registration API in WordPress 6.7
• Developer Notes for Zoom Out in WordPress 6.7
• Block Bindings: Improvements to the Editor Experience in 6.7
• Internationalization improvements in 6.7
• Updates to the HTML API in 6.7
• Miscellaneous Block Editor Changes in WordPress 6.7
• All 6.7-related developer notes

How you can contribute

WordPress is open source software made possible by a passionate community of people collaborating on and contributing to its development. The resources below outline various ways you can help the world’s most popular open source web platform, regardless of your technical expertise.

Get involved in testing

Testing for issues is critical to ensuring WordPress is performant and stable. It’s also a meaningful way for anyone to contribute. This detailed guide will walk you through testing features in WordPress 6.7. For those 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 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.

Search for vulnerabilities

From now until the final release of WordPress 6.7 (scheduled for November 12, 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.

Update your theme or plugin

For plugin and theme authors, 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.7 beta releases. With RC1, you’ll want to conclude your testing and update the “Tested up to” version in your plugin’s readme file to 6.7.

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. This release milestone (RC1) also marks the hard string freeze point of the 6.7 release cycle.

Release the haiku

I See An R.C.
You See A Chance For Testing
Six Seven For The Win!

Thank you to the following contributors for collaborating on this post: @atachibana, @jorbin.

At the heart of our community is our shared pledge to create a space that is harassment-free, welcoming, and inclusive for all. Our Community Code of Conduct already outlines a clear set of expectations, while also providing examples of unacceptable actions. Today, we are reinforcing our values by adding another element to our list of unacceptable behaviors: Publishing private messages without consent.

Why This Addition Matters

The relationships we build within our community often involve private discussions. These conversations may involve sensitive matters, personal experiences, or simply casual exchanges. Regardless of the content, every individual should feel confident that their private communications will remain private unless they grant explicit permission to share them.

Sharing private messages without consent is a breach of trust that can also lead to unintended harm, including emotional distress or misrepresentation. When members of our community feel they cannot trust others in their personal conversations, it undermines the collaborative spirit that is crucial to our collective success.

How This Change Protects the Community

By explicitly addressing the publication of private messages without consent, we are reinforcing an existing unacceptable behavior in our Community Code of Conduct: Other conduct which could reasonably be considered inappropriate in a professional setting. Sharing private communications without permission is a clear violation of professional integrity.

This new addition ensures that private messages receive the same level of protection as personal information and that sensitive communications shared in confidence will not be disclosed without prior consent. An important exception to this is when sharing private messages is necessary for reporting incidents or concerns to the Incident Response Team, as part of our commitment to maintaining a safe and respectful environment.

Ultimately, this change encourages honest, constructive engagement across all levels of participation.

Moving Forward Together

The strength of our community lies in the trust we place in one another. By clarifying and reinforcing our expectations, we are taking another step toward maintaining an inclusive, respectful, and safe environment for everyone.This new addition will take effect immediately, and violations will be handled in accordance with our existing enforcement guidelines. Together, we can ensure our community remains a place of collaboration, trust, and mutual respect.

In the midst of our legal battles with Silver Lake and WP Engine, I wanted to take a moment to highlight something positive.

Because of my friendships with the co-founders of Slack, Stewart Butterfield and Cal Henderson, WordPress.org has had a free version of the Pro version of Slack since they started in 2009. We switched from IRC to Slack, and it was like superpowers were unlocked for our team.

Over the past 10 years, Slack has been our secret weapon of productivity compared to many other open source projects. Its amazing collaboration features have allowed us to scale WordPress from running just a few blogs to now powering around 43% of all websites in the world, almost 10 times the runner-up in the market.

As we have scaled from very small to very large, Slack has scaled right alongside us, seemingly effortlessly. WordPress.org currently has 49,286 users on its Slack Business+ instance, which would cost at least $8.8M/yr if we were paying. (And we may need to go to their enterprise grid, to support e-discovery in the lawsuit attacks from WP Engine, which would cost even more.)

This incredible generosity was continued by the enlightened leadership of Marc Benioff at Salesforce when they bought Slack in 2020. However, it has not been widely known or recognized on our Five for the Future page, which only highlights self-reported contributor hours and doesn’t mention Salesforce at all.

This is a grave error, and we are correcting it today. Going forward:

• I would like every business in the world to see the amazing collaboration and productivity gains Slack has enabled for our community of tens of thousands of volunteers worldwide and consider adopting it for their own business.
• Salesforce will have a complimentary top sponsor slot at our flagship WordCamp events in the United States, Europe, and Asia, which attract thousands of people each.
• We will update our Five for the Future program to reflect contributions such as Salesforce’s going forward.

We just want to repeat: Thank you. We hope to deepen our partnership with Salesforce in the future.

Given the egregious legal attacks by WP Engine against WordPress co-founder Matt Mullenweg, a number of their customers have been looking for alternative hosting, and in return a number of hosts have created specials and promotions for WP Engine customers looking to migrate to a host that has great relations with WordPress.org. Here they are, in alphabetical order.

We’ll update this post if any new offers come online, get in touch and we’ll link it.

• Bluehost will cover migration costs, and credit back your existing contract. They offer 24/7 phone support, you can call them at 844-699-3907. Their wp.cloud-powered Cloud hosting starts at $29.99/mo.
• DreamHost is offering free migrations, with plans starting at $16.95/mo.
• Hostinger offers free migration for an unlimited number of websites with a 24/7 dedicated customer success team. Their relevant cloud plans start at $7.99/mo.
• Nexcess has plans starting at $21/mo.
• Pressable will credit back your current WP Engine contract and match their pricing, so if you’re in the middle of a long contract with WP Engine, you don’t need to wait until your renewal time.
• SiteGround has a special with 83% off and unlimited automated WP migrations, their plans start at $2.99/mo.
• WordPress.com will give you a free year of any plan they offer, and donate 5% of your purchase price to the WordPress Foundation. Their relevant plans start at $25/mo.
• For large-scale enterprise customers, WordPress VIP will cover the cost of migration. Their plans generally start at $2k/mo.

WordPress 6.7 Beta 3 is now ready for testing!

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:

Plugin	Install and activate the WordPress Beta Tester plugin on a WordPress install. (Select the “Bleeding edge” channel and “Beta/RC Only” stream).
Direct Download	Download the Beta 3 version (zip) and install it on a WordPress website.
Command Line	Use the following WP-CLI command: wp core update --version=6.7-beta3
WordPress Playground	Use the 6.7 Beta 3 WordPress Playground instance to test the software directly in your browser without the need for a separate site or setup.

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.

On behalf of the WordPress security team, I am announcing that we are invoking point 18 of the plugin directory guidelines and are forking Advanced Custom Fields (ACF) into a new plugin, Secure Custom Fields. SCF has been updated to remove commercial upsells and fix a security problem.

On October 3^rd, the ACF team announced ACF plugin updates will come directly from their website. Sites that followed the ACF team’s instructions on “How to update ACF” will continue to get updates directly from WP Engine. On October 1^st, 2024, WP Engine also deployed its own solution for updates and installations for plugins and themes across their customers’ sites in place of WordPress.org’s update service.

Sites that continue to use WordPress.org’s update service and have not chosen to switch to ACF updates from WP Engine can click to update to switch to Secure Custom Fields. Where sites have chosen to have plugin auto-updates from WordPress.org enabled, this update process will auto-switch them from Advanced Custom Fields to Secure Custom Fields.

This update is as minimal as possible to fix the security issue. Going forward, Secure Custom Fields is now a non-commercial plugin, and if any developers want to get involved in maintaining and improving it, please get in touch.

Similar situations have happened before, but not at this scale. This is a rare and unusual situation brought on by WP Engine’s legal attacks, we do not anticipate this happening for other plugins.

WP Engine has posted instructions for how to use their version of Advanced Custom Fields that uses their own update server, so you have that option, though the WordPress Security Team does not recommend it until they fix the security issues. You can uninstall Advanced Custom Fields and activate Secure Custom Fields from the plugin directory and be just fine.

There is separate, but not directly related news that Jason Bahl has left WP Engine to work for Automattic and will be making WPGraphQL a canonical community plugin. We expect others will follow as well.

The right to fork the software is at the heart of open source. WordPress itself started as a fork of the b2/cafelog project. WordPress was one of several forks from b2, which included b2++ (which eventually became WordPress Multisite) and some like b2evolution which still continue today.

The last decent fork attempt for WordPress was ClassicPress in 2018, over disagreements about Gutenberg being integrated into core.

We’re very proud to announce that Vinny Green, a former WordPress community member, has started his fork, FreeWP. We strongly encourage anyone who disagrees with the direction WordPress is headed in to join up with Vinny and create an amazing fork of WordPress. Viva FreeWP!

If there are other forks of WordPress we should highlight, let us know.

Updates with complete fork list:

• AspirePress “AspirePress exits [sic] to be a community of individuals focused on helping WordPress become the platform we all aspire for it to be.”
• b2evolution, which forked b2/cafélog at the same time WordPress did, so contains some of the same root source code.
• FreeWP, by Vinny Green.
• OpenPress is not a fork, but their name implies they want people to consider it as an alternative to WordPress. They are building on Laravel, using the CC-0 license, and claim to be optimized for AI. Their plugin to export from WordPress is here.
• WP Engine is the most confusing fork of WordPress because it claims it’s actually WordPress despite disabling core features like revisions, hiding the news and meetups widget, and running its own plugin, theme, and core update system (which is slower than core’s). This is the one fork we recommend not touching with a ten-foot pole.