WordPress.org News

Minimum PHP Version update

WordPress 5.2 is targeted for release at the end of this month, and with it comes an update to the minimum required version of PHP. WordPress will now require a minimum of PHP 5.6.20. Beginning in WordPress 5.1, users running PHP versions below 5.6 have had a notification in their dashboard that includes information to help them update PHP. Since then, the WordPress stats have shown an increase in users on more recent versions of PHP. The dashboard widget users see if running an outdated version of PHP Why You Should Update PHP If your site is running on an unsupported version of PHP, the WordPress updater will not offer WordPress 5.2 to your site. If you attempt to update WordPress manually, that update will fail. To continue using the latest features of WordPress you must update to a newer version of PHP. When updating to a new version of PHP, WordPress encourages updating to its recommended version, PHP 7.3. The PHP internals team has done a great job making its most recent version the fastest version of PHP yet. This means that updating will improve the speed of your site, both for you and your visitors. This performance increase also means fewer servers are needed to host websites. Updating PHP isn’t just good for your site, it also means less energy is needed for the 1-in-3 sites that use WordPress, so it’s good for the planet. How to Update PHP If you need help updating to a new version of PHP, detailed documentation is available. This includes sample communication to send to your host for them to assist you. Many hosting companies have published information on how to update PHP that is specific for them. 5.6 now, but soon 7+ This is the first increase in PHP required version for WordPress since 2010, but may not be the only increase in 2019. The WordPress core team will monitor the adoption of the most recent versions of PHP with an eye towards making PHP 7+ the minimum version towards the end of the year. Update PHP today, so you can update WordPress tomorrow!

The Month in WordPress: March 2019

WordPress reached a significant milestone this month. With some exciting developments in Core, an interesting new proposal, and the return of a valuable global event, March was certainly an interesting time. WordPress Now Powers One-Third of the Web WordPress’ market share has been steadily increasing, and as of halfway through this month, it powers over one-third of the top 10 million sites on the web (according to W3Techs, which tracks usage statistics for all major web platforms). This growth of WordPress is only made possible by the large team of volunteers working to build the project and community. If you would like to get involved in building the future of WordPress, then check out the Make network for a contributor team that fits your skill set. WordPress 5.2 is on the Way WordPress 5.1.1 was released this month, with 14 fixes and enhancements, and the Core team is now focusing on the next major release, version 5.2. This release will include some great new features, along with the latest updates to the block editor. One of the most anticipated new features is the improved fatal error detection – this was removed from v5.1 shortly before release so that it could be improved and made more secure for this release. Along with that, PHP 5.6 is going to become the minimum required PHP version for WordPress, a significant step towards a more modern web and updated coding standards. WordPress 5.2 is now in beta and you can test it by installing the Beta Tester plugin on any WordPress site. Want to get involved in building WordPress Core? Follow the Core team blog and join the #core channel in the Making WordPress Slack group. Proposal for a Central Block Directory With blocks becoming the new way to manage content in WordPress, more and more types of blocks are being developed to cater for different use cases and content types. In an effort to make it easier for content creators to find these block types, there is a proposal for a new type of plugin and a directory to handle it. The proposal outlines a new type of WordPress plugin that provides blocks and nothing else, named Single Block Plugins. The primary benefit would be to provide content creators with individual pieces of functionality and new types of blocks without the need to search for and install new plugins. The Single Block Plugins would be hosted in a separate Block Directory section of the Plugin Directory and they would initially be JavaScript-based. Each plugin will register a single block, and they will be searchable and installable from within the editor itself. This puts blocks at the publishers’ fingertips — you no longer have to leave the editor to find them. Want to get involved in shaping this new type of plugin? Join in the conversation on the proposal post, follow the Meta team blog, and join the #meta channel in the Making WordPress Slack group. Global WordPress Translation Day is Back On 11 May 2019, the fourth Global WordPress Translation Day will take place. This is a 24-hour global event dedicated to the translation of all things WordPress, from core to themes, plugins to marketing. Over the course of 24 hours, WordPress communities will meet to translate WordPress into their local languages and watch talks and sessions broadcast on wptranslationday.org. During the last Global WordPress Translation Day, 71 local events took place in 29 countries, and even more communities are expected to take part this time. Want to get involved in the Global WordPress Translation Day? Find out how to organize a local event, apply to be a speaker, follow the updates on the Polyglots team blog, and join the #polyglots channel in the Making WordPress Slack group. Gutenberg Development Continues With the block editor in WordPress Core, the team has been able to focus on adding some frequently requested features. Version 5.3 of Gutenberg,  released this month, includes a new block manager modal, the ability to nest different elements in the cover block, and some UI tweaks to improve the hover state of blocks. Want to get involved in developing Gutenberg? Check out the GitHub repository and join the #core-editor channel in the Making WordPress Slack group. Further Reading: The PHP upgrade notice in WordPress 5.1 has already had a hugely positive effect on thousands of websites.The Theme Review Team has released their useful Theme Sniffer plugin on the Plugin Directory to help theme developers build more standards-compliant themes.The Polyglots team has started a discussion about the best way to localize WordPress user documentation.The schedule for WordCamp Europe 2019 has been published – the event takes place on June 20-22.A new `wp_body_open` hook has been added to Core in version 5.2, providing more power and flexibility for theme developers.The dates and location of WordCamp for Publishers 2019 have been announced.In a milestone achievement for inclusivity, more than 50% of all speakers at WordCamp Miami were women. Have a story that we should include in the next “Month in WordPress” post? Please submit it here.

WordPress 5.2 Beta 1

WordPress 5.2 Beta 1 is now available! This software is still in development, so we don’t recommend you run it on a production site. Consider setting up a test site to play with the new version. You can test the WordPress 5.2 Beta two ways: Try the WordPress Beta Tester plugin (choose the “bleeding edge nightlies” option)Or download the beta here (zip). WordPress 5.2 is slated for release on April 30, and we need your help to get there. Here are some of the big items to test so we can find as many bugs as possible in the coming weeks. Block Editor The block editor has received significant performance improvements since WordPress 5.1, shaving 35% off the load time for massive posts, and cutting the keypress time (how responsive it feels when you’re typing) in half! Accessibility continues to improve, too. The block editor now supports your browser’s reduced motion settings. The post URL slug has better labelling and help text. The focus styling for keyboard navigating through landmarks is clearer and more consistent. There are a variety of new speak messages, and existing messages have been tweaked for more useful screen-reader behaviour. We’ve added several new blocks: An RSS blockAn Amazon Kindle embed blockA Search blockA Calendar blockA Tag Cloud block To help you keep track of these blocks, and only show the ones you need, there’s a new block management tool to switch blocks on and off. Block Management Modal We’re constantly working on existing blocks, too. There are hundreds of bug fixes and improvements in the block editor, you can read more about them in the Gutenberg plugin releases: 4.9, 5.0, 5.1, 5.2, and 5.3. The WordPress Mobile Apps The block editor isn’t just for websites, either. The WordPress mobile apps now include an experimental version of a built-in block editor. This is still under development, but you can try it out now! The block editor is coming to the mobile apps Site Health Check Site Health Check is an ongoing project aimed at improving the stability and performance of the entire WordPress ecosystem. The first phase of this project (originally scoped for WordPress 5.1) is now included in WordPress 5.2. For the first time, WordPress will catch and pause the problem code, so you can log in to your Dashboard and see what the problem is (#44458). Before, you’d have to FTP in to your files or get in touch with your host. The Improved Fatal Error Protection In addition, we’re adding a new Health Check tool to your Dashboard. Visit the Tools menu and click on Health Check to get information that can help improve the speed and security of your site. PHP Version Bump With this release, WordPress will increase its minimum supported PHP version to 5.6. To help you check if you’re prepared for this change, WordPress 5.2 will show you a warning and help you upgrade your version of PHP, if necessary. For Developers Plugins can now specify the minimum version of PHP that they support, so you can safely modernise your development practices without risking breaking your users’ sites. (#40934)We’ve added the sodium_compat library, which provides backwards compatibility for the Sodium-based cryptography library added in PHP 7.2. (#45806)There’s a new release of Dashicons, the WordPress Dashboard icon font. There are 25 new icons for you to use! (#41074)You can now pass a label to get_search_form(), improving accessibility. (#42057) There have been 130 tickets closed in WordPress 5.2 so far, with numerous small bug fixes and improvements to help smooth your WordPress experience. Keep your eyes on the Make WordPress Core blog for developer notes (which are assigned the dev-notes tag) in the coming weeks detailing other changes in 5.2 that you should be aware of. How to Help Do you speak a language other than English? Help us translate WordPress into more than 100 languages! If you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report, file one on WordPress Trac, where you can also find a list of known bugs. With each new release,bearing multiple betas; We fix, then we fly.

One-third of the web!

WordPress now powers over 1/3rd of the top 10 million sites on the web according to W3Techs. Our market share has been growing steadily over the last few years, going from 29.9% just one year ago to 33.4% now. We are, of course, quite proud of these numbers! The path here has been very exciting. In 2005, we were celebrating 50,000 downloads. Six years later, in January 2011, WordPress was powering 13.1% of websites. And now, early in 2019, we are powering 33.4% of sites. Our latest release has already been downloaded close to 14 million times, and it was only released on the 21st of February. WordPress market share on the rise over the last 8 years. Image source: W3Techs. Over the years WordPress has become the CMS of choice for more and more people and companies. As various businesses use WordPress, the variety of WordPress sites grows. Large enterprise businesses all the way down to small local businesses: all of them use WordPress to power their site. We love seeing that and we strive to continuously make WordPress better for all of you. We’d like to thank everyone who works on WordPress, which is built and maintained by a huge community of volunteers that has grown alongside the CMS. This incredible community makes it possible for WordPress to keep growing while still also remaining free. And of course, we’d like to thank all of you using WordPress for using it and trusting in it. To all of you: let’s celebrate!

WordPress 5.1.1 Security and Maintenance Release

WordPress 5.1.1 is now available! This security and maintenance release introduces 10 fixes and enhancements, including changes designed to help hosts prepare users for the minimum PHP version bump coming in 5.2. This release also includes a pair of security fixes that handle how comments are filtered and then stored in the database. With a maliciously crafted comment, a WordPress post was vulnerable to cross-site scripting. WordPress versions 5.1 and earlier are affected by these bugs, which are fixed in version 5.1.1. Updated versions of WordPress 5.0 and earlier are also available for any users who have not yet updated to 5.1. Props to Simon Scannell of RIPS Technologies who discovered this flaw independent of some work that was being done by members of the core security team. Thank you to all of the reporters for privately disclosing the vulnerabilities, which gave us time to fix them before WordPress sites could be attacked. Other highlights of this release include: Hosts can now offer a button for their users to update PHP.The recommended PHP version used by the “Update PHP” notice can now be filtered.Several minor bug fixes. You can browse the full list of changes on Trac. WordPress 5.1.1 was a short-cycle maintenance release. Version 5.1.2 is expected to follow a similar two week release cadence. You can download WordPress 5.1.1 or visit Dashboard → Updates and click Update Now. Sites that support automatic background updates have already started to update automatically. In addition to the security researcher mentioned above, thank you to everyone who contributed to WordPress 5.1.1: Aaron Jorbin, Alex Concha, Andrea Fercia, Andy Fragen, Anton Vanyukov, Ben Bidner, bulletdigital, David Binovec, Dion Hulse, Felix Arntz, Garrett Hyder, Gary Pendergast, Ian Dunn, Jake Spurlock, Jb Audras, Jeremy Felt, Johan Falk, Jonathan Desrosiers, Luke Carbis, Mike Schroder, Milan Dinić, Mukesh Panchal, Paul Biron, Peter Wilson, Sergey Biryukov, and Weston Ruter.

The Month in WordPress: February 2019

A new version of WordPress, significant security enhancements, important discussions, and much more – read on to find out what has been going on in the WordPress community for the month of February. Release of WordPress 5.1 Near the end of the month, WordPress 5.1 was released, featuring significant stability and performance enhancements as well as the first of the Site Health mechanisms that are in active development. Most prominent is the new warning for sites running long-outdated versions of PHP. You can check out the Field Guide for this release for a detailed look at all the new features and improvements. The next release is already in development with plans to improve the Site Health features, PHP compatibility, and a number of other things. Want to get involved in testing or building WordPress Core? You can install the WordPress Beta Tester plugin, follow the Core team blog, and join the #core channel in the Making WordPress Slack group. Gutenberg Development Continues The block editor that is now a part of WordPress core started out as a project named Gutenberg with the lofty goal of creating a whole new site-building experience for all WordPress users. The first phase of Gutenberg resulted in the block editor that was included in WordPress 5.0, but development didn’t stop there – phase 2 of the project is well underway. This month, one of the initial goals for this phase was reached with all of the core WordPress widgets being converted to blocks – this will go a long way to allowing full sites to be built using blocks, rather than simply post or page content. Want to get involved in developing Gutenberg? Check out the GitHub repository and join the #core-editor channel in the Making WordPress Slack group. Block Editor Comes to the Mobile Apps As Gutenberg development continues, the Mobile team has been working hard to integrate the new block editor into the WordPress mobile apps. Near the end of February, the team shipped a complete integration in the beta versions of the apps – this a significant milestone and a big step towards unifying the mobile and desktop editing experiences. Both the iOS and Android apps are open for beta testers, so if you would like to experience the block editor on mobile today, then join the beta program. Want to get involved in developing the WordPress mobile apps? Follow the Mobile team blog, and join the #mobile channel in the Making WordPress Slack group. WordPress Triage Team Announced One of the goals for 2019 that Matt Mullenweg (@matt) announced in his State of the Word address last year was to form a team who would work to manage the ever-increasing number of tickets in Trac, the bug tracker that WordPress Core employs. This team, known as the Triage Team, has been announced. Their work will involve coordinating with component maintainers, release leads, project leadership, contributors, and other WordPress related projects with issue trackers outside of Trac to ensure that everyone is empowered to focus on contributing. The team was formed based on nominations of volunteers to take part and will be led by Jonathan Desrosiers (@desrosj). The other members of the team are Chris Christoff (@chriscct7), Tammie Lister (@karmatosed), Sergey Biryukov (@sergey), and Sheri Bigelow (@designsimply) – all of whom have a strong track record of contributing to WordPress, have exhibited good triaging practices, and are overall good community members. Further Reading: In this year alone, the WordPress meetup program has hosted 800 events across the world, all organized by local community members.An important discussion has been opened regarding the future of the WordPress Community Summit.The Polyglots team has started planning the fourth Global WordPress Translation Day to take place on 11 May 2019.The Theme Review team is working on a useful tool named Theme Sniffer to assist theme developers and reviewers in making sure their code is standards-compliant.The first WordCamp Nordic is coming up on March 7-8.The WordCamp Europe team is looking for feedback on their designs for a Progressive Web Application (PWA) for WordCamp.org.The Design team has been working hard on designing the new Navigation Menu block and are looking for feedback. Have a story that we should include in the next “Month in WordPress” post? Please submit it here.

WordPress 5.1 “Betty”

A Little Better Every Day Version 5.1 of WordPress, named “Betty” in honour of acclaimed jazz vocalist Betty Carter, is available for download or update in your WordPress dashboard. Following WordPress 5.0 — a major release which introduced the new block editor — 5.1 focuses on polish, in particular by improving the overall performance of the editor. In addition, this release paves the way for a better, faster, and more secure WordPress with some essential tools for site administrators and developers. Site Health With security and speed in mind, this release introduces WordPress’s first Site Health features. WordPress will start showing notices to administrators of sites that run long-outdated versions of PHP, which is the programming language that powers WordPress. When you install new plugins, WordPress’s Site Health features will check them against the version of PHP you’re running. If the plugin requires a version that won’t work with your site, WordPress will keep you from installing that plugin. Editor Performance Introduced in WordPress 5.0, the new block editor continues to improve. Most significantly, WordPress 5.1 includes solid performance improvements within the editor. The editor should feel a little quicker to start, and typing should feel smoother. Expect more performance improvements in the next couple of releases. Developer Happiness Multisite Metadata 5.1 introduces a new database table to store metadata associated with sites and allows for the storage of arbitrary site data relevant in a multisite / network context. Cron API The Cron API has been updated with new functions to assist with returning data and includes new filters for modifying cron storage. Other changes in behavior affect cron spawning on servers running FastCGI and PHP-FPM versions 7.0.16 and above. New JS Build Processes WordPress 5.1 features a new JavaScript build option, following the large reorganisation of code that started in the 5.0 release. Other Developer Goodness Miscellaneous improvements include: Updates to values for the WP_DEBUG_LOG constantNew test config file constant in the test suite, new plugin action hooks Short-circuit filters for wp_unique_post_slug(), WP_User_Query, and count_users()A new human_readable_duration functionImproved taxonomy metabox sanitizationLimited LIKE support for meta keys when using WP_Meta_QueryA new “doing it wrong” notice when registering REST API endpoints …and more! The Squad This release was led by Matt Mullenweg, along with Gary Pendergast as Senior Code Reshuffler and Poet. They received wonderful assistance from the following 561 contributors for this release, 231 of whom were making their first ever contribution! Pull up some Betty Carter on your music service of choice, and check out some of their profiles: 0x6f0, 1265578519, 1naveengiri, 360zen, aardrian, Aaron Jorbin, Abdullah Ramzan, Abhay Vishwakarma, Abhijit Rakas, Achal Jain, achbed, Adam Silverstein, Ajit Bohra, Alain Schlesser, aldavigdis, alejandroxlopez, Alex, Alex Shiels, Alexander Botteram, Alexandru Vornicescu, alexgso, All, allancole, Allen Snook, Alvaro Gois dos Santos, Ana Cirujano, Anantajit JG, Andrés, Andrea Fercia, Andrea Gandino, Andrea Middleton, andrei0x309, andreiglingeanu, Andrew Duthie, Andrew Lima, Andrew Nacin, Andrew Nevins, Andrew Ozz, Andrey Savchenko, Andy Fragen, Andy Meerwaldt, Angelika Reisiger, Antal Tettinger, antipole, Anton Timmermans, Antonio Villegas, antonioeatgoat, Anwer AR, Arun, Ashar Irfan, ashokrd2013, Ayesh Karunaratne, Ayub Adiputra, Barry Ceelen, Behzod Saidov, benhuberman, Benoit Chantre, benvaassen, Bhargav Mehta, bikecrazyy, Birgir Erlendsson, BjornW, Blair jersyer, blob, Blobfolio, bobbingwide, boblinthorst, Boone Gorges, Boro Sitnikovski, Brad Parbs, Bradley, bramheijmink, Brandon Kraft, Brandon Payton, Brent Swisher, Brian Richards, bridgetwillard, Brooke., bruceallen, Burhan Nasir, Bytes.co, Caleb Burks, Calin Don, campusboy, carolinegeven, ccismaru, chasewg, Chetan Prajapati, Chouby, ChriCo, chriscct7, Christopher Spires, claudiu, Clifford Paulick, Code Clinic, codegrau, coleh, conner_bw, Corey McKrill, croce, Csaba (LittleBigThings), Cyrus Collier, Daniel Bachhuber, Daniel James, Daniel Koskinen, Daniel Richards, Daniele Scasciafratte, danimalbrown, Danny Cooper, Danny de Haan, Darko A7, Darren Ethier (nerrad), Dave Pullig, David A. Kennedy, David Anderson, David Binovec, David Cramer, David Herrera, David Lingren, David Shanske, David Stone, dekervit, Denis Yanchevskiy, Dennis Snell, designsimply, dfangstrom, Dhanendran, Dharmesh Patel, Dhaval kasavala, Dhruvin, DiedeExterkate, Dilip Bheda, dingo_d, Dion Hulse, dipeshkakadiya, Dominik Schilling, Donncha O Caoimh, dontstealmyfish, Drew Jaynes, Drivingralle, drywallbmb, dschalk, dsifford, eamax, eArtboard, edo888, edocev, ElectricFeet, Ella Van Durpe, Eric Andrew Lewis, Eric Daams, Erich Munz, Erick Hitter, ericmeyer, etoledom, Evan Solomon, Evangelos Athanasiadis, ever, everyone, Faisal Alvi, Felipe Elia, Felix Arntz, Fernando Claussen, flipkeijzer, Florian TIAR, folio, FPCSJames, Frank Klein, frOM, fuchsws, fullyint, Gabriel Maldonado, Gareth, Garrett Hyder, Gary Jones, Gennady Kovshenin, Gerhard Potgieter, Girish Panchal, GM_Alex, gnif, graymouser, greg, Grzegorz (Greg) Ziółkowski, Guido, GutenDev, Hafiz Rahman, Hai@LiteSpeed, Hans-Christiaan Braun, Hardeep Asrani, Hardik Amipara, Harsh Patel, haruharuharuby, Heather Burns, Helen Hou-Sandi, Henry Wright, Herre Groen, hitendra, Hitendra Chopda, Ian Belanger, Ian Dunn, ibantxillo, Ignacio Cruz Moreno, Igor, Igor Benic, imath, ionvv, Irene Strikkers, isabel104, ishitaka, Ivan Mudrik, J.D. Grimes, Jack Reichert, Jacob Peattie, James Nylen, janak Kaneriya, janalwin, Janki Moradiya, janthiel, Jason Caldwell, javorszky, Jaydip Rami, Jayman Pandya, Jb Audras, Jeff Farthing, Jeffrey de Wit, Jeffrey Paul, Jennifer M. Dodd, Jenny, Jeremey, Jeremy Felt, Jeremy Herve, Jeremy Pry, Jeremy Scott, Jesper V Nielsen, Jesse Friedman, Jimmy Comack, Jip Moors, Jiri Hon, JJJ, joanrho, Job, Joe Bailey-Roberts, Joe Dolson, Joe Hoyle, Joe McGill, Joel James, Joen Asmussen, John Blackbourn, John Godley, johnalarcon, johnpgreen, johnschulz, Jonathan Champ, Jonathan Desrosiers, joneiseman, Jonny Harris, Joost de Valk, Jorge Costa, Joseph Scott, JoshuaWold, Joy, jpurdy647, jrdelarosa, jryancard, Juhi Patel, Julia Amosova, juliemoynat, Juliette Reinders Folmer, Junaid Ahmed, Justin Sainton, Justin Sternberg, Justin Tadlock, K.Adam White, kapteinbluf, keesiemeijer, Kelly Dwan, kelvink, khaihong, Kiran Potphode, Kite, kjellr, kkarpieszuk, kmeze, Knut Sparhell, konainm, Konstantin Obenland, Konstantinos Xenos, kristastevens, krutidugade, laghee, Laken Hafner, Lance Willett, laurelfulford, lbenicio, Leander Iversen, leemon, lenasterg, lisannekluitmans, lizkarkoski, Luca Grandicelli, LucasRolff, luciano, Luminus, Mário Valney, maartenleenders, macbookandrew, Maja Benke, Mako, mallorydxw-old, Manuel Augustin, manuel_84, Marc Nilius, marcelo2605, Marco Martins, marco.marsala, Marcus Kazmierczak, marcwieland95, Marius L. J., mariusvw, Mariyan Belchev, Mark Jaquith, Mathieu Sarrasin, mathieuhays, Matt Cromwell, Matt Gibbs, Matt Martz, Matthew Boynes, Matthew Riley MacPherson, mattyrob, mcmwebsol, Mel Choyce, mensmaximus, mermel, metalandcoffee, Micah Wood, Michael Nelson, Michiel Heijmans, Migrated to @sebastienserre, Miguel Fonseca, Miguel Torres, mihaiiceyro, mihdan, Mike Gillihan, Mike Jolley, Mike Schroder, Milan Dinić, Milan Ivanovic, Milana Cap, Milind More, mirkoschubert, Monika Rao, Monique Dubbelman, moto hachi ( mt8.biz ), mrmadhat, Muhammad Kashif, Mukesh Panchal, MultiformeIngegno, Muntasir Mahmud, munyagu, MyThemeShop, mzorz, nadim0988, nandorsky, Naoki Ohashi, Naoko Takano, nataliashitova, Nate Allen, Nathan Johnson, ndavison, Ned Zimmerman, Nextendweb, Nick Diego, Nick Halsey, Nick Momrik, Nick the Geek, Nicolas Figueira, Nicolas GUILLAUME, Nicolle Helgers, Nidhi Jain, Niels Lange, Nikhil Chavan, Nilambar Sharma, Noam Eppel, notnownikki, odyssey, Omar Reiss, Omkar Bhagat, on, others, Ov3rfly, Paal Joachim Romdahl, palmiak, panchen, parbaugh, Parham Ghaffarian, Pascal Birchler, Pascal Casier, Paul Bearne, Paul Biron, Paul Paradise, Paul Schreiber, Perdaan, Peter Putzer, Peter Wilson, Petter Walbø Johnsgård, Pierre Saïkali, Pieter Daalder, Piyush Patel, poena, Pramod Jodhani, Prashant Baldha, Pratik K. Yadav, Pratik K. Yadav, precies, Presskopp, Presslabs, PressTigers, programmin, Punit Patel, Purnendu Dash, qcmiao, Rachel Baker, Rachel Cherry, Rachel Peter, Rafsun Chowdhury, Rahul Prajapati, Raja Mohammed, Ramanan, Rami Yushuvaev, Ramiz Manked, ramonopoly, RavanH, redcastor, remyvv, rensw90, rhetorical, Riad Benguella, Rian Rietveld, Richard Tape, Ricky Lee Whittemore, Rinku Y, Rishi Shah, Robbie, robdxw, Robert Anderson, Robin Cornett, Robin van der Vliet, Ryan McCue, Ryan Paul, Ryan Welcher, ryotsun, Sébastien SERRE, Saša, sagarnasit, Sami Ahmed Siddiqui, Sami Keijonen, Samuel Wood (Otto), sarah semark, Sayed Taqui, Scott Lee, Scott Reilly, Sean Hayes, Sebastian Kurzynoswki, Sebastian Pisula, Sergey Biryukov, Shamim Hasan, Shane Eckert, Sharaz Shahid, Shashwat Mittal, Shawn Hooper, sherwood, Shital Marakana, Shiva Poudel, Simon Prosser, sjardo, skoldin, slilley, slushman, Sonja Leix, sonjanyc, Soren Wrede, spartank, spyderbytes, Stanimir Stoyanov, Stanko Metodiev, stazdotio, Stephen Edgar, Stephen Harris, stevenlinx, Storm Rockwell, Stoyan Kostadinov, strategio, Subrata Sarkar, Sultan Nasir Uddin, swift, Takahashi Fumiki, Takayuki Miyauchi, Tammie Lister, Taylor Lovett, teddytime, Terri Ann, terwdan, tharsheblows, the, ThemeZee, Thomas Patrick Levy, Thomas Vitale, thomaswm, Thorsten Frommen, Thrijith Thankachan, Tiago Hillebrandt, tigertech, Tim Havinga, Tim Hengeveld, Timmy Crawford, Timothy Jacobs, titodevera, Tkama, to, Tobias Zimpel, Tom J Nowell, TomHarrigan, Tommy, tonybogdanov, Tor-Bjorn Fjellner, TorontoDigits, Toshihiro Kanai, Towhidul Islam, transl8or, Ulrich, upadalavipul, Usman Khalid, Utsav tilava, uttam007, Vaishali Panchal, Valérie Galassi, valchovski, vishaldodiya, vnsavage, voneff, warmlaundry, wbrubaker, Weston Ruter, who, Will Kwon, William Earnhardt, williampatton, wpcs, wpzinc, xhezairi, Yahil Madakiya, Yoav Farhi, Yui, YuriV, Zane Matthew, and zebulan. Finally, thanks to all the community translators who worked on WordPress 5.1. Their efforts bring WordPress 5.1 fully translated to 34 languages at release time, with more on the way. If you want to follow along or help out, check out Make WordPress and our core development blog. Thanks for choosing WordPress!

WordPress 5.1 RC2

The second release candidate for WordPress 5.1 is now available! WordPress 5.1 will be released on Thursday, February 21, but we need your help to get there—if you haven’t tried 5.1 yet, now is the time! There are two ways to test the WordPress 5.1 release candidate: try the WordPress Beta Tester plugin (you’ll want to select the “bleeding edge nightlies” option), or you can download the release candidate here (zip). For details about what to expect in WordPress 5.1, please see the first release candidate post. This release includes the final About page design. It also contains fixes for: New WordPress installs not setting the database table prefix correctly (#46220).A HTTP error occurring when opening browser developer tools (#46218).The legacy media dialog having incorrect pagination link styling (#41858).The comment form not appearing when clicking “Reply” on comments loaded via Ajax (#46260). Plugin and Theme Developers Please test your plugins and themes against WordPress 5.1 and update the Tested up to version in the readme to 5.1. If you find compatibility problems, please be sure to post to the support forums so we can figure those out before the final release. The WordPress 5.1 Field Guide has also been published, which goes into the details of the major changes. WordPress 5.1 Field Guide How to Help Do you speak a language other than English? Help us translate WordPress into more than 100 languages! If you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report, file one on WordPress Trac, where you can also find a list of known bugs. WordPress Five Point One: It’s so slick, shiny, and new. Lands in a few days!

WordPress 5.1 Release Candidate

The first release candidate for WordPress 5.1 is now available! This is an important milestone, as the release date for WordPress 5.1 draws near. “Release Candidate” means that the new version is ready for release, but with millions of users and thousands of plugins and themes, it’s possible something was missed. WordPress 5.1 is scheduled to be released on Thursday, February 21, but we need your help to get there—if you haven’t tried 5.1 yet, now is the time! There are two ways to test the WordPress 5.1 release candidate: try the WordPress Beta Tester plugin (you’ll want to select the “bleeding edge nightlies” option), or you can download the release candidate here (zip). What’s in WordPress 5.1? Inspired by Archie Bell & The Drells, WordPress’s theme for 2019 is to “tighten up”, and WordPress 5.1 focussed on exactly that. With security and speed in mind, this release introduces WordPress’s first Site Health features. WordPress will start showing notices to administrators of sites that run long-outdated versions of PHP, which is the programming language that powers WordPress. Furthermore, when installing new plugins, WordPress’s Site Health features will check whether a plugin requires a version of PHP incompatible with your site. If so, WordPress will prevent you from installing that plugin. The new block editor has kept improving since its introduction in WordPress 5.0. Most significantly, WordPress 5.1 includes solid performance improvements within the editor. The editor should feel a little quicker to start, and typing should feel smoother. There are more features and performance improvements planned in upcoming WordPress releases, you can check them out in the Gutenberg plugin. Plugin and Theme Developers Please test your plugins and themes against WordPress 5.1 and update the Tested up to version in the readme to 5.1. If you find compatibility problems, please be sure to post to the support forums so we can figure those out before the final release. The WordPress 5.1 Field Guide has also been published, which goes into the details of the major changes. WordPress 5.1 Field Guide How to Help Do you speak a language other than English? Help us translate WordPress into more than 100 languages! This release also marks the hard string freeze point of the 5.1 release schedule. If you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report, file one on WordPress Trac, where you can also find a list of known bugs. This is my release candidate. There are many like it. This is mine.

The Month in WordPress: January 2019

The momentum from December’s WordPress 5.0 release was maintained through January with some big announcements and significant updates. Read on to find out what happened in the WordPress project last month. WordPress Leadership Grows In a milestone announcement this month, WordPress project lead, Matt Mullenweg (@matt), named two individuals who are coming on board to expand the leadership team of the project. As Executive Director, Josepha Haden (@chanthaboune) will oversee all the contribution teams across the project. As Marketing & Communications Lead, Joost de Valk (@joostdevalk) will lead the Marketing team and generally oversee improvements to WordPress.org. Both Josepha and Joost have contributed to the WordPress project for many years and will certainly have a much larger impact going forward in their new roles. WordPress 5.1 Development Continues Immediately after the 5.0 release of WordPress, work started on version 5.1 with some highly anticipated new features coming out in the first beta release. Since then, the second and third betas have been made available. One of the core updates in this release — a feature to improve the way in which WordPress handles PHP errors — has been pushed back to version 5.2 due to unforeseen issues that would have caused significant delays to the 5.1 release. Want to get involved in testing or building WordPress Core? You can install the WordPress Beta Tester plugin, follow the Core team blog, and join the #core channel in the Making WordPress Slack group. Further Reading: The WordPress Coding Standards team released version 2.0 this month.In her new role as Executive Director, Josepha Haden looks at what contributors need to help support them more effectively.Approximately 2,300 tickets in the Core bug tracker were closed in a large bulk edit this month due to their inactivity over the last two years.Autocomplete for usernames has been added to the WordPress Support Forums, making it much easier to communicate directly with individuals.Work continues on the Gutenberg project, expanding into more areas of the WordPress dashboard.Since the new WordPress Support portal release in December, work has been ongoing to improve its features and complete the content migration.The Plugin Review team has published an important reminder about behavior in the Plugin Directory and support forums. Have a story that we should include in the next “Month in WordPress” post? Please submit it here.

WordPress 5.1 Beta 3

WordPress 5.1 Beta 3 is now available! This software is still in development, so we don’t recommend you run it on a production site. Consider setting up a test site to play with the new version. There are two ways to test the WordPress 5.1 beta: try the WordPress Beta Testerplugin (you’ll want to select the “bleeding edge nightlies” option), or you can download the beta here (zip). WordPress 5.1 is slated for release on February 21, and we need your help to get there! Site Health Check One of the features originally slated for WordPress 5.1—the PHP error protection handler—will target WordPress 5.2 instead. Some potential security issues were discovered in the implementation: rather than risk releasing insecure code, the team decided to pull it out of WordPress 5.1. The work in #46130 is showing good progress towards addressing the security concerns, if you’d like to follow development progress on this feature. Additional Changes A handful of smaller bugs have also been fixed in this release, including: TinyMCE has been upgraded to version 4.9.2 (#46094).The block editor has had a couple of bugs fixed (#46137).A few differences in behaviour between the classic block and the classic editor have been fixed (#46062, #46071, #46085).When adding rel attributes to links, ensure the value isn’t empty (#45352), and that it works as expected with customizer changesets (#45292). Developer Notes WordPress 5.1 has many changes aimed at polishing the developer experience. To keep you informed, we publish developers’ notes on the Make WordPress Core blog throughout the release cycle. Subscribe to the Make WordPress Core blog for updates over the coming weeks, detailing other changes in 5.1 that you should be aware of. How to Help Do you speak a language other than English? Help us translate WordPress into more than 100 languages! The beta 2 release also marks the soft string freeze point of the 5.1 release schedule. If you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report, file one on WordPress Trac, where you can also find a list of known bugs. In just a few weeks WordPress Five-One will be here. Your testing helps us!

WordPress 5.1 Beta 2

WordPress 5.1 Beta 2 is now available! This software is still in development, so we don’t recommend you run it on a production site. Consider setting up a test site to play with the new version. There are two ways to test the WordPress 5.1 beta: try the WordPress Beta Tester plugin (you’ll want to select the “bleeding edge nightlies” option), or you can download the beta here (zip). WordPress 5.1 is slated for release on February 21, and we need your help to get there! Over 110 tickets have been closed since beta 1, many of which are documentation and testing suite improvements. Here are the major changes and bug fixes: Several refinements and bug fixes related to the Site Health project have been made.The pre_render_block and render_block_data filters have been introduced allowing plugins to override block attribute values (#45451, dev note coming soon).get_template_part() will now return a value indicating whether a template file was found and loaded (#40969).A notice will now be triggered when developers incorrectly register REST API endpoints (related dev note).Bulk editing posts will no longer unintentionally change a post’s post format (#44914)Twemoji has been updated to the latest version, 11.2.0 (#45133).A bug preventing the Custom Fields meta box from being enabled has been fixed (#46028).The treatment of orderby values for post__in, post_parent__in, and post_name__in has been standardized (#38034).When updating language packs, old language packs are now correctly deleted to avoid filling up disk space (#45468). Developer Notes WordPress 5.1 has many changes aimed at polishing the developer experience. To keep you informed, we publish developers notes on the Make WordPress Core blog throughout the release cycle. Subscribe to the Make WordPress Core blog for updates over the coming weeks, detailing other changes in 5.1 that you should be aware of. How to Help Do you speak a language other than English? Help us translate WordPress into more than 100 languages! The beta 2 release als marks the soft string freeze point of the 5.1 release schedule. If you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report, file one on WordPress Trac, where you can also find a list of known bugs. Do you enjoy bugs? I don’t. So, we fixed them all. Well, not all. But close.

WordPress 5.1 Beta 1

WordPress 5.1 Beta 1 is now available! This software is still in development, so we don’t recommend you run it on a production site. Consider setting up a test site to play with the new version. There are two ways to test the WordPress 5.1 beta: try the WordPress Beta Tester plugin (you’ll want to select the “bleeding edge nightlies” option), or you can download the beta here (zip). WordPress 5.1 is slated for release on February 21, and we need your help to get there. Here are some of the big items to test so we can find as many bugs as possible in the coming weeks. Site Health Check Site Health Check is an ongoing project aimed at improving the stability and performance of the entire WordPress ecosystem. The first phase of this project is included in WordPress 5.1. For the first time, WordPress will catch and pause the problem code, so you can log in to your Dashboard and see what the problem is (#44458). Before, you’d have to FTP in to your files or get in touch with your host. Additionally, in April 2019, WordPress’ will increase its minimum supported PHP version to 5.6. To help you check if you’re prepared for this change, WordPress 5.1 will show you a warning and help you upgrade your version of PHP, if necessary. For Developers The Cron system can now be more easily replaced with a custom cron handler (#32656).When starting cron under PHP-FPM, the connection will return a response immediately, even for long running cron jobs (dev note).WP_DEBUG_LOG can be set to a custom log location (#18391).Introduced the wp_blogmeta table (#37923).Added LIKE support to meta_key comparisons in WP_Meta_Query (#42409). There have been over 360 tickets closed in WordPress 5.1, with numerous small bug fixes and improvements to help smooth your WordPress experience. Keep your eyes on the Make WordPress Core blog for more developer notes (which are assigned the dev-notes tag) in the coming weeks detailing other changes in 5.1 that you should be aware of. How to Help Do you speak a language other than English? Help us translate WordPress into more than 100 languages! If you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report, file one on WordPress Trac, where you can also find a list of known bugs. Miss my haiku?I will have plenty for youin the coming weeks.

WordPress 5.0.3 Maintenance Release

WordPress 5.0.3 is now available! 5.0.3 is a maintenance release that includes 37 bug fixes and 7 performance updates. The focus of this release was fine-tuning the new block editor, and fixing any major bugs or regressions. Here are a few of the highlights: 15 block editor related bug fixes and improvements have been added to bundled themes. Make sure to update these for an improved block editing experience.2 block editor related internationalization (I18N) bugs have been fixedUsers with JavaScript disabled now see a notice when attempting to use the block editor.A few PHP errors in the Customizer have been fixed.Some issues uploading common file types, like CSVs, have been fixed. For a full list of changes, please consult the list of tickets on Trac, changelog, or read a more technical summary on the Make WordPress Core blog. You can download WordPress 5.0.3 or visit Dashboard → Updates on your site and click Update Now. Sites that support automatic background updates have already started to update automatically. Thank you to everyone who contributed to WordPress 5.0.3: Aaron Jorbin, Alex Shiels, allancole, Andrea Fercia, Andrew Nevins, Andrew Ozz, Birgir Erlendsson (birgire), bobbingwide, Csaba (LittleBigThings), David Binovec, David Herrera, Dominik Schilling (ocean90), Felix Arntz, Gary Pendergast, Gerhard Potgieter, Grzegorz (Greg) Ziółkowski, Jb Audras, Job, Joe McGill, Joen Asmussen, John Blackbourn, Jonathan Desrosiers, kjellr, laurelfulford, Marcus Kazmierczak, Milan Dinić, Muntasir Mahmud, Nick Halsey, panchen, Pascal Birchler, Ramanan, Riad Benguella, Ricky Lee Whittemore, Sergey Biryukov, Weston Ruter, and William Earnhardt.

The Month in WordPress: December 2018

New features, a big event, and important announcements marked December as a milestone month for the WordPress community. Release of WordPress 5.0 On December 6 WordPress 5.0 was released. This release includes the much anticipated new block editor as the default editing experience. While some users have chosen to continue using the Classic Editor on their sites, many site owners have quickly upgraded to this latest version. Two security and maintenance releases came out over the course of the month, with the latest update providing a huge boost to performance and stability. The new version of WordPress comes a new default theme: Twenty Nineteen. This theme is designed to highlight how the block editor can be used. Want to get involved in developing WordPress Core? Follow the Core team blog and join the #core channel in the Making WordPress Slack group. Gutenberg Phase 2 The next phase of Gutenberg is being decided, starting with widgets, which will make it easier for users to customize their sites. This will be done with features being added to the Gutenberg plugin. Want to get involved in develop the future of the WordPress dashboard? Follow the Core team blog and join the #core channel in the Making WordPress Slack group. 9 Projects for 2019 WordPress co-founder Matt Mullenweg outlined 9 projects for the year 2019. These projects range from creating a block for navigations menus, porting all existing widgets into blocks, forming a triage team to tackle open issues on Trac and more. A status update for porting existing widgets to blocks has been posted by Mel Choyce. WordCamp US 2019 Dates announced WordCamp US 2019 will be held during Nov. 1-3, 2019, in St Louis, Missouri. It will be one of our largest events of the year and will feature Matt Mullenweg’s annual State of the Word address. Further Reading: v1.2.1 of the WordPress Coding Standards library has been released.A few revisions have been proposed for the WordPress JavaScript coding standards. If you have a story we should consider including in the next “Month in WordPress” post, please submit it here.

WordPress 5.0.2 Maintenance Release

WordPress 5.0.2 is now available! 5.0.2 is a maintenance release that addresses 73 bugs. The primary focus of this release was performance improvements in the block editor: the cumulated performance gains make it 330% faster for a post with 200 blocks. Here are a few of the additional highlights: 45 total Block Editor improvements are included (14 performance enhancements & 31 bug fixes).17 Block Editor related bugs have been fixed across all of the bundled themes.Some internationalization (i18n) issues related to script loading have also been fixed. For a full list of changes, please consult the list of tickets on Trac or the changelog. You can download WordPress 5.0.2 or visit Dashboard → Updates and click Update Now. Sites that support automatic background updates have already started to update automatically. Thank you to everyone who contributed to WordPress 5.0.2: Alexander Babaev, Alex Kirk, allancole, Andrea Fercia, Andrew Ozz, Anton Timmermans, David Binovec, David Trower, Dominik Schilling, Eduardo Pittol, Gary Pendergast, Greg Raven, gziolo, herregroen, iCaleb, Jb Audras, Joen Asmussen, John Blackbourn, Jonathan Desrosiers, khleomix, kjellr, laurelfulford, Jeff Paul, mihaivalentin, Milan Dinić, Muntasir Mahmud, Pascal Birchler, Pratik K. Yadav, Riad Benguella, Rich Tabor, strategio, Subrata Sarkar, tmatsuur, TorontoDigits, Ulrich, Vaishali Panchal, volodymyrkolesnykov, Weston Ruter, Yui, ze3kr, and のむらけい.

WordCamp US 2019 dates announced

Save the date! The next WordCamp US will be held on November 1-3, 2019, in beautiful St Louis, Missouri. One of our largest events of the year, WordCamp US is a great chance to connect with WordPress enthusiasts from around the world. This is also the event that features Matt Mullenweg’s annual State of the Word address. We’d love to see you in St. Louis next year, so mark your calendar now!

WordPress 5.0.1 Security Release

WordPress 5.0.1 is now available. This is a security release for all versions since WordPress 3.7. We strongly encourage you to update your sites immediately. Plugin authors are encouraged to read the 5.0.1 developer notes for information on backwards-compatibility. WordPress versions 5.0 and earlier are affected by the following bugs, which are fixed in version 5.0.1. Updated versions of WordPress 4.9 and older releases are also available, for users who have not yet updated to 5.0. Karim El Ouerghemmi discovered that authors could alter meta data to delete files that they weren’t authorized to.Simon Scannell of RIPS Technologies discovered that authors could create posts of unauthorized post types with specially crafted input.Sam Thomas discovered that contributors could craft meta data in a way that resulted in PHP object injection. Tim Coen discovered that contributors could edit new comments from higher-privileged users, potentially leading to a cross-site scripting vulnerability.Tim Coen also discovered that specially crafted URL inputs could lead to a cross-site scripting vulnerability in some circumstances. WordPress itself was not affected, but plugins could be in some situations. Team Yoast discovered that the user activation screen could be indexed by search engines in some uncommon configurations, leading to exposure of email addresses, and in some rare cases, default generated passwords.Tim Coen and Slavco discovered that authors on Apache-hosted sites could upload specifically crafted files that bypass MIME verification, leading to a cross-site scripting vulnerability. Thank you to all of the reporters for privately disclosing the vulnerabilities, which gave us time to fix them before WordPress sites could be attacked. Download WordPress 5.0.1, or venture over to Dashboard → Updates and click Update Now. Sites that support automatic background updates are already beginning to update automatically. In addition to the security researchers mentioned above, thank you to everyone who contributed to WordPress 5.0.1: Alex Shiels, Alex Concha, Anton Timmermans, Andrew Ozz, Aaron Campbell, Andrea Middleton, Ben Bidner, Barry Abrahamson, Chris Christoff, David Newman, Demitrious Kelly, Dion Hulse, Hannah Notess, Gary Pendergast, Herre Groen, Ian Dunn, Jeremy Felt, Joe McGill, John James Jacoby, Jonathan Desrosiers, Josepha Haden, Joost de Valk, Mo Jangda, Nick Daugherty, Peter Wilson, Pascal Birchler, Sergey Biryukov, and Valentyn Pylypchuk.

WordPress 5.0 “Bebo”

Say Hello to the New Editor We’ve made some big upgrades to the editor. Our new block-based editor is the first step toward an exciting new future with a streamlined editing experience across your site. You’ll have more flexibility with how content is displayed, whether you are building your first site, revamping your blog, or write code for a living. Building with Blocks The new block-based editor won’t change the way any of your content looks to your visitors. What it will do is let you insert any type of multimedia in a snap and rearrange to your heart’s content. Each piece of content will be in its own block; a distinct wrapper for easy maneuvering. If you’re more of an HTML and CSS sort of person, then the blocks won’t stand in your way. WordPress is here to simplify the process, not the outcome. We have tons of blocks available by default, and more get added by the community every day. Here are a few of the blocks to help you get started: ParagraphHeadingPreformattedQuoteImageGalleryCoverVideoAudioColumnsFileCodeListButtonEmbedsMore Freedom to Build, Freedom to Write This new editing experience provides a more consistent treatment of design as well as content. If you’re building client sites, you can create reusable blocks. This lets your clients add new content anytime, while still maintaining a consistent look and feel. A Stunning New Default Theme Introducing Twenty Nineteen, a new default theme that shows off the power of the new editor. Designed for the block editor Twenty Nineteen features custom styles for the blocks available by default in 5.0. It makes extensive use of editor styles throughout the theme. That way, what you create in your content editor is what you see on the front of your site. Simple, type-driven layout Featuring ample whitespace, and modern sans-serif headlines paired with classic serif body text, Twenty Nineteen is built to be beautiful on the go. It uses system fonts to increase loading speed. No more long waits on slow networks! Versatile design for all sites Twenty Nineteen is designed to work for a wide variety of use cases. Whether you’re running a photo blog, launching a new business, or supporting a non-profit, Twenty Nineteen is flexible enough to fit your needs. Give Twenty Nineteen a try Developer Happiness Protect Blocks provide a comfortable way for users to change content directly, while also ensuring the content structure cannot be easily disturbed by accidental code edits. This allows the developer to control the output, building polished and semantic markup that is preserved through edits and not easily broken. Compose Take advantage of a wide collection of APIs and interface components to easily create blocks with intuitive controls for your clients. Utilizing these components not only speeds up development work but also provide a more consistent, usable, and accessible interface to all users. Create The new block paradigm opens up a path of exploration and imagination when it comes to solving user needs. With the unified block insertion flow, it’s easier for your clients and customers to find and use blocks for all types of content. Developers can focus on executing their vision and providing rich editing experiences, rather than fussing with difficult APIs. Learn how to get started Keep it Classic Prefer to stick with the familiar Classic Editor? No problem! Support for the Classic Editor plugin will remain in WordPress through 2021. The Classic Editor plugin restores the previous WordPress editor and the Edit Post screen. It lets you keep using plugins that extend it, add old-style meta boxes, or otherwise depend on the previous editor. To install, visit your plugins page and click the “Install Now” button next to “Classic Editor”. After the plugin finishes installing, click “Activate”. That’s it! Note to users of assistive technology: if you experience usability issues with the block editor, we recommend you continue to use the Classic Editor. Check out the Classic Editor This release is named in homage to the pioneering Cuban jazz musician Bebo Valdés. The Squad This release was led by Matt Mullenweg, along with co-leads Allan Cole, Anthony Burchell, Gary Pendergast, Josepha Haden Chomphosy, Laurel Fulford, Omar Reiss, Daniel Bachhuber, Matías Ventura, Miguel Fonseca, Tammie Lister, Matthew Riley MacPherson. They were ably assisted by the following fabulous folks. There were 423 contributors with props in this release. Pull up some Bebo Valdés on your music service of choice, and check out some of their profiles: Aaron Jorbin, Abdul Wahab, Abdullah Ramzan, Abhijit Rakas, Adam Silverstein, afraithe, Ahmad Awais, ahmadawais, Airat Halitov, Ajit Bohra, Alain Schlesser, albertomedina, aldavigdis, Alex Kirk, Alex Sanford, Alex Shiels, Alexander Babaev, Alexander Botteram, alexis, Alexis Lloyd, Amanda Rush, amedina, Andrés, Andrea Fercia, Andrea Middleton, Andrei Lupu, andreiglingeanu, Andrew Duthie, Andrew Munro, Andrew Nevins, Andrew Ozz, Andrew Roberts, Andrew Taylor, andrewserong, Andy Peatling, Angie Meeker, Anna Harrison, Anton Timmermans, ArnaudBan, Arshid, Arya Prakasa, Asad, Ashar Irfan, Asvin Balloo, Atanas Angelov, Bappi, bcolumbia, belcherj, Ben Lowery, Benjamin Eyzaguirre, Benjamin Zekavica, benlk, Bernhard Kau, Bernhard Reiter, betsela, Bhargav Mehta, Birgir Erlendsson (birgire), Birgit Pauli-Haack, bobbingwide, boblinthorst, Boone Gorges, Brady Vercher, Brandon Kraft, Brandon Payton, Brent Swisher, Brianna Privett, briannaorg, Bronson Quick, Brooke., Burhan Nasir, Caleb Burks, CantoThemes, cathibosco, Chetan Prajapati, chetansatasiya, chetansatasiya, Chouby, Chris Lloyd, Chris Runnells, Chris Van Patten, chriskmnds, Christian Sabo, Christoph Herr, Claudio Sanches, coderkevin, Copons, courtney0burton, Crisoforo Gaspar, Csaba (LittleBigThings), csabotta, Daniel James, Daniel Richards, danielhw, daniloercoli, Danny Cooper, Darren Ethier (nerrad), davemoran118, David Binovec, David Cavins, David Herrera, David Kennedy, David Ryan, David Sword, David Trower, Davide 'Folletto' Casali, davidherrera, Davis, dciso, Dennis Snell, Derek Smart, designsimply, Devin Walker, Devio Digital, dfangstrom, Dhanendran, Diego de Oliveira, diegoreymendez, dingo_d, Dion Hulse, Dixita Dusara, Dixita Dusara Gohil, Dominik Schilling, Donna Peplinskie, Drew Jaynes, dsawardekar, dsifford, Duane Storey, Eduardo Pittol, Edwin Cromley, ehg, ElectricFeet, Elio Rivero, Elisabeth Pointal, Ella Iseulde Van Dorpe, elrae, enodekciw, ephoxjames, ephoxmogran, Eric Amundson, ericnmurphy, etoledom, Evan Mullins, fabiankaegy, fabs_pim, Faishal, Felix Arntz, Florian Simeth, foobar4u, foreverpinetree, Frank Klein, fuyuko, Gabriel Maldonado, Garrett Hyder, Gary Jones, Gary Thayer, garyjones, Gennady Kovshenin, George Olaru, George Stephanis, georgeh, Gerhard Potgieter, gnif, goldsounds, Grappler, Greg Raven, Grzegorz Ziółkowski, Gustavo Bordoni, gwwar, Hardeep Asrani, hblackett, Helen Hou-Sandi, Hendrik Luehrsen, herbmiller, Herre Groen, Hugo Baeta, hypest, Ian Belanger, Ian Dunn, ianstewart, idpokute, Igor, imath, Imran Khalid, intronic, Ipstenu (Mika Epstein), Irene Strikkers, Ismail El Korchi, israelshmueli, J.D. Grimes, J.D. Grimes, Jacob Peattie, jagnew, jahvi, James Nylen, jamestryon, jamiehalvorson, Jan Dembowski, janalwin, Jason Caldwell, Jason Stallings, Jason Yingling, Javier Villanueva, Jay Hoffmann, Jb Audras, Jeff Bowen, Jeffrey Paul, Jeremy Felt, Jip Moors, JJJ, Job, Joe Bailey-Roberts, Joe Dolson, Joe Hoyle, Joe McGill, joemaller, Joen Asmussen, Johan Falk, John Blackbourn, John Godley, johndyer, JohnPixle, johnwatkins0, jomurgel, Jon Surrell, Jonathan Desrosiers, Jonny Harris, Joost de Valk, Jorge Bernal, Jorge Costa, Jose Fremaint, Josh Pollock, Josh Visick, Joshua Wold, Joy, jrf, jryancard, jsnajdr, JulienMelissas, Justin Kopepasah, K.Adam White, Kallehauge, KalpShit Akabari, Kat Hagan, Kelly Dwan, Kevin Hoffman, khleomix, Kite, Kjell Reigstad, kluny, Konstantin Obenland, Konstantinos Xenos, krutidugade, Lance Willett, Lara Schenck, leahkoerper, lloyd, Loïc Blascos, Lucas Stark, LucasRolff, luigipulcini, Luke Cavanagh, Luke Kowalski, Luke Pettway, Luminus, lynneux, macbookandrew, Maedah Batool, Mahdi Yazdani, mahmoudsaeed, Maja Benke, Marcus Kazmierczak, Marin Atanasov, marina_wp, Marius L. J., mariusvw, Mark Jaquith, Mark Uraine, Marko Andrijasevic, martinlugton, Marty Helmick, mathiu, Matt Cromwell, Matt Mullenweg, MattGeri, Matthew Boynes, Matthew Haines-Young, maurobringolf, Maxime BERNARD-JACQUET, Mayo Moriyama, meetjey, Mel Choyce, mendezcode, Micah Wood, Micah Wood, Michael Adams (mdawaffe), Michael Hull, Michael Nelson, Michele Mizejewski, Migrated to @jeffpaul, mihaivalentin, Miina Sikk, Mikael Korpela, Mike Crantea, Mike Haydon, Mike Schroder, Mike Selander, mikehaydon, Mikey Arce, Milan Dinić, Milana Cap, Milen Petrinski - Gonzo, milesdelliott, mimo84, mirka, mmtr86, Monique Dubbelman, Morten Rand-Hendriksen, Mostafa Soufi, motleydev, mpheasant, mrmadhat, mrwweb, msdesign21, mtias, Muhammad Irfan, Mukesh Panchal, munirkamal, Muntasir Mahmud, mzorz, nagayama, Nahid F. Mohit, Naoko Takano, napy84, nateconley, Native Inside, Ned Zimmerman, Neil Murray, nic.bertino, Nick Halsey, Nicola Heald, Niels Lange, Nikhil Chavan, Nikolay Bachiyski, nitrajka, njpanderson, nshki, Okamoto Hidetaka, oskosk, panchen, Paresh Radadiya, Pascal Birchler, Paul Bearne, Paul Dechov, Paul Stonier, Paul Wilde, Pedro Mendonça, Peter Wilson, pglewis, Philipp Bammes, piersb, Pieter Daalder, pilou69, Piotr Delawski, poena, postphotos, potbot, Prateek Saxena, Pratik K. Yadav, Presskopp, psealock, ptasker, Rachel, Rachel Baker, Rahmohn, Rahmon, Rahul Prajapati, rakshans1, Ramanan, ramonopoly, Rastislav Lamos, revgeorge, Riad Benguella, Rian Rietveld, Rich Tabor, richsalvucci, Ricky Lee Whittemore, Riddhi Mehta, rileybrook, Robert Anderson, Robert O'Rourke, robertsky, Rocio Valdivia, Rohit Motwani, Ross Wintle, Ryan McCue, Ryan Welcher, ryo511, Sagar Prajapati, Sami Keijonen, Samuel Wood (Otto), Sang-Min Yoon, sarah semark, Scott Weaver, Sergey Biryukov, SergioEstevao, Shahjehan Ali, Shailee Sheth, Sharaz Shahid, Shaun sc, shaunandrews, Shawn Hooper, shenkj, sikander, Simon Prosser, siriokun, sirjonathan, sirreal, Sisanu, skorasaurus, Slushman, Sofia Sousa, SOMTIJDS, Soren Wrede, spocke, Stagger Lee, Stanimir Stoyanov, Stephen Edgar, Steve Henty, Store Locator Plus, strategio, stuartfeldt, Subrata Sarkar, tacrapo, talldan, Tammie Lister, ThemeRoots, Thorsten Frommen, Thrijith Thankachan, Tim Hengeveld, timgardner, Timmy Crawford, Timothy Jacobs, tmatsuur, Tom J Nowell, Toni Laakso, Toni Viemerö, Tor-Bjorn Fjellner, Toro_Unit (Hiroshi Urabe), TorontoDigits, Toshihiro Kanai, Towhidul Islam, Travis Lopes, truongwp, Tunji Ayoola, twoelevenjay, Ulrich, Vaishali Panchal, Vishal Kakadiya, Vitor Paladini, volodymyrkolesnykov, Walter Ebert, warmarks, WebMan Design | Oliver Juhas, websupporter, Weston Ruter, William Earnhardt, williampatton, Willy Bahuaud, Yahil Madakiya, yingles, Yoav Farhi, Yui, Yusuke Takahashi, ze3kr, zebulan, Ziyaddin Sadigov, and のむらけい (Kei Nomura). Finally, thanks to all the community translators who worked on WordPress 5.0. Their efforts bring WordPress 5.0 fully translated to 37 languages at release time, with more on the way. If you want to follow along or help out, check out Make WordPress and our core development blog. Thanks for choosing WordPress!

The Month in WordPress: November 2018

WordPress 5.0 is almost ready for release, including an all-new content editing experience. Volunteers all across the project are gearing up for the launch and making sure everything is ready. Read on to find out what’s been happening and how you can get involved. WordPress 5.0 Close to Launch The release date for WordPress 5.0 has not yet been set, but the second release candidate (RC) is now available. The final release date will be determined based on feedback and testing of this RC. The Core development team has been posting daily updates on the progress of their work on v5.0, with the number of open issues for this release decreasing every day. The primary feature of this release is the new editor that will become the default WordPress experience going forward. A number of people have been seeking more direct feedback from the release leads about the progress of this release, which @matt has facilitated by hosting one-to-one discussions with anyone in the community who wanted to talk with him about it. He has also published an extended FAQ covering many of the questions people have been asking. Alongside the development of the new editor, the Mobile team has been working hard to bring the WordPress mobile apps up to speed. They plan to make a beta version available in February 2019. Want to get involved in developing WordPress Core in 5.0 and beyond? Follow the Core team blog and join the #core channel in the Making WordPress Slack group. New WordPress Support Platform Goes Live WordPress user documentation has long been hosted on the WordPress Codex, but for the past couple of years an ambitious project has been underway to move that content to a freshly-built WordPress-based platform. This project, named “HelpHub,” is now live and the official home of WordPress Support. There is still plenty of content that needs to be migrated from the Codex to HelpHub, but the initial move is done and the platform is ready to have all WordPress’ user documentation moved across. HelpHub will be the first place for support, encouraging users to find solutions for themselves before posting in the forums. Want to get involved in populating HelpHub with content, or with its future development? Follow the Documentation team blog and join the #docs channel in the Making WordPress Slack group. Spanish WordPress Community Pushes Translations Forward The WordPress community in Spain has been hard at work making sure as much of the WordPress project as possible is available in Spanish. They have recently translated more of the project than ever — including WordPress Core, WordPress.org, the mobile apps and the top 120 plugins in the Directory. This achievement has largely been possible due to the fact that the Spanish translation team has over 2,500 individuals contributing to it, making it the largest translation team across the whole project. Want to get involved in translating WordPress into your local language? You can jump straight into translations, follow the Polyglots team blog and join the #polyglots channel in the Making WordPress Slack group. Further Reading: All volunteer teams have checked in with their latest quarterly updates.The WordPress Support Team is hosting an orientation for new Support volunteers on December 9.Tickets are now available to watch the WordCamp US livestream for free.WordPress Core has switched to a WP-CLI command for generating localization files.WordPress Coding Standards v1.2.0 has been released with some really useful improvements.The first ever WordCamp Nordic is taking place on March 7-8, 2019 with ticket sales now open.The WordCamp Incubator program is going very well this year — you can see the latest updates here.The Mobile Team is looking for testers for the upcoming v11.3 release of the WordPress mobile apps on Android and iOS.The WordCamp Europe team is looking for local communities to apply to be the host city for the 2020 event. If you have a story we should consider including in the next “Month in WordPress” post, please submit it here.

Pages

Recommended Content