WordPress.org News

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.

WordPress 5.0 RC2

The second release candidate for WordPress 5.0 is now available! This is an important milestone, as we near the release of WordPress 5.0. A final release date will be announced soon, based on feedback from this release candidate. Things are appearing very stable and we hope to announce a date soon. This is a big release and needs your help—if you haven’t tried 5.0 yet, now is the time!  To test WordPress 5.0, you can use the WordPress Beta Tester plugin or you can download the release candidate here (zip). For details about what to expect in WordPress 5.0, please see the previous release candidate post. Significant changes We stopped rendering AdminNotices compatibility component, as this previous attempt at backward compatibility was bringing in numerous incompatible banners and notices from plugins.An update to the parser to better deal with malformed HTML that could cause a loop. We’re only aware of this in the wild being triggered once in the over a million posts made with Gutenberg, but it caused a loop so we wanted to fix for RC2. Cosmetic and minor changes in RC2 Accessibility: Simplify sidebar tabs aria-labels.Make the Image Link URL field readonly.Internationalization: Merge similar text strings that differed only in capitalization.CSS: Improve block preview styling.CSS: Fix visual issues with Button block text wrap.Fix getSelectedBlockClientId selector.Fix Classic block not showing galleries on a grid.Fix an issue where the block toolbar would cause an image to jump downwards when the wide or full alignments were activated.Move editor specific styles from style.scss to editor.scss in Cover block.Fix modals in Microsoft Edge browser.Fix Microsoft IE11 focus loss after TinyMCE init. Add IE check.Fix Microsoft IE11 input when mounting TinyMCE.Change @package names to WordPress. 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. RC bittersweet.We welcome in Gutenberg,Vale Gutenbeard.

WordPress 5.0 Release Candidate

The first release candidate for WordPress 5.0 is now available! This is an important milestone, as we near the release of WordPress 5.0. The WordPress 5.0 release date has shifted from the 27th to give more time for the RC to be fully tested. A final release date will be announced soon, based on feedback on the RC. This is a big release and needs your help—if you haven’t tried 5.0 yet, now is the time!  To test WordPress 5.0, you can use the WordPress Beta Tester plugin or you can download the release candidate here (zip). What’s in WordPress 5.0? The new block-based post editor. WordPress 5.0 introduces the new block-based post editor. This 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. The block editor is used on over a million sites, we think it’s ready to be used on all WordPress sites. We do understand that some sites might need some extra time, though. If that’s you, please install the Classic Editor plugin, you’ll continue to use the classic post editor when you upgrade to WordPress 5.0. Twenty Nineteen is WordPress’ new default theme, it features custom styles for the blocks available by default in 5.0. 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. The block editor is a big change, but that’s not all. We’ve made some smaller changes as well,  including: All of the previous default themes, from Twenty Ten through to Twenty Seventeen, have been updated to support the block editor.You can improve the accessibility of the content you write, now that simple ARIA labels can be saved in posts and pages.WordPress 5.0 officially supports the upcoming PHP 7.3 release: if you’re using an older version, we encourage you to upgrade PHP on your site.Developers can now add translatable strings directly to your JavaScript code, using the new JavaScript language packs. You can read more about the fixes and changes since Beta 5 in the last update post. For more details about what’s new in version 5.0, check out the Beta 1, Beta 2, Beta 3, Beta 4 and Beta 5 blog posts. Plugin and Theme Developers Please test your plugins and themes against WordPress 5.0 and update the Tested up to version in the readme to 5.0. If you find compatibility problems, please be sure to post to the support forums so we can figure those out before the final release. An in-depth field guide to developer-focused changes is coming soon on the core development blog. In the meantime, you can review the developer notes for 5.0. 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. Ruedan los bloquesContando vivos cuentosQue se despiertan

WordPress 5.0 Beta 5

WordPress 5.0 Beta 5 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 this WordPress 5.0 Beta: try the WordPress Beta Tester plugin (you’ll want “bleeding edge nightlies”), or you can download the beta here (zip). Reminder: the WordPress 5.0 release date has changed. It is now scheduled for release on November 27, and we need your help to get there. Here are some of the big issues that we’ve fixed since Beta 4: Block Editor The block editor has been updated to match the Gutenberg 4.4 release, the major changes include:  A permalink panel has been added to the document sidebar to make it easier to find.Editor document panels can now be programmatically removed.The uploading indicator for images and galleries has been replaced with a spinner and faded out image.The text and code editing blocks will now use the full width of the editor.Image handling has been improved. Images now take up the right amount of space for themes with wider editors (like Twenty Nineteen).Hover styles are now correctly disabled for mobile devices.The i18n module has been refactored to benefit from significant performance gains. Additionally, there have been some pesky bugs fixed: Better handling for links without an href attribute, which were showing as undefined.Japanese text (double byte characters) are now usable in the list block.Better handling for different text encodings (e.g. emoji) within a block in block validation. A full list of changes can be found in the Gutenberg 4.4 release post. PHP 7.3 Support The final known PHP 7.3 compatibility issue has been fixed. You can brush up on what you need to know about PHP 7.3 and WordPress by checking out the developer note on the Make WordPress Core blog. Twenty Nineteen Work on making Twenty Nineteen ready for prime time continues on its GitHub repository. This update includes a host of tweaks and bug fixes, including: Add .button class support.Fix editor font-weights for headings.Improve support for sticky toolbars in the editor.Improve text-selection custom colors for better contrast and legibility.Fix editor to prevent Gutenberg’s meta boxes area from overlapping the content. 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 5.0 Beta 4

WordPress 5.0 Beta 4 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.0 Beta: try the WordPress Beta Tester plugin (you’ll want “bleeding edge nightlies”), or you can download the beta here (zip). The WordPress 5.0 release date has changed, it is now scheduled for release on November 27, and we need your help to get there. Here are some of the big issues that we’ve fixed since Beta 3: Block Editor The block editor has been updated to match the Gutenberg 4.3 release, the major changes include: An Annotations API, allowing plugins to add contextual data as you write.More consistent keyboard navigation between blocks, as well as back-and-forth between different areas of the interface.Improved accessibility, with additional labelling and speech announcements. Additionally, there have been some bugs fixed that popped up in beta 3: Better support for plugins that have more advanced meta box usage.Script concatenation is now supported.Ajax calls could occasionally cause PHP errors. Internationalisation We’ve added an API for translating your plugin and theme strings in JavaScript files! The block editor is now using this, and you can start using it, too. Check out the developer note to get started. Twenty Nineteen Twenty Nineteen is being polished over on its GitHub repository. This update includes a host of tweaks and bug fixes, including: Menus now properly support keyboard and touch interactions.A footer menu has been added for secondary page links.Improved backwards compatibility with older versions of WordPress. Default Themes All of the older default themes—from Twenty Ten through to Twenty Seventeen—have polished styling in the block editor. 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. International-isation is a word withmany syllables. Meta boxes arethe original style block.Old is new again.

Quarterly Updates | Q3 2018

To keep everyone aware of big projects and efforts across WordPress contributor teams, I’ve reached out to each team’s listed representatives. I asked each of them to share their Top Priority (and when they hope for it to be completed), as well as their biggest Wins and Worries. Have questions? I’ve included a link to each team’s site in the headings. Accessibility Contacted: @joedolson, @audrasjb, @arush Priority: Work on authoring a manual for assistive technology users on Gutenberg, led by Claire Brotherton (@abrightclearweb). Continue to work on improving the overall user experience in Gutenberg. Update and organize the WP A11y handbook. Struggle: Lack of developers and accessibility experts to help test and code the milestone issues. Still over 100 outstanding issues, and developing the Gutenberg AT manual helps expose additional issues. The announcement of an accessibility focus on 4.9.9 derailed our planning for Gutenberg in September with minimal productivity, as that goal was quickly withdrawn from the schedule. Big Win: Getting focus constraint implemented in popovers and similar components in Gutenberg. CLI Contacted: @danielbachhuber, @schlessera Priority: Current priority is v2.1.0 of WP-CLI, to polish the major refactoring v2.0.0 introduced. You can join in or follow progress on their site. Struggle: Getting enough contributors to make peer-review possible/manageable. Big Win: The major refactoring of v2 was mostly without any negative impacts on existing installs. It provided substantial improvements to maintainability including: faster and more reliable testing, more straight-forward changes to individual packages, and simpler contributor on-boarding. Community Contacted: @francina, @hlashbrooke Priority: Supporting contributors of all levels via: monthly WordCamp Organizers chat, better onboarding with a translated welcome pack, and Contribution Drive documentation. Struggle: Fewer contributors than usual. Big Win: Meetup Vetting Sprint!  Core Contacted: @jeffpaul Priority: Continued preparation for the 5.0 release cycle and Gutenberg. Struggle: Identifying tasks for first time contributors, as well as for new-to-JS contributors. Design Contacted: @melchoyce, @karmatosed, @boemedia, @joshuawold, @mizejewski Priority: Preparing for WordPress 5.0 and continuing to work on better onboarding practices. Struggle: Identifying tasks for contributor days, especially for small- to medium-sized tasks that can be fit into a single day. Big Win: Regular contributions are starting to build up. Documentation Contacted: @kenshino Priority: Getting HelpHub out before WordPress 5.0’s launch to make sure Gutenberg User Docs have a permanent position to reside Struggle: Getting the documentation from HelpHub into WordPress.org/support is more manual than initially anticipated. Big Win: Had a good discussion with the Gutenberg team about their docs and how WordPress.org expects documentation to be distributed (via DevHub, Make and HelpHub). Getting past the code blocks to release HelpHub (soon) Hosting Contacted: @mikeschroder, @jadonn Priority: Helping Gutenberg land well at hosts for users in 5.0. Struggle: Short time frame with few resources to accomplish priority items. Big Win: Preparing Try Gutenberg support guide for hosts during the rollout and good reception from users following it. Marketing Contacted: @bridgetwillard Priority: Continuing to write and publish case studies from the community. Big Win: Onboarding guide is going well and is currently being translated. Meta (WordPress.org Site) Contacted: @tellyworth, @coffee2code Priority: Support for other teams in the lead up to, and the follow-up of, the release of WP 5.0. ETA is the WP 5.0 release date (Nov 19) and thereafter, unless it gets bumped to next quarter. Struggle: Maintaining momentum on tickets (still). Big Win: Launch of front-end demo of Gutenberg on https://wordpress.org/gutenberg/ Mobile Contacted: @elibud Priority: Have an alpha version of Gutenberg in the WordPress apps, ETA end of year 2018. Struggle: Unfamiliar tech stack and the goal of reusing as much of Gutenberg-web’s code as possible. Big Win: Running mobile tests on web’s PRs. Plugins Contacted: @ipstenu Priority: Cleaning up ‘inactive’ users, which was supposed to be complete but some work preparing for 5.0 was necessary. Struggles: Devnotes are lacking for the upcoming release which slows progress. Big Win: No backlog even though a lot were out! Polyglots Contacted: @petya, @ocean90, @nao, @chantalc, @deconf, @casiepa Priority: Help re-activating inactive locale teams. Struggle: Many GTEs are having a hard time keeping up with incoming translation validation and PTE requests. Big Win: Made some progress in locale research and reassigning new GTEs. Support Contacted: @clorith Priority: Preparing for the upcoming 5.0 release Struggle: Finding a good balance between how much we want to help people and how much we are able to help people. Also, contributor recruitment (always a crowd favorite!) Big Win: How well the team, on a global level, has managed to maintain a good flow of user engagement through support. Theme Review Contacted: @acosmin, @rabmalin, @thinkupthemes, @williampatton Priority: Implementing the Theme Sniffer plugin on WordPress.org which is one step forward towards automation. ETA early 2019 Struggle: Not having so many contributors/reviewers. Big Win: Implementing multiple requirements into our review flow, like screenshots and readme.txt requirements. Training Contacted: @bethsoderberg, @juliek Priority: Getting the learn.wordpress.org site designed, developed, and being able to publish lesson plans to it. Struggle: Getting contributors onboard and continually contributing. Part of that is related to the learn.wordpress.org site. People like to see their contributions. Big Win: We have our new workflow and tools in place. We are also streamlining that process to help things go from idea to publication more quickly. Interested in updates from the last quarter? You can find those here: https://wordpress.org/news/2018/07/quarterly-updates-q2-2018/

The Month in WordPress: October 2018

Teams across the WordPress project are working hard to make sure everything is ready for the upcoming release of WordPress 5.0. Find out what’s going on and how you can get involved. The Plan for WordPress 5.0 Early this month, the planned release schedule was announced for WordPress 5.0, which was updated a few weeks later. WordPress 5.0 is a highly anticipated release, as it’s the official  launch of Gutenberg — the new block editor for WordPress Core. For more detail, check out this  granular timeline. Along with the planned release schedule, @matt, who is heading up this release, announced leads for critical focuses on the project, including @matveb, @karmatosed, @laurelfulford, @allancole, @lonelyvegan, @omarreiss, @antpb, @pento, @chanthaboune, @danielbachhuber, and @mcsf. WordPress 5.0 is currently in its second beta phase and will soon move to the release candidate status. Help test this release right now by installing the WordPress Beta Tester plugin on your 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. You can also help out by testing or translating the release into a local language. New Editor for WordPress Core Active development continues on Gutenberg, the new editing experience for WordPress Core. The latest release is feature complete, meaning that all further development on it will be to improve existing features and fix outstanding bugs. Some have raised concerns about Gutenberg’s accessibility, prompting the development team to detail some areas in which the new editor is accessible. To help improve things further, the team has made a public call for accessibility testers to assist. Want to get involved in building Gutenberg? Follow the Gutenberg tag on the Core team blog and join the #core-editor channel in the Making WordPress Slack group. Read this guide to find areas where you can have the most impact. Migrating HelpHub to WordPress.org HelpHub is an ongoing project to move all of WordPress’ user documentation from the Codex to the WordPress Support portal. HelpHub has been developed on a separate staging server and it’s now time to migrate the new documentation to its home on WordPress.org. The plan is to have everything moved over  before WordPress 5.0 is released, so that all the new documentation will be available on the new platform from the start. The HelpHub team has published a call for volunteers to help with the migration. If you would like to get involved, join the #docs channel in the Making WordPress Slack group, and contact @atachibana to get started. A New Default Theme for WordPress A brand new default theme — Twenty Nineteen — has been announced with development being led by @allancole. The theme is packaged with WordPress 5.0, so it will be following the same release schedule as Core. The new theme is designed to integrate seamlessly with Gutenberg and showcase how you can build a theme alongside the new block editor and take advantage of the creative freedom that it offers. Want to help build Twenty Nineteen? Join in on the theme’s GitHub repo and join the #core-themes channel in the Making WordPress Slack group. Further Reading: The Support team are putting together more formal Support Guidelines for the WordPress Support Forums.The group focused on privacy tools in Core has released some details on the work they have been doing recently, with a roadmap for their plans over the next few months.The Core team released an update about how WordPress will be compatible with PHP 7.3.The Theme Review Team have published some new requirements regarding child themes, readme files and trusted authors in the Theme Directory.The WordCamp Europe team are working on a PWA service for all WordCamp websites. If you have a story we should consider including in the next “Month in WordPress” post, please submit it here.

WordPress 5.0 Beta 2

WordPress 5.0 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.0 Beta: try the WordPress Beta Tester plugin (you’ll want “bleeding edge nightlies”), or you can download the beta here (zip). WordPress 5.0 is slated for release on November 19, and we need your help to get there. Here are some of the big issues that we fixed since Beta 1: Block Editor We’ve updated to the latest version of the block editor from the Gutenberg plugin, which includes the new Format API, embedding improvements, and a variety of bug fixes. Meta boxes had a few bugs, and they weren’t showing at all in the block editor, so we’ve fixed and polished there. Internationalisation We’ve added support for registering and loading JavaScript translation files. Twenty Nineteen The Twenty Nineteen repository is a hive of activity, there have been a stack of minor bugs clean up, and some notable additions: There’s now a widget area in the page footer.Navigation submenus have been implemented for mobile devices.Customiser options have been added for changing the theme colours and feature image filters. Everything Else The REST API has a couple of bug fixes and performance improvements. PHP 7.3 compatibility has been improved. We’re fixing the bugs:All the ones you’ve reported.Some that we’ve found, too.

The Month in WordPress: September 2018

The new WordPress editor continues to be a major focus for all WordPress contribution teams. Read on to find out some more about their work, as well as everything else that has been happening around the community this past month. Further Enhancements to the New WordPress Editor Active development continues on Gutenberg, the new editing experience for WordPress Core. The latest update for the editor includes great new features, such as reusable content blocks, a dark editor style, export and import of templates, and much more. In addition, the Gutenberg team has published a comprehensive guide to the features currently included in the editor. Users can test Gutenberg right now by installing the plugin, which currently has over 450,000 active installs according to the new Gutenberg in Numbers site. Along with that, the Gutenberg Handbook has some very useful information about how to use and develop for the new editor. Want to get involved in building Gutenberg? Follow the #gutenberg tag on the Core team blog and join the #core-editor channel in the Making WordPress Slack group. Work Begins on WordPress 5.0 After initially announcing a minor v4.9.9 release, the Core team has shifted their focus to the next major release — v5.0. One of the primary factors for this change is that Gutenberg is nearly ready to be considered for merging into Core, with the goal to complete the merge in v5.0. To maintain flexibility in the development process the final timelines are not yet determined, allowing work already done for v4.9.9 to be moved to v5.0 if needed. Ensuring that WordPress is compatible with the upcoming PHP 7.3 release is a high priority for the Core team. Once a final decision is made, the details will be announced on the Core team blog. Want to get involved in building WordPress Core? Follow the Core team blog and join the #core channel in the Making WordPress Slack group. Further Reading: The Community Team has some great updates on the progress of the current WordCamp Incubator Program.A team inside the Drupal community is working on integrating Gutenberg into their CMS.There is a current discussion among community organizers about plans to increase the maximum ticket price for WordCamps.The Mobile Team is looking for people to grow the beta program for testing the iOS and Android mobile apps.The Diversity Outreach Speaker Training group is looking for feedback on their document to assist WordPress Meetups and WordCamps in building diverse speaker rosters.The Theme Team has updated their rules regarding sponsored and affiliate links inside themes added to the Theme Directory.Meetup organizers are now able to receive a WordPress.org profile badge for their community work. If you have a story we should consider including in the next “Month in WordPress” post, please submit it here.

Pages

Recommended Content