This minor release features 29 bug fixes in Core and 21 bug fixes for the block editor. WordPress 6.1.1 is a short-cycle maintenance release. You can review a summary of the key updates in this release by reading the RC1 announcement.

The next major release will be version 6.2 planned for 2023.

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

You can download WordPress 6.1.1 from WordPress.org, or visit your WordPress Dashboard, click “Updates”, and then click “Update Now”.

For more information, check out the version 6.1.1 HelpHub documentation page.

Thank you to these WordPress contributors

The WordPress 6.1.1 release was led by Jonathan Desrosiers, George Mamadashvili, and Jeffrey Paul.

WordPress 6.1.1 would not have been possible without the contributions of more than 105 people. Their asynchronous coordination to deliver several enhancements and fixes into a stable release is a testament to the power and capability of the WordPress community.

10upsimon, Aaron Jorbin, Aaron Robertshaw, Adam Silverstein, Aki Hamano, alexstine, Andrei Draganescu, Andrew Ozz, Andrew Serong, Andre, Andy Fragen, Ari Stathopoulos, azurseisme, Ben Dwyer, Bernie Reiter, Bethany Chobanian Lang, Birgit Pauli-Haack, bjorn2404, Carlos Bravo, Carolina Nymark, Clayton Collie, codesdnc, Colin Stewart, Daniel Richards, David Baumwald, David Smith, David Vongries, Dilip Bheda, Dion Hulse, Dominik Schilling, Ella, Eugene M, Felix Arntz, fpodhorsky, franzaurus, gamecreature, Gary Pendergast, George Mamadashvili, gisgeo, glendaviesnz, Innovext, ironprogrammer, Isabel Brison, James, Jan Thiel, Javier Carazo, Jb Audras, jchambo, jeffpaul, joelmadigan, Joen A., John Blackbourn, John Watkins, Jonathan Desrosiers, Jonny Harris, jsh4, Juliette Reinders Folmer, K. Adam White, kacper3355, Kai Hao, Konstantin Obenland, konyoldeath, larsmqller, Lena Morita, Leo Milo, lozula, Marco Ciampini, Marin Atanasov, Marius L. J., Matt Keys, Michal Czaplinski, Miguel Axcar, Miguel Fonseca, Mukesh Panchal, mw108, Namith Jawahar, Nick Diego, Nik Tsekouras, Nithin SreeRaj, nuvoPoint, oakesjosh, ockham, Oliver Juhas, Pascal Birchler, Paul Biron, Peter Wilson, petitphp, pkolenbr, pypwalters, ramonopoly, Riad Benguella, rjasdfiii, Robert Anderson, rodricus, Ryan Kienstra, Sarah Norris, Sergey Biryukov, stentibbing, Stephen Bernhardt, Subrata Sarkar, Sybre Waaijer, Timi Wahalahti, Timothy Jacobs, Tonya Mork, Torsten Landsiedel, and vtad.

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-1-release-leads channels. Need help? Check out the Core Contributor Handbook.

Welcome to “Misha”

Say hello to WordPress 6.1, “Misha,” inspired by the life and work of jazz pianist Mikhail “Misha” Alperin. Ukrainian-born Misha introduced the work of jazz ensembles globally and is celebrated as a founding member of the Moscow Art Trio.

“Misha” further refines the site-building experience. Inside WordPress 6.1 you’ll interact with enhancements that continue to make site creation more intuitive while pushing your creative boundaries further than ever. Don’t forget to enjoy some of Misha’s jazz piano as you take in all WordPress 6.1 has to offer.

The third major release of 2022 is here. Download it now! As of the time of this release, WordPress powers 43% of websites worldwide.

Site owners and administrators should upgrade today to take full advantage of the many stability, performance, and usability enhancements. Furthermore, WordPress content creators will enjoy a suite of new features geared toward improving the writing and designing experiences.

This release includes features that many in the WordPress Community have been most excited about since the start of this project. Additional enhancements and improvements to the editor give site owners more control and easier customization while offering a more cohesive experience to users. A lot of writing-focused improvements are included in the release, because if you’re giving voices to the voiceless you’ve got to focus on folks writing the copy.

Some of my favorite enhancements are the refined ability to select partial paragraphs in a block; settings to keep list view open by default; and the keyboard shortcut to add internal links expanded to all blocks.

Josepha Haden Chomphosy, Executive Director

What’s Inside

Twenty Twenty-Three:
A fresh default theme with 10 distinct style variations

After introducing foundational elements for block themes and style variations in releases 5.9 and 6.0, WordPress site builders welcome a new default theme, Twenty Twenty-Three, that is powered by 10 different styles and tagged as  “Accessibility Ready.” These intentionally unique styles ensure users can apply a different look and feel to their site with a single click—all within a single theme.

New templates for an improved creator experience

New and more refined templates now give site builders more control over the creation of their sites. In this suite of new templates, find a custom template for posts & pages in the Site Editor. Create and edit template parts like headers and footers more quickly with a new search-and-replace tool and easily view your new site.

Design tools for more consistency and control

Thoughtful upgrades to the controls for design elements and blocks make laying out and building your new site a more consistent, complete, and intuitive experience.

Manage menus with ease

New fallback options in the navigation block mean you can edit the menu that’s open; no searching needed. Plus, the controls for choosing and working on menus have their own place in the block settings. The mobile menu system also gets an upgrade with new features, including different icon options, to make the menu yours.

Cleaner layouts and document settings visualization

View and manage post and page settings with a better-organized display improving the use of features like template picker and scheduler.

One-click lock setting for all inner blocks

When locking blocks, a new toggle lets you apply your lock settings to all the blocks in a containing block like the group, cover, and column blocks.

Improved block placeholders

Various blocks have improved placeholders that reflect customization options to help you design your site and its content. For example, the Image block placeholder displays custom borders and duotone filters even before selecting an image.

Compose richer lists and quotes with inner blocks

The List and Quote blocks now support inner blocks, allowing for more flexible and rich compositions like adding headings inside your Quote blocks.

More responsive text with fluid typography

For developers working with block themes and/or theme.json, fluid typography lets you define font sizes that adapt for easy reading in any screen size.

Add starter patterns to any post type

In WordPress 6.0, site builders could add suggested patterns so that when creating a new page, you did not have to start blank. In 6.1, site builders can continue to opt-in to this feature for not only pages but for any post type.

Find block themes faster

The Themes Directory has a filter for block themes, and a pattern preview gives a better sense of what the theme might look like while exploring different themes and patterns.

Keep your Site Editor settings for later

Site Editor settings are now persistent for each user. This means your settings will now be consistent across browsers and devices.

A streamlined style system

The CSS rules for margin, padding, typography, colors, and borders within the styles engine are now all in one place, reducing time spent on layout-specific tasks and helps to generate semantic class names.

Updated interface options and features

Updates include styling elements like buttons, citations, and links globally; controlling hover, active, and focus states for links using theme.json (not available to control in the interface yet); and customizing outline support for blocks and elements, among other features.

Continued evolution of layout options

The default content dimensions provided by themes can now be overridden in the Styles Sidebar, giving site builders better control over full-width content. Developers have fine-grained control over these controls.

Block Template parts in classic themes

Block template parts can now be defined in classic themes by adding the appropriate HTML files `parts` directory at the root of the theme.

Expanded support for Query Loop blocks

New filters let Query Block variations support custom queries for more powerful variations and advanced hierarchical post types filtering options.

Filters for all your styles

Leverage filters in the Styles sidebar to control settings at all four levels of your site—core, theme, user, or block, from less to more specific.

Spacing presets for faster, consistent design

Save time and avoid hard-coding values into a theme with preset margin and padding values for multiple blocks.

Content-only editing support for container blocks

Thanks to content-only editing settings, layouts can be locked within container blocks. In a content-only block, its children are invisible to the List View and entirely uneditable. So you control the layout while your writers can focus on the content. Combine it with block-locking options for even more advanced control over your blocks.

Other notes of interest

• 6.1 includes a new time-to-read feature showing content authors the approximate time-to-read values for pages, posts, and custom post types.
• The site tagline is empty by default in new sites but can be modified in General Settings.
• A new modal design offers a background blur effect, making it easier to focus on the task at hand.

Enhancing WordPress 6.1 Accessibility

Accessibility is an integral part of the WordPress mission of fostering an inclusive community and supporting users of all types around the world. With this in mind, WordPress 6.1 includes nearly 60 updates specifically focused on enhancing the accessibility of the platform. Read these updates to learn more about the continual initiatives aimed at improving accessibility.

Improved Performance in WordPress 6.1

WordPress 6.1 resolves more than 25 tickets dedicated to enhancing performance with improvements for every type of site. A full breakdown can be found in the Performance Field Guide.

Learn More About WordPress 6.1

See WordPress 6.1 in action! Watch a brief overview video highlighting some of the major features debuting in WordPress 6.1.

Explore learn.wordpress.org for brief how-to videos and lots more on new features in WordPress. Or join a live interactive online workshop on a specific WordPress topic.

Developers can explore the WordPress 6.1 Field Guide, complete with detailed developer notes to help you build with and extend WordPress. Read the WordPress 6.1 Release Notes for more information on the included enhancements and issues fixed, installation information, developer notes and resources, release contributors, and the list of file changes in this release.

The WordPress 6.1 Release Squad

The group listed below tirelessly supported the release, from conception to ship date, and beyond:

Release Lead: Matt Mullenweg 
Release Coordinators: Héctor Prieto and Jonathan Desrosiers 
Core Tech Co-Leads: Mike Schroder, David Baumwald, and Jeff Paul
Editor Tech Co-Leads: Michal Czaplinski, Bernie Reiter, and Carlos Bravo
Core Triage Co-Leads: JB Audras and Ahmed Chaion
Editor Triage Co-Leads: Nick Diego and Anne McCarthy
Documentation Co-Leads: Birgit Pauli-Haack, Milana Cap, and Femy Praseeth
Marketing & Communications Co-Leads: Jonathan Pantani and Dan Soschin
Test Lead: Brian Alexander
Design Lead: Rich Tabor
Default Theme Co-Leads: Beatriz Fialho & Sarah Norris

Thank you to all the contributors who dedicated time and energy to bring the best WordPress experience to everyone.

Josepha Haden Chomphosy

10upsimon · 1naveengiri · Aaron D. Campbell · Aaron Jorbin · Aaron Robertshaw · Abha Thakor · Abu Hurayra · Adam Bosco · Adam Pickering · Adam Silverstein · Adam Wiltgen · Adam Zielinski · Addie · Adil Öztaşer · aduth · Aezaz Shekh · afrid1719 · Ahmed Chaion · Ahmed Saeed · Akash Mia · Aki Hamano · Akram ul haq · Akshit Sethi · Alain Schlesser · alamgircsebd · AlanP57 · alansyue · Albert Juhé Lluveras · Alberuni Azad. · Alejandro J. Sanchez P. · Aleksej · Alex Concha · Alex Lende · Alex Mills · Alexis Coulombe · alexstine · allancole · allisonplus · Alvaro Gómez · amirkamizi · Amjad Ali · Anantajit JG · Andrea Fercia · Andreas · Andrei Draganescu · Andrei Surdu · Andrew Nacin · Andrew Ozz · Andrew Serong · Andrew Wilder · AndrewNZ · Andrey "Rarst" Savchenko · Andrija Naglic · André · Andy Fragen · Andy Keith · Aniket Patel · anitanenova · Ankit K Gupta · Anna Bansaghi · Anne McCarthy · Ante Laca · Anthony Burchell · Anton Vlasenko · apedog · apokalyptik · AR Rasel · arcangelini · archon810 · Ari Stathopoulos · Ariel Chinn · Arjun Singh · Arnab Mondal · Arslan Kalwar · Artur Grabowski · Arunas Liuiza · Aspexi · Aurooba Ahmed · Austin Matzko · Ayesh Karunaratne · azurseisme · BaneD · barneydavey · Bartosz Bobnis · Beatriz Fialho · Ben Dwyer · Ben Greeley · Benachi · Benjamin Grolleau · Benoit Chantre · Bernhard Reiter · Bernie Reiter · Bethany Chobanian Lang · Bhavik Kalpesh · Bhrugesh Bavishi · Birgir Erlendsson (birgire) · Birgit Pauli-Haack · bjorn2404 · Bob · bobbingwide · bonger · Boone Gorges · Brad Jorsch · Brandon Kraft · Brian Alexander · Brian Gardner · Bruno Cantuaria · Bruno Ribaric · burgiuk · Burhan Nasir · bwbama · cadlec · cagsmith · Carlos Bravo · Carlos Garcia Prim · Carolina Nymark · cavalierlife · cdbessig · Chad Chadbourne · Chandra M · Channing Ritter · Chetan Prajapati · Chintan hingrajiya · Chloe Bringmann · Chouby · Chris Budd · Chris Hardie · Chris Zarate · chriscct7 · chrisguitarguy · Christian-W. Budde · Christina Voudouris · Christoph Daum · Christopher Finke · Chuck Reynolds · chynnabenton · ckanderson22 · Clayton Collie · CodePoet · codesdnc · codewhy · Colin Stewart · colonelphantom · Cory Birdsong · Courtney Robertson · craigfrancis · crazycoders · Crisoforo Gaspar · Cupid Chakma · Curdin Krummenacher · cyrillbolliger · Daijiro Miyazawa · dainemawer · Daisy Olsen · Dale du Preez · Damon Cook · damonganto · Dan Farrow · Dan Soschin · Daniel Bachhuber · Daniel Iser · Daniel Richards · Daniel Schutzsmith · Daniele Scasciafratte · darerodz · Daria · Darin Kotter · Darko G. · darkskipper · Darren Coutts · Dat Hoang · datainterlock · Dave Hilditch · dave1010 · David Anderson · David Baumwald · David Biňovec · David C · David Calhoun · David E. Smith · David Goring · David Gwyer · David Herrera · David Rozando · David Smith · David Vongries · daxelrod · daymobrew · Dean Sas · Deepak Vijayan · Denis de Bernardy · Denis Žoljom · denishua · Dennis Claassen · Dennis Snell · derekblank · Derrick Hammer · Dharmesh Patel · dhl · Diane Co · Dilip Bheda · dingdang · Dion Hulse · Dipak Parmar · divyeshgodhani · Dominik Schilling · donmhico · Doug Wollison · Dougal Campbell · Drew Jaynes · Drivingralle · drzraf · Dwain Maralack · Dzikri Aziz · Dōvy Paukstys · eclev91 · Edwin Cromley · eedee · Ehtisham S. · Eliezer Peña · Ella van Durpe · Emily Clarke · Emmanuel Hesry · Enrico Battocchi · Erick Hitter · Erik · Erik Betshammar · Estela Rueda · Eugene M · eugene.manuilov · Eugene.Manuilov · Evan Herman · Evan Mattson · Evan Mullins · Fabian Kägy · Faisal Alvi · Faison · Felipe Elia · Felix Arntz · Fellyph Cintra · Femy Praseeth · Florian Brinkmann · fpodhorsky · Francisco · franzaurus · Fuad Ragib · furi3r · gabri3lmarques · Gabriel de Tassigny · Gabriel Rose · gamecreature · Garrett Hyder · Garth Mortensen · Gary Jones · Gary Pendergast · garymatthews919 · George Hotelling · George Mamadashvili · George Stephanis · Gerardo Pacheco · gigitux · giox069 · gisgeo · giuseppemazzapica · Glen Davies · goldenapples · Grégory Viguier · graham73may · Grant M. Kinney · Greg Niedzielski · Greg Ziółkowski · gRegor Morrill · gunterer · Gustavo Bordoni · gvgvgvijayan · h2ham (Hiromu Hasegawa) · hakanca · hakre · Hans-Christiaan Braun · Hardik Thakkar · Harit Panchal · harshvaishnav · Hasanuzzaman · Hauwa Abashiya · Helen Hou-Sandi · Henrique Iamarino · Henry Wright · here · Herre Groen · Hilay Trivedi · hiren sanja · hiyascout · Howdy_McGee · hugodevos · huubl · hztyfoon · Héctor Prieto · Ian Belanger · Ian Dunn · iansvo · iCaspar · Ignacio Cruz Moreno · Igor · igrigorik · ilovecats7 · ilunabar · imadarshakshat · Innovext · ipajen · Ipstenu (Mika Epstein) · irecinius · Isabel Brison · Iulia Cazan · ivanjeronimo · iviweb · J.D. Grimes · Jacob Schweitzer · Jakaria Istauk · James · James Koster · jamesckemp · jamieburchell · Jan Thiel · Jarret · Jason Johnston · Jasper Kinoti · Javier Arce · Javier Carazo · Javier Casares · Jay Trees · jchambo · Jean-Baptiste Audras · jeawhanlee · Jeff Ong · Jeff Paul · Jeff Uberstine · Jeremy Felt · Jeremy Herve · JeroenReumkens · Jessica Lyschik · jhart35 · jhnstn · jigar bhanushali · jnz31 · Joe Dolson · Joe Hoyle · Joe McGill · joelhardi · joelmadigan · Joen Asmussen · John Blackbourn · John James Jacoby · John Regan · John Watkins · johnmark8080 · Jon Brown · Jon Surrell · Jonathan Bossenger · Jonathan Desrosiers · Jonathan Pantani · jonmackintosh · Jonny Harris · jonny-s · Jono Alderson · Joost de Valk · Jorge Costa · Jos Velasco · Joseph Grainger · Josepha Dambul · Josepha Haden · Josh Habdas · Joshua Abenazer · Joy · jrbeilke · jsh4 · jsnajdr · Juhi Saxena · Julie Moynat · Juliette Reinders Folmer · Julio Potier · just0nequestion · Justin Ahinon · Justin Sainton · Justin Tadlock · Justin Welenofsky · jyolsna · K. Adam White · kacper3355 · KafleG · Kai Hao · Kajal Gohel · Kalpesh Akabari · Kapil Paul · Kari Anderson · karlgroves · Karlijn Bok · Kaspars · Kathryn Presner · kbrownkd · Keanan Koppenhaver · Kelly Choyce-Dwan · Kelly Hoffman · Kevin Behrens · Kevin Hagerty · Khoi Pro · Khokan Sardar · killua99 · Kishan Jasani · kitchin · Kjell Reigstad · kkmuffme · klewis · Knut Sparhell · Koen Van den Wijngaert · Konrad.K · Konstantin Kovshenin · Konstantin Obenland · konyoldeath · Kris Kelvin · KrishaWeb · Krupal Panchal · Kunal Madhak · Kurt Payne · kwillmorth · Kyle B. Johnson · Kyle Nel · larsmqller · laurelfulford · Lauren Stein · laurent22777 · lazam786 · Lee Willis · leemon · Lena Morita · Leo Milo · leogermani · Linkon Miyan · Linnea Huxford · lonnylot · Lovekesh Kumar · Lovro Hrust · lozula · Lucas Bustamante · lucilastancato · luigipulcini · Luis Felipe Zaguini · luisherranz · Luiz Araújo · Lukas Niebler · Luke Cavanagh · M S Newaz · Maarten · Maciej · maciejmackowiak · Madhu Dollu · Madhu Dollu · Maggie Cabrera · Mahrokh · maksimkuzmin · malthert · manfcarlo · Manish Songirkar · Manzoor Wani · Manzur Ahammed · Marc · Marcelo de Moraes Serpa · Marco Ciampini · Marcus Kazmierczak · Marek Dědič · Marianna · Marie Comet · Marin Atanasov · Mario Santos · Marius L. J. · Mark Biek · Mark Howells-Mead · Mark Jaquith · Mark Parnell · Marko Heijnen · Markus · Markus Kosmal · Martijn van der Klis · Martin Stehle · martin.krcho · Mary Baum · Mashu · masteradhoc · Matías Emanuel Surdi · Matias Ventura · matiasbenedetto · Matt Chowning · Matt Keys · Matt Mullenweg · Matt Wondra · Matthew Boynes · Matthew Eppelsheimer · Matthias Pabst · Matthias Reinholz · mattyrob · Mauriac AZOUA · Maxime J. · Maxime Meganck · Mayank Majeji · maythamalsudany · Mayuge · mcliwanow · Md Rakib Hossain · Md. Russel Hussain · mdrago · Mehedi Foysal · Meher Bala · Mehul Kaklotar · Mel Choyce-Dwan · meloniq · Merkys Maliukevičius · meysam norouzi · Micha Krapp · Michael Bourne · Michael Burridge · Michal Czaplinski · Miguel Axcar · Miguel Fonseca · Mihai Dumitrascu · Mike Crantea · Mike Glendinning · Mike Hansen · Mike Jolley (a11n) · Mike Schroder · mikemanzo · Milana Cap · Milind More · mimi · Minal Diwan · miya · Mladen · Mohammad Jangda · MohammadJafar Khajeh · Mohit Dadhich · Monique Dubbelman · moto hachi · mreishus · mrobit · msolution · mtias · Muhammad Arslan · Mukesh Panchal · Muntasir Mahmud · Mustaque Ahmed · mvraghavan · mw108 · mweichert · n8finch · Nahid Hasan · Nalini Thakor · Namith Jawahar · Naresh Bheda · Nate Allen · Nathan · Nathan Johnson · navigatrum · neffff · nendeb · Neycho Kalaydzhiev · Nicholas Garofalo · Nick Diego · Nick Halsey · Nico · nidhidhandhukiya · Nik Tsekouras · nikkigagency · Niloy · Ninos · Nithin John · Nithin SreeRaj · nlpro · Noah Allen · noplanman · nouarah · NumidWasNotAvailable · nunomorgadinho · Nurul Umbhiya · nuvoPoint · nvartolomei · oakesjosh · Obayed Mamur · obliviousharmony · ockham · oguzkocer · Olga Gleckler · Oliver Stapelfeldt · OllieJones · oneearth27 · Onni Hakala · opr18 · ovidiul · p_enrique · Paal Joachim Romdahl · Pablo Postigo · PabloHoney · palmiak · Paolo L. Scala · Paragon Initiative Enterprises · Parham Ghaffarian · Pascal Birchler · Patrick Groot · Paul Bearne · Paul Biron · Paul Kevan · Paul Ryan · Paulo Cruz · Paulo Trentin · Pavan Patil · pavelschoffer · pbking · Pedro Mendonça · Peter Westwood · Peter Wilson · petitphp · Petter Walbø Johnsgård · Phil Johnston · Phill · Pierre Sylvestre · Pieterjan Deneys · Piotrek Boniu · Pippin Williamson · pkolenbr · Pooja Derashri · Pooja N Muchandikar · Praful Patel · Pratiksha · presscustomizr · Presskopp · presstoke · Priyo Mukul · prokium · pypwalters · Q · Rachel Baker · Rachel Peter · raduiason · Rafi Ahmed · Rahi Prajapati · Rajan Panchal · Rajesh Raval · ralucastn · Ramanan · Ramon Ahnert · Ramon Corrales · ramon fincken · Ramon James · Randhir Jha · Ravikumar Patel · rcanepa · rebasaurus · Rehan Ali · Remy Perona · Renatho (a11n) · renegeuze · Reuhno · rflw · Riad Benguella · Rich Tabor · Rinat · Rinky Chowdhury · Rishi Shah · rjasdfiii · rkaiser0324 · Robert Anderson · Robert Chapin · robertght · Robin · robmiller · rodricus · rodrigosevero · Rolf Allard van Hagen · Rolf Siebers · rollybueno · Romain Herault · romulodl · ross_ritchey · Roy · Russell Aaron · Ryan Boren · Ryan Kienstra · Ryan McCue · Ryan Murphy · Ryan Welcher · Sébastien SERRE · Sérgio Gomes · Sören Wrede · Sabbir Ahmed · Sajjad Hossain Sagor · Sakri Koskimies · Sami Keijonen · Sampat Viral · Samuel Wood (Otto) · Sandip Mondal - a11n · Sandra Sanz · Sarah Norris · sarahricker · Sathiyamoorthy V · Saumya Majumder · Saurabh Sharma · Scott Fennell · Scott Kingsley Clark · Scott Lesovic · Scott Taylor · scribu · Sean Fisher · Sebastian Pisula · seieric · Sergey Biryukov · Sergio Scabuzzo · seriouslysenpai · Seth Alling · shangidah afroz · Shannon Little · Sharjeel Khan · Shoaib Ali · Shraboni · Shreyas Ikhar · shuvo586 · siddharth ravikumar · Siddharth Thevaril · Siobhan · sirzooro · Slava Abakumov · Slobodan Manic · Smit Rathod · sobatkras · Stanislav Khromov · SteelWagstaff · Stefano · Stefano Minoia · Stefanos Togoulidis · stentibbing · Stephen Bernhardt · Stephen Edgar · Stephen Page · Sterling Hamilton · Steven Lin · steveo2000 · studiolxv · Subrata Sarkar · Sumit Bagthariya · Sumit Singh · Sumit Singh · Sumon Sarker · SunilPrajapati · sunyatasattva · Sybre Waaijer · Synchro · system909 · Tahmid ul Karim · Takashi Kitajima · Tammie Lister · Tanbir Ahmod · Tanvirul Haque · Taras Dashkevych · targz · Taylor Lovett · tazotodua · tbember · Teddy Patriarca · Tellyworth · Terence Eden · tharsheblows · thejaydip · Thierry Muller · Thijs · Thomas Griffin · Thorsten Schraut · threadi · Tiffany Bridge · Till Krüss · Timi Wahalahti · Timothy Jacobs · Titus Moore · TobiasBg · tobifjellner (Tor-Bjorn Fjellner) · Tom de Visser · Tom J Nowell · Tom Janssen · Tom Rhodes · Tomasz Tunik · tomepajk · Tomoki Shimomura · Toni Viemerö · tony.localword · Tonya Mork · Toro_Unit (Hiroshi Urabe) · Torsten Landsiedel · transl8or · Travis Smith · Tremi Dkhar · TrevorPolischuk · Trinadin · Tung Du · turtlepod · Ugyen Dorji · Ulrich · Umesh Gupta · upadalavipul · utsavmadaan823 · Vagelis · varma · vasartam · vdankbaar · Velochicdunord · Vicente Canales · vikasprogrammer · Virginie Garnier · Vishal Kakadiya · vortfu · vtad · Wang · webbeetle · WebMan Design | Oliver Juhas · Weston Ruter · whaze · Whissi · William Earnhardt · williampatton · withinboredom · woji29911 · Yahil Madakiya · Yan Knudtskov · Yann · Yoav Farhi · Yohann Billard · Yui · yuu · zaerl · Zebulan Stanphill · Zenaul Islam · ziposc · Česlav Przywara · 沈唁

WordPress 6.1 would not have been possible without the contributions of more than 800 people in over 60 countries. Their asynchronous coordination to deliver hundreds of enhancements and fixes into a stable release is a testament to the power and capability of the WordPress community.

By release day, 71 locales had translated 90-percent or more of WordPress 6.1 into their language. Community translators continue after a release ensuring more translations are on their way. Thank you to everyone who helps to make WordPress available in over 200 languages.

Many thanks to all of the community volunteers who contribute to the support forums by answering questions from WordPress users around the world.

If contributing to WordPress appeals to you, it’s easy to learn more and get involved. Discover the different teams that come together to Make WordPress and explore the product roadmap on the core development blog.

The WordPress Mission & You

WordPress is software designed for everyone, emphasizing accessibility, performance, security, and ease of use. The project believes great software should work with minimum setup, so you can focus on sharing your story, product, or services freely. The basic WordPress software is simple and predictable so you can easily get started. It also offers powerful features for growth and success.

WordPress believes in democratizing publishing and the freedoms that come with open source. Supporting this idea is a large community of people collaborating on and contributing to this project. The WordPress community is welcoming and inclusive. Our contributors’ passion drives the success of WordPress which, in turn, helps you reach your goals.

Learn more about WordPress and how you can join our community to help shape the future of the world’s most popular website platform.

Haiku Fun for 6.1

Another release,
Mark it down as completed.
Breathe, relax, and cheers!

This announcement was updated on Tue Nov 8 at 9:00 p.m. UTC to clarify some features in 6.1.

This RC3 release is the final opportunity for you to test and help to ensure the resilience of the 6.1 release by performing a final round of reviews and checks. Since the WordPress ecosystem is vast and composed of thousands of plugins and themes the entire project benefits from the time you take to assist.

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 is recommended that you test RC3 on a test server and site. 

You can test WordPress 6.1 RC3 in three ways:

Option 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).

Option 2: Direct download the RC3 version (zip).

Option 3: Use the WP-CLI command:

wp core update --version=6.1-RC3

Additional information on the 6.1 release cycle is available here.

Check the Make WordPress Core blog for 6.1-related developer notes in the coming weeks detailing all upcoming changes.

What’s in WordPress 6.1 RC3?

Since Release Candidate 2, approximately 60 items have been addressed. 

• GitHub tickets
• Trac tickets 

WordPress 6.1 is the third major release for 2022, following 5.9 and 6.0, released in January and May of this year, respectively.

To learn more about the highlights for both end-users and developers, you’re invited to read more about them in the RC1 announcement post and review the WordPress 6.1 Field Guide.

Plugin and theme developers

All plugin and theme developers should test their respective extensions against WordPress 6.1 RC3 and update the “Tested up to” version in their readme file to 6.1. If you find compatibility problems, please post detailed information to the support forums, so these items can be investigated further prior to the final release date of November 1st.

Translate WordPress

Do you speak a language other than English? Help translate WordPress into more than 100 languages. 

Keep WordPress bug-free – help with testing

Testing for issues is critical for stabilizing a release throughout its development. Testing is also a great way to contribute. This detailed guide is an excellent start if you have never tested a beta release.

Testing helps ensure that this and future releases of WordPress are as stable and issue-free as possible. Anyone can take part in testing – regardless of prior experience.

Want to know more about testing releases like this one? Read about the testing initiatives that happen in Make Core. You can also join a core-test channel on the Making WordPress Slack workspace.

If you have run into an issue, please report it to the Alpha/Beta area in the support forums. If you are comfortable writing a reproducible bug report, you can file one on WordPress Trac. This is also where you can find a list of known bugs.

To review features in the Gutenberg releases since WordPress 6.0 (the most recent major release of WordPress), access the What’s New In Gutenberg posts for 14.1, 14.0, 13.9, 13.8, 13.7, 13.6, 13.5, 13.4, 13.3, 13.2, and 13.1.

RC3, A Penultimate Haiku

The time ticks forward
Release nears ever closer
Download and review

Props to the following contributors for collaborating on this post: Dan Soschin, Jonny Harris

The second release candidate (RC2) for WordPress 6.1 is now available!

“Release Candidate” means that this version of WordPress is ready for release and it is a key milestone in the 6.1 release cycle! Before the official release date, the community sets aside time to perform final reviews and help test. Since the WordPress ecosystem includes thousands of plugins and themes, it is important that everyone checks to see if anything has been missed along the way. That means the project would greatly benefit from your assistance.

WordPress 6.1 is planned for official release on November 1st, 2022, two weeks from today. 

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 is recommended that you test RC2 on a test server and site. 

You can test WordPress 6.1 RC2 in three ways:

Option 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).

Option 2: Direct download the RC2 version (zip).

Option 3: Use the WP-CLI command:

wp core update --version=6.1-RC2

Additional information on the 6.1 release cycle is available here.

Check the Make WordPress Core blog for 6.1-related developer notes in the coming weeks detailing all upcoming changes.

What’s in WordPress 6.1 RC2?

Since Release Candidate 1, approximately 65 items have been addressed, bringing the total count to more than 2,000 updates since WordPress 6.0 in May of 2022. 

• GitHub tickets
• Trac tickets 

WordPress 6.1 is the third major release for 2022, following 5.9 and 6.0, released in January and May of this year, respectively.

To learn more about the highlights for both end-users and developers, you’re invited to read more about them in the RC1 announcement post and review the WordPress 6.1 Field Guide.

Plugin and theme developers

All plugin and theme developers should test their respective extensions against WordPress 6.1 RC2 and update the “Tested up to” version in their readme file to 6.1. If you find compatibility problems, please post detailed information to the support forums, so these items can be investigated further prior to the final release date of November 1st.

Translate WordPress

Do you speak a language other than English? Help translate WordPress into more than 100 languages. 

Keep WordPress bug-free – help with testing

Testing for issues is critical for stabilizing a release throughout its development. Testing is also a great way to contribute. This detailed guide is an excellent start if you have never tested a beta release.

Testing helps ensure that this and future releases of WordPress are as stable and issue-free as possible. Anyone can take part in testing – regardless of prior experience.

Want to know more about testing releases like this one? Read about the testing initiatives that happen in Make Core. You can also join a core-test channel on the Making WordPress Slack workspace.

If you have run into an issue, please report it to the Alpha/Beta area in the support forums. If you are comfortable writing a reproducible bug report, you can file one on WordPress Trac. This is also where you can find a list of known bugs.

To review features in the Gutenberg releases since WordPress 6.0 (the most recent major release of WordPress), access the What’s New In Gutenberg posts for 14.1, 14.0, 13.9, 13.8, 13.7, 13.6, 13.5, 13.4, 13.3, 13.2, and 13.1.

Haiku Fun for RC2

Two weeks from the launch 
Constant improvements we make 
Great outcomes await 

Update Oct 25 12:45 UTC: This post has been updated to remove the reference to Gutenberg versions 14.3 and 14.2 being included in the 6.1 release. They will be included in a future release.

This release features several security fixes. Because this is a security release, it is recommended that you update your sites immediately. All versions since WordPress 3.7 have also been updated.

WordPress 6.0.3 is a short-cycle release. The next major release will be version 6.1 planned for November 1, 2022.

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

You can download WordPress 6.0.3 from WordPress.org, or visit your WordPress Dashboard, click “Updates”, and then click “Update Now”.

For more information on this release, 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.

• Stored XSS via wp-mail.php (post by email) – Toshitsugu Yoneyama of Mitsui Bussan Secure Directions, Inc. via JPCERT
• Open redirect in `wp_nonce_ays` – devrayn
• Sender’s email address is exposed in wp-mail.php – Toshitsugu Yoneyama of Mitsui Bussan Secure Directions, Inc. via JPCERT
• Media Library – Reflected XSS via SQLi – Ben Bidner from the WordPress security team and Marc Montpas from Automattic independently discovered this issue
• CSRF in wp-trackback.php – Simon Scannell
• Stored XSS via the Customizer – Alex Concha from the WordPress security team
• Revert shared user instances introduced in 50790 – Alex Concha and Ben Bidner from the WordPress security team
• Stored XSS in WordPress Core via Comment Editing – Third-party security audit and Alex Concha from the WordPress security team
• Data exposure via the REST Terms/Tags Endpoint – Than Taintor
• Content from multipart emails leaked – Thomas Kräftner
• SQL Injection due to improper sanitization in `WP_Date_Query` – Michael Mazzolini
• RSS Widget: Stored XSS issue – Third-party security audit
• Stored XSS in the search block – Alex Concha of the WP Security team
• Feature Image Block: XSS issue – Third-party security audit
• RSS Block: Stored XSS issue – Third-party security audit
• Fix widget block XSS – Third-party security audit

Thank you to these WordPress contributors

This release was led by Alex Concha, Peter Wilson, Jb Audras, and Sergey Biryukov at mission control. Thanks to Jonathan Desrosiers, Jorge Costa, Bernie Reiter and Carlos Bravo for their help on package updates.

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

Alex Concha, Colin Stewart, Daniel Richards, David Baumwald, Dion Hulse, ehtis, Garth Mortensen, Jb Audras, John Blackbourn, John James Jacoby, Jonathan Desrosiers, Jorge Costa, Juliette Reinders Folmer, Linkon Miyan, martin.krcho, Matias Ventura, Mukesh Panchal, Paul Kevan, Peter Wilson, Robert AndersonRobin, Sergey Biryukov, Sumit Bagthariya, Teddy Patriarca, Timothy Jacobs, vortfu, and Česlav Przywara.

Thanks to @peterwilsoncc for proofreading.

This is an important milestone in the 6.1 release cycle. “Release Candidate” means that this version of WordPress is ready for release! Before the official release date, time is set aside for the community to perform final reviews and help test. Since the WordPress ecosystem includes thousands of plugins and themes, it is important that everyone checks to see if anything was missed along the way. That means the project would love your help.

WordPress 6.1 is planned for official release on November 1st, 2022, three weeks from today. 

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 is recommended that you test RC1 on a test server and site. 

You can test WordPress 6.1 RC1 in three ways:

Option 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).

Option 2: Direct download the RC1 version (zip).

Option 3: Use the following WP-CLI command:

wp core update --version=6.1-RC1

Additional information on the 6.1 release cycle is available here.

Check the Make WordPress Core blog for 6.1-related developer notes in the coming weeks detailing all upcoming changes.

What’s in WordPress 6.1 RC1?

Since Beta 3, approximately 100 items have been addressed, bringing the total count to more than 2,000 updates since WordPress 6.0 in May of 2022. 

• GitHub tickets
• Trac tickets 

WordPress 6.1 is the third major release for 2022, following 5.9 and 6.0, released in January and May of this year, respectively.

WordPress 6.1 highlights for end-users

• Default theme powered by 10 unique style variations (learn more)
• More design tools in more blocks (learn more)
• Expanded and refined template experience and template options
• More intuitive document settings experience
• Improved quote and list blocks with inner block support
• More robust placeholders for various blocks
• New modal interfaces and preferences improvements
• Automatic navigation block selection with fallbacks and easier menu management
• Apply locking settings to all inner blocks in one click
• Improvements to the block theme discovery experience
• Accessibility updates, with more than 60 resolved tickets
• Performance updates, with more than 25 resolved tickets

WordPress 6.1 highlights for developers

• Opt into appearance tools to make any theme more powerful
• New iteration on the style system
• Add starter patterns to any post type (learn more)
• Evolution of layout options including a new constrained option and the ability to disable layout options
• Content lock patterns for more curation options
• Expanded support for query loop blocks
• Allow the use of block-based template parts in classic themes (give feedback)
• Filter theme.json data (learn more)
• Fluid typography allows for more responsiveness (give feedback)
• Ability to style elements inside blocks like buttons, headings, or captions in theme.json

Please note that all features listed in this post are subject to change before the final release.

Plugin and theme developers

All plugin and theme developers should test their respective extensions against WordPress 6.1 RC1 and update the “Tested up to” version in their readme file to 6.1. If you find compatibility problems, please post detailed information to the support forums, so these items can be investigated further prior to the final release date of November 1st.

Translate WordPress

Do you speak a language other than English? Help translate WordPress into more than 100 languages. This release also marks the hard string freeze point of the 6.1 release cycle.

Keep WordPress bug-free – help with testing

Testing for issues is critical for stabilizing a release throughout its development. Testing is also a great way to contribute. This detailed guide is an excellent start if you have never tested a beta release.

Testing helps ensure that this and future releases of WordPress are as stable and issue-free as possible. Anyone can take part in testing – regardless of prior experience.

Want to know more about testing releases like this one? Read about the testing initiatives that happen in Make Core. You can also join a core-test channel on the Making WordPress Slack workspace.

If you have run into an issue, please report it to the Alpha/Beta area in the support forums. If you are comfortable writing a reproducible bug report, you can file one on WordPress Trac. This is also where you can find a list of known bugs.

To review features in the Gutenberg releases since WordPress 6.0 (the most recent major release of WordPress), access the What’s New In Gutenberg posts for 14.1, 14.0, 13.9, 13.8, 13.7, 13.6, 13.5, 13.4, 13.3, 13.2, and 13.1.

Haiku Fun for RC1

Languages abound
Test today, releases soon
Freedom to publish

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

WordPress 6.1 Beta 3 is now available 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 is recommended that you test Beta 3 on a test server and site. 

You can test WordPress 6.1 Beta 3 in three ways:

Option 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).

Option 2: Direct download the Beta 3 version (zip).

Option 3: Use the following WP-CLI command:

wp core update --version=6.1-beta3

The current target for the final release is November 1, 2022, which is about four weeks away. 

Additional information on the 6.1 release cycle is available.

Check the Make WordPress Core blog for 6.1-related developer notes in the coming weeks detailing all upcoming changes.

Keep WordPress bug-free – help with testing

Testing for issues is critical for stabilizing a release throughout its development. Testing is also a great way to contribute. This detailed guide is an excellent start if you have never tested a beta release before.

Testing helps ensure that this and future releases of WordPress are as stable and issue-free as possible. Anyone can take part in testing – especially great WordPress community members like you.

Want to know more about testing releases like this one? Read about the testing initiatives that happen in Make Core. You can also join a core-test channel on the Making WordPress Slack workspace.

If you have run into an issue, please report it to the Alpha/Beta area in the support forums. If you are comfortable writing a reproducible bug report, you can file one on WordPress Trac. This is also where you can find a list of known bugs.

To review features in the Gutenberg releases since WordPress 6.0 (the most recent major release of WordPress), access the What’s New In Gutenberg posts for 14.1, 14.0, 13.9, 13.8, 13.7, 13.6, 13.5, 13.4, 13.3, 13.2, and 13.1.

This release contains more than 350 enhancements and 350 bug fixes for the editor, including more than 300 tickets for WordPress 6.1 core. More fixes are on the way in the remainder of the 6.1 release cycle.

Some highlights

Want to know what’s new in version 6.1? Read the initial Beta 1 announcement for some details, or check out the product walk-through recording.

What’s new in Beta 3

Nearly 100 issues have been resolved since Beta 2 was released last week.

• Github tickets
• Trac tickets (may include some overlap with Github)

A Beta 3 haiku for thee

Beta time done soon
Gather up your WordPress sites
RC then we ship

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

You can test WordPress 6.1 Beta 2 in three ways:

Option 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).

Option 2: Direct download the Beta 2 version (zip).

Option 3: Use the following WP-CLI command:

wp core update --version=6.1-beta2

The current target for the final release is November 1, 2022, which is about five weeks away. 

Additional information on the 6.1 release cycle is available.

Check the Make WordPress Core blog for 6.1-related developer notes in the coming weeks detailing all upcoming changes.

Keep WordPress bug-free – help with testing

Testing for issues is critical for stabilizing a release throughout its development. Testing is also a great way to contribute. This detailed guide is an excellent start if you have never tested a beta release before.

Testing helps ensure that this and future releases of WordPress are as stable and issue-free as possible. Anyone can take part in testing – especially great WordPress community members like you.

Want to know more about testing releases like this one? Read about the testing initiatives that happen in Make Core. You can also join a core-test channel on the Making WordPress Slack workspace.

If you have run into an issue, please report it to the Alpha/Beta area in the support forums. If you are comfortable writing a reproducible bug report, you can file one on WordPress Trac. This is also where you can find a list of known bugs.

To review features in the Gutenberg releases since WordPress 6.0 (the most recent major release of WordPress), access the What’s New In Gutenberg posts for 14.1, 14.0, 13.9, 13.8, 13.7, 13.6, 13.5, 13.4, 13.3, 13.2, and 13.1.

This release contains more than 350 enhancements and 350 bug fixes for the editor, including more than 300 tickets for WordPress 6.1 core. More fixes are on the way in the remainder of the 6.1 release cycle.

Some highlights

Want to know what’s new in version 6.1? Read the initial Beta 1 announcement for some details, or check out the product walk-through recording.

What’s new in Beta 2

Here are some updates since last week’s Beta 1 release:

• 24 issues addressed in GitHub

A haiku for Beta 2

WordPress six-point-one,
Please help test Beta 2 now.
Best release ever.

Thank you to the following contributors for collaborating on this post: @dansoschin, @robinwpdeveloper, @webcommsat, @jeffpaul, and @cbringmann.

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 is recommended that you test Beta 1 on a test server and site. 

You can test WordPress 6.1 Beta 1 in three ways:

Option 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).

Option 2: Direct download the Beta 1 version (zip).

Option 3: Use the following WP-CLI command:

wp core update --version=6.1-beta1

The current target for the final release is November 1, 2022, which is about six weeks away. 

Additional information on the 6.1 release cycle is available.

Check the Make WordPress Core blog for 6.1-related developer notes in the coming weeks detailing all upcoming changes.

Keep WordPress bug-free – help with testing

Testing for issues is critical for stabilizing a release throughout its development. Testing is also a great way to contribute. If you have never tested a beta release before, this detailed guide is a great start.

Testing helps make sure that this and future releases of WordPress are as stable and issue-free as possible. Anyone can do it – especially great WordPress community members like you.

Want to know more about testing releases like this one? Read about the testing initiatives that happen in Make Core. You can also join a publicly-accessible channel on the Making WordPress Slack workspace.

If you think you have run into an issue, please report it to the Alpha/Beta area in the support forums. If you are comfortable writing a reproducible bug report, you can file one on WordPress Trac. This is also where you can find a list of known bugs.

To review features in the Gutenberg releases since WordPress 6.0 (the most recent major release of WordPress), access the What’s New In Gutenberg posts for 14.1, 14.0, 13.9, 13.8, 13.7, 13.6, 13.5, 13.4, 13.3, 13.2, and 13.1.

This release contains more than 350 enhancements and 350 bug fixes for the editor, including more than 250 tickets for the WordPress 6.1 core.

Some highlights

Want to know what’s new in WordPress version 6.1? Read on for some highlights.

Features for end-users

• Default theme powered by 10 unique style variations (learn more)
• More design tools in more blocks (learn more)
• Expanded and refined template experience and template options
• More intuitive document settings experience
• Header and footer patterns for all themes
• Improved quote and list blocks with inner block support
• More robust placeholders for various blocks
• New modal interfaces and preferences improvements
• Automatic navigation block selection with fallbacks and easier menu management
• Apply locking settings to all inner blocks in one click
• Improvements to the block theme discovery experience
• Accessibility updates, with more than 60 resolved tickets
• Performance updates, with more than 25 resolved tickets

For developers

• Opt into appearance tools to make any theme more powerful
• New iteration on the style system
• Add starter patterns to any post type (learn more)
• Evolution of layout options including a new constrained option and the ability to disable layout options
• Content lock patterns for more curation options
• Expanded support for query loop blocks
• Allow the use of block-based template parts in classic themes (give feedback)
• Filter theme.json data (learn more)
• Fluid typography allows for more responsiveness (give feedback)
• Ability to style elements inside blocks like buttons, headings, or captions in theme.json

Please note that all features listed in this post are subject to change before the final release.

A Haiku for you

Twenty Twenty-Three
10 style variations
The new default theme

Thank you to the following contributors for collaborating on this post: @dansoschin, @annezazu, @cbringmann, @davidbaumwald, @priethor, and @jeffpaul.

This security and maintenance release features 12 bug fixes on Core, 5 bug fixes for the Block Editor, and 3 security fixes. Because this is a security release, it is recommended that you update your sites immediately. All versions since WordPress 3.7 have also been updated.

WordPress 6.0.2 is a short-cycle release. You can review a summary of the main updates in this release by reading the RC1 announcement.

The next major release will be version 6.1 planned for November 1, 2022.

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

You can download WordPress 6.0.2 from WordPress.org, or visit your WordPress Dashboard, click “Updates”, and then click “Update Now”.

For more information on this release, 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:

• Fariskhi Vidyan for finding a possible SQL injection within the Link API.
• Khalilov Moe for finding an XSS vulnerability on the Plugins screen.
• John Blackbourn of the WordPress security team, for finding an output escaping issue within the_meta().

Thank you to these WordPress contributors

The WordPress 6.0.2 release was led by @sergeybiryukov and @gziolo.

WordPress 6.0.2 would not have been possible without the contributions of more than 50 people. Their asynchronous coordination to deliver several enhancements and fixes into a stable release is a testament to the power and capability of the WordPress community.

Alex Concha, Andrei Draganescu, annezazu, Anton Vlasenko, Ari Stathopoulos, Ben Dwyer, Carolina Nymark, Colin Stewart, Darren Coutts, Dilip Bheda, Dion Hulse, eMKey, Fabian Kägy, George Mamadashvili, Greg Ziółkowski, huubl, ironprogrammer, Jb Audras, John Blackbourn, Jonathan Desrosiers, jonmackintosh, Jonny Harris, Kelly Choyce-Dwan, Lena Morita, Linkon Miyan, Lovro Hrust, marybaum, Nick Diego, Nik Tsekouras, Olga Gleckler, Pascal Birchler, paulkevan, Peter Wilson, Sergey Biryukov, Stephen Bernhardt, Teddy Patriarca, Timothy Jacobs, tommusrhodus, Tomoki Shimomura, Tonya Mork, webcommsat AbhaNonStopNewsUK, and zieladam.