Devchat summary, September 28, 2022

1. Welcome

@marybaum and @webcommsat led the meeting on this agenda.

Last week’s summary, if you like to keep track.

2. Anouncements

WordPress 6.1 Beta 2 landed on Tuesday, September 27, 2022. Props to everyone who helped!

3. Blogblog (versus network, site) posts of note

A Week in Core – September 26, 2022 – thanks @audrasjb

Core Editor Improvement: Catalyst for creativity and control, September 26, 2022 – posted by @annezazu

Proposal: Client-side WebAssembly WordPress with no server, September 23, 2022

Roadmap to 6.1 core companion .

4. Upcoming releases

The next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope. is WordPress 6.1.

@audrasjb gave a triage update.

On the 488 tickets in the milestone:

5. Maintainers and tickets

@sergeybiryukov reported in on several components. They covered these tickets:

On Help/About, @marybaum reported a new patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. for #50866.

@webcommsat raised #55603 on behalf of @costdev. Discussion followed on the impacts of trying to get it in for 6.1 or moving it to 6.2.

On behalf of @luminuu, @marybaum raised ticketticket Created for both bug reports and feature development on the bug tracker. #55985. That also prompted some discussion.

For @ndiego, @webcommsat raised #44434, a GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ issue.

And for Quick/Bulk edit, @webcommsat asked for eyeballs on #19859.

Props to @webcommsat for meeting prep, @marybaum and @webcommsat for facilitating, and @marybaum, @webcommsat, and @audrasjb for collaborating on the summary.

#core, #dev-chat, #summary

Performance team meeting summary 27 September 2022

Meeting agenda here and the full chat log is available beginning here on Slack.

Announcements

Focus group updates

Images

@adamsilverstein @mikeschroder

GitHub project

Feedback requested

Object Cache

@tillkruess @spacedmonkey

GitHub project

Feedback requested

Site Health

N/A

GitHub project

  • We’re seeking 1-2 POCs for this group; if you’re interested, please comment here or pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” in SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.
  • No updates

Feedback requested

Measurement

N/A

GitHub project

Feedback requested

JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/.

@aristath @sergiomdgomes

GitHub project

  • @aristath: No movement on the JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. front recently, so focusing on general performance improvements instead, including #56636#56637#56654 and just a few minutes ago #56666. The process I’ve been following is to basically run vanilla WP using Xdebug-profiling, examine the results using webgrind and try to reduce the amount of function calls – as well as their cost. Generally small tweaks, with relatively big benefits. Last week #55005 was also merged in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., so overall I believe WP 6.1 contains a lot of nice and impactful performance changes – as highlighted by all the updates from other folks above.

Feedback requested

Infrastructure

@flixos90

GitHub project

Feedback requested

Discussion: SQLite support

@spacedmonkey and @aristath

  • @spacedmonkey: Think this is a great idea and could be useful in core for running unit tests and for other projects like wordpress-wasm. Wonder if the performance team should help take on this problem, even if it is to review the solution and ensure that there’s no performance regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5..
  • @aristath: Understand that testing could be difficult, so currently converting it to work as a pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party in this repository. Trying to convert to something that would make sense for core and then publish in the .org repo as a featured plugin. Hoping if this is in the form of the plugin, more people will test and provide feedback. Also noting that the initial proposal focused on small-to-medium sites, but there’s great potential for growth in other areas as well where large sites can take advantage of SQLite.
    • @spacedmonkey: I’ve forked hyperdb and run very large multisites, can provide context here
    • @aristath: We’ll need lots of context once we get rolling – the prospect of pairing SQLite and hyperdb is very exciting

Our next chat will be held on Tuesday, October 4, 2022 at 11am EDT in the #core-performance channel in Slack.

#core-js, #core-media, #performance, #performance-chat, #summary, #hosting-community

#meta

A Week in Core – September 26, 2022

Welcome back to a new issue of Week in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. Let’s take a look at what changed on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between September 19 and September 26, 2022.

  • 110 commits
  • 173 contributors
  • 66 tickets created
  • 13 tickets reopened
  • 91 tickets closed

The Core team is currently working on the next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope., WP 6.1 🛠 Last week, we entered the betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. cycle, with the release of WP 6.1 beta 1 🚀

Ticketticket Created for both bug reports and feature development on the bug tracker. numbers are based on the Trac timeline for the period above. The following is a summary of commits, organized by component and/or focus.

Code changes

Administration

  • Add new get_views_links method to WP_List_Table#42066
  • Allow to wrap Settings sections with custom HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. content – #17851

Bootstrap/Load

  • Confirm the value of WP_ENVIRONMENT_TYPE before using – #55741
  • Introduce is_*_admin_screen() aliases for is_*_admin() function family – #56400
  • Send HTTPHTTP HTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands. headers after querying posts in WP::main()#56068

Build/Test Tools

  • Enable debugging when rerunning a failed workflow – #56407
  • Increase the timeout value for MacOS jobs – #55652
  • Remove unnecessary --no-interaction option from Composer commands – #54695
  • Temporarily allow the NPM testing workflow to fail – #56615
  • Test building WordPress to run from src first – #55652
  • Update NPM dependencies in default themes – #56641
  • Update NPM dependencies in default themes, part 2 – #56641
  • Update NPM dependencies to their latest versions – #56641
  • Improve how combined assets are generated – #56615

Bundled Themes

  • Import Twenty Twenty-Three, the new default theme for WordPress 6.1 – #56383
  • Twenty Twenty-One: Add a missing HTML comment for CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. notice control – #55725
  • Twenty Twenty-Three: Bug fixes and improvements for beta 2 – #56383
  • Twenty Twenty: Ensure the fallback fonts is applied to all content elements for non-latin languages – #56396

Chore

  • Run browserslits update – #56467

Code Modernization

  • Fix null to non-nullable deprecation in WP_REST_Users_Controller::update_item()#55656

Coding Standards

  • Applying an alignment fix from running composer format#56467
  • Correct alignment in WP_Theme_JSON_Resolver::get_core_data()#55647
  • Move WP_List_Table::get_views_links() to a more appropriate place – #42066
  • Remove extra space in REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. plugins controller test class – #56629
  • Rename WordPress Dependencies APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. class files – #37861, #55647
  • Replace double quote with single quote in test_if_failed_update()#55758
  • Various alignment fixes from composer format#39210, #55443, #56288, #56092, #56408, #56467, #55881

Cron API

  • Add error logging and hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same. to wp-cron.php#56048

Date/Time

  • Correct sanitization of timezone_string in sanitize_option()#56468#53404
  • Correct sanitization of localized default timezone_string in populate_options()#56468
  • Correct timezone dropdown list creation in wp_timezone_choice()#56468
  • Minor tweak to support deprecated timezones on General Settings screen – #56468

Docs

  • Correct @see reference to deprecated_function_run in the _deprecated_function docblockdocblock (phpdoc, xref, inline docs)#56625
  • Correct the wording in wp_lostpassword_url() description – #55646
  • Fix prev_text and next_text parameters type in paginate_links()#56622, #55646
  • Fix wp_get_layout_style() parameter documentation – #55646
  • Increase the specificity of various property documentation – #55646
  • Remove a change that needs to instead be applied in the GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ repo – #55646
  • Typo correction in _load_textdomain_just_in_time() docblock – #55646
  • Updates and corrections to various inline docsinline docs (phpdoc, docblock, xref) added in 6.1 – #55646
  • Use typed array notation for the $locales parameter in pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party update filters – #55646
  • Various improvements and corrections to inline docs – #55646

Editor

  • Remove repetitive calls to file_get_contents() in blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor settings – #56637
  • Remove duplicate use of realpath() in register_block_style_handle()#56636
  • Add box-shadow support for blocks through theme.json files – #56467
  • Add has_archive property to the post types REST endpoint – #56467
  • Add post types property to wp-rest-block-patterns-controller.php – #56467
  • Adds template types, is_wp_suggestion, and fallback template content – #56467
  • Backportbackport A port is when code from one branch (or trunk) is merged into another branch or trunk. Some changes in WordPress point releases are the result of backporting code from trunk to the release branch. block supports (border, color, elements, spacing) from Gutenberg to WP 6.1 – #56467
  • Backport block supports filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. callback, registrations and tests to 6.1 – #56467
  • Backport hooks to filter theme.json data from Gutenberg to 6.1 – #56467
  • Fix function name case in wp_default_packages_inline_scripts()#56467
  • Fix missing frontend section presets output – #56467
  • Fix spacing property generation in flow layout type – #56467
  • Fix text zoom on link popup editor – #53174
  • Improve block loading PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher performance – #55005
  • Improves layout block support in wp_get_layout_style()#56467
  • Introduce spacing presets in global style properties – #56467
  • Introduces fluid typography and uses Style Engine – #56467
  • Make template names and descriptions dynamic – #56467
  • Revert [54305]
  • Sync changes from the Gutenberg plugin 14.1 release – #56467

External Libraries

  • Update the jQuery UIUI User interface library to version 1.13.2 – #56239
  • Update the jQuery library to version 3.6.1 – #56451

General

  • Correct the fallback logic in apache_mod_loaded()#56010
  • Ensure adminadmin (and super admin) notices are properly displayed on Site Health layout – #54624
  • Pass $action to nonce_life filter – #35188
  • Remove file_exists() checks after calling realpath()#56654
  • Replace Codex links with their HelpHub counterparts – My Sites screen – #48987
  • Revert [54225]#48987
  • Throw a more descriptive error when templates are not found – #36631

Help/About

  • Add a help tab in Theme Install screen for the new “Block Themes” search filter – #56405
  • Make translator comments version agnostic and make version translatable on the About page – #54741
  • Remove an unwanted whitespace in a Theme Install screen help tab string – #56405

I18Ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill.

  • Remove code tags from translatable strings in WP_List_Table::get_views_links()#42066
  • Update list of continents and cities for the timezone selection – #56468

Login and Registration

  • Add a new filter for the lost password link – #55388

Media

  • Add caching to wp_count_attachments()#55227
  • Change alt attribute field to textarea in media library – #50066
  • Fix JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. TypeError with video playlists and native video – #47513
  • Respect EXIF Rotations – #54937
  • Revert WebP generation – #55443

Menus

Networknetwork (versus site, blog) and Sites

  • Move global_terms_enabled() to its proper final resting place – #21734
  • Officially remove global terms – #21734
  • Store main site id of a network in network options – #55802

Posts, Post Types

  • Fix WP_Query parameter used by get_page_by_title()#56609, #36905
  • Post title should not be translatable in get_user_data_from_wp_global_styles method – #55392
  • Update new wp_post_class_taxonomies filter name for consistency – #37114
  • Cache get_page_by_title()#36905
  • Coding standards fixes following [54234] – #36905
  • Prevent get_sample_permalink() modifying the post object – #54736

REST API

  • Fix check for has_archive inclusion – #56618

Role/Capability

  • Add a new update_role function – #54572

Security

  • Salting functions: translate the phrase “put your unique phrase here” – #55937

Shortcodes

  • Reverse wrapping of apply_shortcodes() and do_shortcode()#55883
  • Revert default filter callback changes from apply_shortcodes to do_shortcode#55883

Site Health

  • Improve the details provided by the REST API checks – #54617

TaxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. https://codex.wordpress.org/Taxonomies#Default_Taxonomies.

  • Standardise the format used to describe arguments passed to actions and filters inside wp_insert_term() and wp_update_term()#55441

Tests

  • Add tests with deprecated timezone strings – #56468
  • Delete Link Manager plugin after running REST API plugins controller tests – #56629
  • Remove empty directory in WP_UnitTestCase_Base::rmdir()#55652
  • Remove nested empty directories in WP_UnitTestCase_Base::rmdir()#55652
  • Replace the timezone used in date/time tests – #56468
  • Reset timezone-related options if the tests change them – #56468
  • Revert removing empty directory in WP_UnitTestCase_Base::rmdir() for now – #55652, #56629
  • Simplify the data provider for testing whether KSES globals are defined – #55652

Text Changes

  • Remove self-reference (“we”) in WordPress Admin – #55758, #46057

Themes

  • Import Twenty Twenty-Three is now the default theme – #56383
  • Relocate actions firing prior to and after template loading – #54541

Tools

  • Fix running build scripts on Windows does not generate CSSCSS Cascading Style Sheets. files for blocks – #56616
  • Simplify syncing core blocks from Gutenberg plugin to Core – #56179

Upgrade/Install

  • Add plugin URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org to the automatic update email – #53049
  • Update sodium_compat to v1.19.0 – #56653
  • Use “placeholder” for example values in setup-config.php – #56365

Users

  • Make wp_list_authors() and wp_list_users() filterable – #17025

i18n

  • Ensure empty strings are consistently translated to ''#55941

Props

Thanks to the 173 (!!) people who contributed to WordPress Core on Trac last week: @costdev (31), @SergeyBiryukov (23), @audrasjb (19), @jrf (12), @hellofromTonya (11), @peterwilsoncc (9), @bernhard-reiter (8), @desrosj (8), @mukesh27 (7), @mcsf (5), @aristath (5), @oandregal (5), @andrewserong (5), @kebbet (5), @johnbillion (4), @gziolo (4), @Clorith (4), @afercia (4), @dd32 (4), @johnjamesjacoby (4), @adamsilverstein (4), @ramonopoly (4), @ntsekouras (4), @rafiahmedd (4), @joedolson (4), @sabernhardt (4), @isabel_brison (3), @spacedmonkey (3), @antonvlasenko (3), @madhudollu (3), @poena (3), @nacin (3), @dingo_d (2), @scribu (2), @jameskoster (2), @onemaggie (2), @scruffian (2), @chaion07 (2), @DrewAPicture (2), @wonderboymusic (2), @glendaviesnz (2), @Presskopp (2), @robinwpdeveloper (2), @czapla (2), @cbravobernal (2), @marcyoast (2), @oliverstapelfeldt (2), @wildworks (2), @clorith (2), @mikachan (2), @ironprogrammer (2), @critterverse (2), @beafialho (2), @hilayt24 (2), @colorful tones (1), @daisyo (1), @dianeco (1), @bgardner (1), @greenshady (1), @anariel-design (1), @amjadr360 (1), @joen (1), @pbiron (1), @thijso (1), @khokansardar (1), @ramon-fincken (1), @JosVelasco (1), @ChrisHardie (1), @Ipstenu (1), @monolithon (1), @pento (1), @noisysocks (1), @joehoyle (1), @wparslan (1), @JavierCasares (1), @edent (1), @shetheliving (1), @Rahmohn (1), @herregroen (1), @jffng (1), @NomNom99 (1), @kafleg (1), @garrett-eclipse (1), @chaton666 (1), @krupalpanchal (1), @haritpanchal (1), @marybaum (1), @giuseppemazzapica (1), @martinkrcho (1), @pbearne (1), @dwainm (1), @pcfreak30 (1), @igmoweb (1), @jorbin (1), @jonny-s (1), @boonebgorges (1), @kishanjasani (1), @Dharm1025 (1), @thelovekesh (1), @tanvirul (1), @soean (1), @richtabor (1), @pbking (1), @mtias (1), @luminuu (1), @juhise (1), @maksimkuzmin (1), @kraftbj (1), @joyously (1), @hellofromtonya (1), @tobifjellner (1), @rehanali (1), @engahmeds3ed (1), @petitphp (1), @presstoke (1), @ocean90 (1), @here (1), @courane01 (1), @davidbaumwald (1), @vikasprogrammer (1), @maximemeganck (1), @gabri3lmarques (1), @dlh (1), @jsnajdr (1), @Camwynsp (1), @draganescu (1), @mamaduka (1), @dmsnell (1), @sergeybiryukov (1), @azaozz (1), @zieladam (1), @paragoninitiativeenterprises (1), @ndiego (1), @felipeelia (1), @lopo (1), @manooweb (1), @Chouby (1), @hugodevos (1), @Boniu91 (1), @krishaweb (1), @timothyblynjacobs (1), @mburridge (1), @palmiak (1), @jeherve (1), @chriscct7 (1), @ryan (1), @ross_ritchey (1), @griffinjt (1), @namithjawahar (1), @whaze (1), @joostdevalk (1), @jonoaldersonwp (1), @webcommsat (1), @swissspidy (1), @schlessera (1), @afragen (1), @antpb (1), @mciampini (1), @mboynes (1), @Enchiridion (1), @oglekler (1), @jorgefilipecosta (1), @cbirdsong (1), @aaronrobertshaw (1), @youknowriad (1), @TimothyBlynJacobs (1), @chetan200891 (1), @Mte90 (1), @kevinB (1), @matveb (1), @mikeschroder (1), @tbember (1), and @tobiasbg (1).

Congrats and welcome to our 15 (!) new contributors of the week: @marcyoast, @colorfultones, @anariel-design, @amjadr360, @thijso, @khokansardar, @edent, @here, @maximemeganck, @gabri3lmarques, @Camwynsp, @hugodevos, @ross_ritchey, @cbirdsong, @tbember ♥️

Core committers: @sergeybiryukov (28), @audrasjb (23), @desrosj (20), @davidbaumwald (13), @hellofromtonya (7), @jorgefilipecosta (6), @johnbillion (5), @gziolo (5), @peterwilsoncc (5), @joedolson (4), @spacedmonkey (2), @antpb (1), @clorith (1).

#6-1, #core, #week-in-core

Editor Chat Agenda: 28th September 2022

Facilitator and notetaker: @ajitbohra.

This is the agenda for the weekly editor chat scheduled for Wednesday, September 28th, 2022, at 03:00 PM GMT+1.

This meeting is held in the #core-editor channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..

If you cannot attend the meeting, you are encouraged to share anything relevant to the discussion:

  • If you have an update for the main site editing projects, please feel free to share as a comment or come prepared for the meeting itself.
  • If you have anything to share for the Task Coordination section, please leave it as a comment on this post.
  • If you have anything to propose for the agenda or other specific items related to those listed above, please leave a comment below.

#agenda#core-editor#core-editor-agenda#meeting

Performance Chat Agenda: 27 September 2022

Here is the agenda for this week’s performance team meeting scheduled for September 27, 2022, at 15:00 UTC.


This meeting happens in the #core-performance channel. To join the meeting, you’ll need an account on the Make WordPress Slack.

#agenda, #meeting, #performance, #performance-chat

Roadmap to 6.1: Core Companion

This post is meant to supplement the broader 6.1 roadmap and focuses on features that are now planned in addition to the ones previously worked on that now have clarity and momentum. Please take both posts into consideration when thinking about the upcoming release cycle and where you might be able to get involved. Keep in mind that for much of what’s mentioned in this post, work will continue beyond 6.1 and into future releases, providing ample opportunity to contribute. 

For more information about current feature projects, check out the Feature Projects overview page

Theme Improvements

This year’s default theme is further embracing blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. themes by offering various opinionated style variations from community members. This will give more folks a chance to enjoy the latest and greatest. Read the latest update here announcing the 10 style variations planned for Twenty Twenty-Three. 

Outside of the default theme, the following improvements are also underway and help set the tone for additional changes: 

Performance initiatives 

Various performance initiatives are underway including, but not limited to the following: 

You can also explore other ongoing efforts being explored in the Performance Lab plugin to test the modules to get their benefits before they become available in WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. Join #core-performance to get involved. 

PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8.2 compatibility 

The work is continuing to improve compatibility with PHP 8.0 and 8.1 while also preparing for PHP 8.2 due out at the end of November. While 6.1 won’t be PHP 8.2 compatible, efforts are still needed today to get us there in future releases. To get involved with this work, please review the overarching tracking issue, the current open issues, and join #core-php.

Rollback and PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party Dependencies 

In an effort to offer a more robust rollback and dependencies experience when a problem is encountered during an update, work is underway to test the current experience in hopes of being incorporated into Core. 

Specifically, hosting feedback is needed but all contributions are welcomed. You can find the Plugin Dependencies feature plugin here. Please put comments, feedback, bugs, etc. as new issues in the Plugin Dependencies repo and join #core-auto-updates.

Keep in mind that the rollback work is for plugins and themes whereas the dependencies is just for plugins currently. 

Site Health Improvements

To help guide more folks to upgrade their versions of PHP and offer more relevant warnings about high urgency issues, messaging improvements are in progress; please follow along in this trac issue and join #core-site-health.

Introducing and refining hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same.

Since Hooks continue to make up the foundation for how plugins and themes interact with WordPress Core, work continues to expand and refine what’s offered both to allow Core to accomplish more and for extenders to do the same. For 6.1, this includes the following:

REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. Improvements

Since the REST API is the foundation of the WordPress block editor and provides a way for you to create your own interface, work continues to expand what’s possible when interacting with your site’s data:

For more information about the REST API, please review this developer documentation and join #core-restapi.

Miscellaneous improvements and bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. fixes

While some work fits nicely into general categories, there’s plenty more work underway that cuts across many different parts of the WordPress ecosystem. This includes everything from database component items to internationalization to Cron API and more. For a full list of what’s planned for 6.1, please review this trac query.

If any efforts were not mentioned here that should be, please leave a comment below so we can all be made aware. 

Thanks to @cbringmann @annezazu @sergeybiryukov for helping craft and review this post. 

Summary, Dev Chat, September 21, 2022

Notes from the weekly WordPress Developers Chat, which takes place on Wednesdays at 20:00 UTC in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. channel of the Make WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.. All are welcome to attend.

To view the content from any of the Slack links listed, you will need a Making WordPress Slack account to view.

1. Welcome

Dev Chat is for everyone. This meeting is not for making decisions but for sharing updates about the next releases, TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets, component maintainers and more.

Meeting preparation and co-hosts: Props to @webcommsat and @marybaum.

The agenda is structured to help new contributors or those new to core or releases follow along more easily, and to make it easier for notetakers and for accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility).

The meeting agenda

Link to the start of the meeting on Slack

2. Announcements

  • WordPress 6.1 BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 is now available 
    https://wordpress.org/news/2022/09/wordpress-6-1-beta-1-now-available/
    Thank you to everyone involved and contributors who came to test at the earlier release party.

3. Blogblog (versus network, site) Posts and important links

Twenty Twenty Two (TT2) theme accessibility discussion

Start of the discussion on Slack

@annezazu highlighted a cross-team discussion on releasing a new version of Twenty Twenty Two theme so that the committers could add the accessibility-ready label to it ahead of 6.1. This was raised as a possibility as it would be the first blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. theme with that label, opening the door for more people to be able to explore using various Full Site Editing (FSE) features.

@audrasjb: if adding the accessibility-ready tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) to TT2 is that important, then suggest to only release this change (the above commit), and not all the other changes milestoned in 6.1.

@joedolson:
– It’s a minor fix, but the theme is less accessible right now than it will be when 6.1 is available.
– elates to the Trac ticketticket Created for both bug reports and feature development on the bug tracker. #56067 query navigation arrow icons. Accessibility image requirements
– confirmed the theme would not pass the accessibility-ready criteria with this bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority..

Actions:

  • @annezazu: The decision feels clear to me to wait for 6.1.
  • Follow the discussion on the accessibility-ready tag for the TT2 theme: these are mostly in the Trac ticket #55172. @annezazu will add a recap of the discussion on the ticket.

4. Releases

a) The next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope. is 6.1.
The Call for Testing for 6.1 was published earlier today.
Actions: The post on testing is really valuable part of the process, and lots of useful information on how to take part.

@jeffpaul: main update from the squad is that the Beta 1 is available and testing is strongly desired please and thanks!
b) @jeffpaul highlighted the following issues to continue discussion on the relevant Trac tickets: should the contributors revert them before Beta 2 on September 27? Is there some other more optimal result? Tickets #56400 and #19898.

Actions request: read and add directly on the tickets, particularly to comment 8 on ticket #56400 on the discussion on the naming of things.


c) Useful links and next release cycle dates
WordPress 6.1 Development cycle
Bug scrub schedule for 6.1

Beta 2 release will be next Tuesday, September 27, 2022 starting at 16:00 UTC in the #core Slack channel@jeffpaul: All are welcome, any and all testing will be welcome.

d) Discussion on date of the 6.1 release
Slack thread

On today’s agenda, comment from @marctison75 relating to the date of the 6.1 release:
“…are you aware that the release day (November 1, 2022) is a public holiday in many European countries (France, Italy, Spain, Belgium, Portugal, Germany, Croatia, Austria…)?”

Discussion points focused on:

  • this date appears to be a public holiday that affects many countries. It is also a public holiday in many countries in Europe, parts of South America, Africa, and further.
  • sensitivity to public holidays given comments about avoiding weekends
  • uncertainty about what dates could be changed at this time. Need to avoid the US elections
  • decision to be made by the release squad to determine what’s best, discussion valuable to take place in core/ dev chat. Availability of release squad members needed will be the key factor
  • question on whether the release date could be moved by just one day to November 2, 2022, like for Beta 1?
  • traditionally Tuesday’s are the planned release days based on past experience
  • primary concern is surrounding core auto-updates:
    • a lot of hosts are likely to auto-update irrespective of a public holiday
    • generally hosts auto-update when they have people on site to handle any issues so weekends are avoided
    • consider hosts outside the US too
    • a host may auto-update without realizing the implications for the users and any public holidays they have
    • auto-update can be enabled by any site owner via update-core.php or by filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output., not only hosts
  • avoid days too close to the weekend.
  • Monday is dry run day, better to avoid dry run falling on a Sunday

Actions:
@davidb: Let the Release coordinators discuss in 6.1 channel and send up the flagpole if necessary. There’s never a best time for to these things. It’s always a compromise.

@jeffpaul: Ok, we will work to sort out with release leads whether an alternate day for the release may be desired, though I imagine folks would complain about Monday of that week with the holiday following.  More to come hopefully by next dev chat.

@webcommsat thanked those who had raised the issue and all the comments. Asked release squad leads to also add a comment to the dev chat summary with any decision.

5. Component maintainers and tickets

@sergeybiryukov: Date/Time: Some fixes were made to ensure that timezone strings deprecated in newer PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher versions are handled correctly by WordPress. Thanks @jrf and @costdev. Ticket #56468 for more details.

Build/Test Tools, General, I18Ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill.: Permalinks: No major news this week 

@webcommsat: About/ Help and Quick/ Bulk Edit: couple of issues we are trying to move forward. More on Monday in our working session.

6. Open Floor

a) @marybaum gave a welcome to our new contributors who helped with dev chat at WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. US!

b) Query on the Canonical Plugins post

@costdev: A couple of questions that others may know the answer to:

  • Is this a decision or a proposal?
  • What does this mean for WebP? Is it going into Core at all, or has it been blocked?
  • What does this mean for other in-development features for Core?
  • Do we have a criteria for what is acceptable for Core, and what should be a Canonical pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party? Or are all features Canonical Plugins unless they’re a “runaway success” as Matt said in the post?

@jeffpaul gave a reply to these questions from his perspective:

  • Is this a decision or a proposal?
    • @jeffpaul: It’s from Matt, so I would read that as a decision.
  • What does this mean for WebP? Is it going into Core at all, or has it been blocked?
    • @jeffpaul: It’s been reverted from 6.1 and seems best suited as a Canonical Plugin, based on Matt’s comment in WebP in Core for 6.1 of “This is excellent territory for a canonical plugin”.
  • What does this mean for other in-development features for Core?
    • @jeffpaul: Can you provide an example as I imagine it could depend based on what you’re referencing?@costdev: Some examples would be Rollback, Plugin Dependencies, WP Notify
    • @afragen: Question – Is Matt or leadership going to let us know whether existing feature projects are going to be acceptable for core or live their life as canonical plugins?
    • @jeffpaul: yeah that’s where I was headed… I think if we as core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org. can collect a list of those outstanding proposals, then we could look to Core Team Reps to route those through Josepha/Matt for input as to whether they’re still ok to continue towards core merge proposal or better suited as a canonical plugin.
  • Do we have a criteria for what is acceptable for Core, and what should be a Canonical plugin? Or are all features Canonical Plugins unless they’re a “runaway success” as Matt said in the post?
    • @jeffpaul: This is all still a new process for many of us I imagine, but if I had to guess I suspect we might want to update our core proposal “process” to ensure there’s a check early on with Matt/Josepha for direction on “this is good for core merge proposal” or “this is best as a canonical plugin” so we know early on how best to be building out the feature.
    • @jeffpaul: answering these on my own behalf with no input from Matt, Josepha, lead devs, committers, or anyone else of significance here in core.
  • @costdev said it might be useful to have the issue discussed with Core during a dev chat open floor to give a little heads up, understand the reasoning of the decision, and a Q&A prior to the public announcement.
    • @jeffpaul: I suspect it may be more likely that we get answers from Matt async than waiting for a week where his schedule is free for dev chat (and one where others can be present to participate).  As such, it may be better to gather questions folks have, again maybe via coordination with Core Team Reps, and present those to Matt/Josepha to get responses async to help guide our actions here as core contributors.

c) WordPress GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/

If you are a member of the WordPress GitHub organization, you should have received a message to enable Two Factor Authentication if it is currently disabled on your account. Please check your messages and settings.

The next dev chat will be on Wednesday September 28, 2022 at 20:00 UTC.

Props to @webcommsat for the summary, @costdev and @marybaum for the review.

#6-1, #core, #dev-chat, #summary

Core Editor chat summary: 21st September 2022

This post summarises the weekly editor chat meeting (agenda here) held on 2022-09-21 14:00 UTC in Slack. Moderated by @get_dave.

Status Updates

  • Version 14.1.0 of the GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party was released. You can read what’s new in Gutenberg 14.1.0.
  • Following this, Minor release 14.1.1 was released 2 days ago to fix a bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. with searching for blocks.
  • Zooming out a bit, the WordPress 6.1 release schedule is proceeding. 
    • BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 was supposed to be yesterday but it turns out that’s been moved to today (21st September 2022).
    • Just in case it moves again, you can check out the full development cycle plan.
  • The last version of Gutenberg that made it into WP 6.1 was 14.1 RC1.

Updates based on updated scope for site editing projects

Task Coordination

The following items were shared by folks to update us on what work is in progress or where help is needed:

@alexstine (not present – shared from agenda):

    @annezazu:

    • Working on
      • the FSE Program Testing Call #17: Guiding the Gutenberg Gallery (everyone is welcome to participate).
      • co-coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. editor triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. duties for 6.1.
      • a Core related roadmap companion post for Make Core with a few folks.
      • a core editor improvement post on the various design tools coming to 6.1.
      • a draft of an accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) improvements roundup for 6.1.
    • Lots of writing, testing, and sharing info with folks where I can!

    @mamaduka – I am planning to start work on the new entity permission selector; it would be like `canUser` but easier to use with entities.

    @get_dave:

    • I’m switching focus to work on bugs. Found some interesting issues around LinkControl and also the Navigation blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience..
    • Continuing to iterate in the background on using slugs for Navigation blocks, and also ability to add Custom Labels to the List View.

    @colorful-tones:

    • I’m really keen on trying to review the latest roadmap for WebFonts APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. and love the organized outline of features, but almost feel overwhelming and hard to know where one might focus on reviewing and providing feedback. So, any guidance is appreciated.
    • @hellofromtonya responded to say: right now, it’s blocked until the re-architecturing work is done.

    @bph:

    • For 6.1 we, Michael and I, added the label needs-dev-note to quite a few PRs in our first round of triaging.
    • Next steps is to add them in topical order to the Dev Note tracking issue. It might take another few more days to finish it.
    • Please continue to leave comments on the issue, or the PRs. I’ll catch up with you quickly. 

    Open Floor

    The full Open Floor discussion is available on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.. It was a quiet meeting…

    Critical Bug Reporting for WordPress 6.1

    @ndiego said:

    As @annezazu alluded to, right now, my main focus is testing, testing, testing. But we need more help to ensure 6.1 is as polished as possible. I just wanted to reiterate that if anyone finds a critical bug, especially if it’s related to 6.1 features, please add it to the 6.1 Project Board and we will triage it from there.

    Thanks to everyone who attended the meeting.

    #core-editor, #core-editor-summary, #meeting, #meeting-notes, #summary

    WordPress 6.1 Beta 1 delayed

    WordPress 6.1 BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 was originally scheduled to be released today (Tuesday, September 20th) starting at 16:00 UTC. However, during the release party in #core those assembled identified an NPM test failure and three GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ PRs (#3221#3254#3255) that were included in the 6.1 Walkthrough and were all deemed ideally resolved and properly part of the 6.1 Beta 1 release.

    The decision was made to delay the 6.1 Beta 1 release party to tomorrow, Wednesday, September 21st at 16:00 UTC to allow time to resolve the NPM test failure and wrap up reviews and commits on the Gutenberg PRs.

    The rest of the 6.1 release cycle schedule is unchanged.

    #6-1, #beta

    A Week in Core – September 19, 2022

    Welcome back to a new issue of Week in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. Let’s take a look at what changed on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between September 12 and September 19, 2022.

    • 94 commits
    • 139 contributors
    • 53 tickets created
    • 2 tickets reopened
    • 71 tickets closed

    The Core team is currently working on the next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope., WP 6.1 🛠

    Ticketticket Created for both bug reports and feature development on the bug tracker. numbers are based on the Trac timeline for the period above. The following is a summary of commits, organized by component and/or focus.

    Code changes

    Administration

    • Add new get_views_links method to WP_List_Table#42066

    Build/Test Tools

    • Move the basic get_block_templates() test to the dedicated file – #55652
    • Rename the test for pre_option filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. to match the filter name – #37930
    • Rename the test for wp_guess_url() to match the function name – #36827
    • Replace the timezone used in date/time tests – #56468
    • Reset timezone-related options if the tests change them – #56468#55388
    • Simplify the data provider for testing whether KSES globals are defined – #55652
    • Update the test for respecting the post type in get_block_templates()#55881

    Bundled Themes

    • Fifteen: Ensure border-bottom styles are applied to the Button BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience.#55006, #55824
    • Nineteen: Define underline thickness for links – #45925
    • Seventeen: Ensure long text wraps correctly in the Button Block – #55783
    • Twenty-One: Add a missing HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. comment for CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. notice control – #55725
    • Twenty-One: Fix Heading Block alignment when nested in Cover Block – #56050
    • Twenty-One: Remove WooCommerce related CSSCSS Cascading Style Sheets. selectors – #56366
    • Twenty-Two: Add “AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Ready” tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) to theme in repository – #55172
    • Twenty: Correctly align Social Icons block in the editor – #55987
    • Twenty: Ensure Latest Posts block set to 2 columns displays accordingly in the Editor – #56175
    • Twenty: Ensure headings styles are consistent between editor and front-en – #56194
    • Twenty: Ensure link color is inherited from paragraph in the editor – #56214
    • Twenty: Fix Heading Block alignment when nested in Cover Block – #56049
    • Twenty: Fix Social Links widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. alignment – #56474
    • Twenty: Improve support for Post Title block alignment – #56167

    Code Modernization

    • Add AllowDynamicProperties attribute to all (parent) classes – #56513, #56034
    • Fix autovivification from false to array in WP_Scripts::localize()#55656
    • Pass correct value to parse_url() in WP_Customize_Manager::get_return_url()#55656
    • Reduce CSS float usage in wp-adminadmin (and super admin) – Timezone settings – #55557
    • Remove -webkit-appearance CSS declarations – #38431
    • Replace deprecated string interpolation patterns – #55787

    Coding Standards

    • Move WP_List_Table::get_views_links() to a more appropriate place – #42066
    • Remove unwanted spaces in the WP_Block_Type class
    • Replace double quote with single quote in test_if_failed_update()#55758
    • Various alignment fixes from composer format#39210, #55443, #56288, #56092, #56408, #56467, #55881

    Comments

    • Make wp_required_field_indicator() and wp_required_field_message() output filterable – #56389, #54394
    • Remove aria-hidden="true" attribute for visible text in comment template – #55717

    Docs

    • Add missing @since history in Gallery ShortcodeShortcode A shortcode is a placeholder used within a WordPress post, page, or widget to insert a form or function generated by a plugin in a specific location on your site. function – #56206, #55646
    • Clarify documentation for the nav_menu_item_id filter – #56574, #55646
    • Clarify that get_page_template() doesn’t work on block themes – #56394, #55646
    • Clarify the $allowed_protocols default value in various KSES functions – #56580
    • Correct @return type for WP_Block_Parser::parse()#56581
    • Correct @return value for wp_get_http_headers()#54225, #55646
    • Correct @since tags for some block parser properties and methods – #56581
    • Correct the wording in wp_lostpassword_url() description – #55646
    • Revert the WP_Block_Parser documentation changes now – #56581
    • Typo correction in _load_textdomain_just_in_time() docblockdocblock (phpdoc, xref, inline docs)#55646
    • Update wp_rand docblock to clarify that it returns a non-negative number – #15089
    • Use third-person singular verbs in Media APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. function descriptions, as per docblocks standards – #55646
    • Use third-person singular verbs in Template Loading functions descriptions, as per docblocks standards – #55646

    Editor

    • Add new render property in block.json for block types – #53148
    • Allow registering multiple items for all supported asset types – #56408
    • Backportbackport A port is when code from one branch (or trunk) is merged into another branch or trunk. Some changes in WordPress point releases are the result of backporting code from trunk to the release branch. Style Engine API functions, classes and tests – #56467
    • Backport build_query_vars_from_query_block changes from GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ repository – #56467
    • Backport wp_theme_element_class_name() alias – #56467
    • Backport block supports (border, color, elements, spacing) from Gutenberg to WP 6.1 – #56467
    • Backport block supports filter callback, registrations and tests to 6.1 – #56467
    • Backport foundation for Layout block support refactor (part 1) – #56467
    • Backport foundation for Layout block support refactor (part 1) – #56467
    • Finalize the theme_json_get_style_nodes hook name – #56467
    • Fix function name case in wp_default_packages_inline_scripts()#56467
    • Fix get_block_templates() to get templates for a post type – #55881
    • Fix text zoom on link popup editor – #53174
    • Hide query loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. pagination link arrows from assistive technologyAssistive technology Assistive technology is an umbrella term that includes assistive, adaptive, and rehabilitative devices for people with disabilities and also includes the process used in selecting, locating, and using them. Assistive technology promotes greater independence by enabling people to perform tasks that they were formerly unable to accomplish, or had great difficulty accomplishing, by providing enhancements to, or changing methods of interacting with, the technology needed to accomplish such tasks. https://en.wikipedia.org/wiki/Assistive_technology#56067
    • Persist preferences in user metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress.#56467
    • Revert [54159] – #56467

    External Libraries

    • Update the jQuery UIUI User interface library to version 1.13.2 – #56239
    • Update the jQuery library to version 3.6.1 – #56451

    Feeds

    • Add a set of fine-grained filters to disable the different types of feed links separately – #55904

    General

    • Add a new filter for the_posts_pagination_args#53392
    • Correct path replacement regex in wp_guess_url#36827
    • Ensure admin notices are properly displayed on Site Health layout – #54624
    • Pass $action to nonce_life filter – #35188
    • Replace Codex links with their HelpHub counterparts – My Sites screen – #48987
    • Replace Codex with HelpHub in WordPress readme – #48987

    Help/About

    • Make translator comments version agnostic and make version translatable on the About page – #54741
    • Remove .hidden class when the Help Tab panel is displayed – #27697

    I18Ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill.

    • Remove code tags from translatable strings in WP_List_Table::get_views_links()#42066

    Login and Registration

    • Access improvements to networknetwork (versus site, blog) signup – #40361
    • Required fields in network registration – #54344

    Options, Meta APIs

    • Add a new pre-option filter – #37930

    Plugins

    • Visually align pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party cards in Plugin Install screen – #55721, #55272

    Posts, Post Types

    • Improve performance of the get_user_data_from_wp_global_styles method – #55392
    • Update new wp_post_class_taxonomies filter name for consistency – #37114

    REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/.

    • Add support for settings to specify their own additionalProperties – #56493

    Role/Capability

    • Add a new update_role function – #54572

    Site Health

    • Adjust margins for the Site Health dashboard widget – #56369
    • Improve the description for Authorization headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. checks – #54508
    • Improve the details provided by the REST API checks – #54617
    • Add a check to wp_check_php_version() whether the current PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher version is lower than the next (desired) minimum version, Set the next desired minimum PHP version to 7.2, Use that check to update the warnings in the wp_dashboard_php_nag() widget, and on the Site Health screen – #56199
    • Add a menu bubble with the critical issues count to the Tools -> Site Health submenu – #56199

    Text Changes

    • Remove self-reference (“we”) in WordPress Admin – #55758, #46057

    Themes

    • Implement file description for theme.json#55325
    • Introduces block-based template parts for Classic themes – #56467

    Upgrade/Install

    • Add plugin URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org to the automatic update email – #53049
    • Remove _copy_dir() function as originally intended – #55712, #17173
    • Update sodium_compat to v1.18.0 – #56564

    Props

    Thanks to the 139 (!!) people who contributed to WordPress Core on Trac last week: @audrasjb (29), @costdev (25), @sabernhardt (18), @SergeyBiryukov (15), @bernhard-reiter (10), @mukesh27 (10), @jrf (8), @hellofromTonya (6), @peterwilsoncc (6), @Clorith (5), @joedolson (5), @aristath (4), @desrosj (4), @kajalgohel (4), @afercia (4), @poena (4), @kebbet (4), @tahmidulkarim (3), @joyously (3), @spacedmonkey (3), @zieladam (3), @ramonopoly (3), @andrewserong (3), @multidots1896 (3), @robinwpdeveloper (3), @scruffian (2), @isabel_brison (2), @aaronrobertshaw (2), @noisysocks (2), @mamaduka (2), @netweb (2), @neychok (2), @umesh84 (2), @mrfoxtalbot (2), @Chouby (2), @webcommsat (2), @smit08 (2), @fabiankaegy (2), @ironprogrammer (2), @azaozz (2), @ocean90 (2), @antonvlasenko (2), @NomNom99 (2), @dd32 (2), @Presskopp (2), @pbiron (2), @luisherranz (1), @juliemoynat (1), @harshvaishnav (1), @ayeshrajans (1), @markjaquith (1), @knutsp (1), @welcher (1), @grandeljay (1), @bhrugesh12 (1), @annezazu (1), @mikeschroder (1), @ryokuhi (1), @utz119 (1), @kjellr (1), @bph (1), @matveb (1), @kamig478 (1), @lopo (1), @robertghetau (1), @NathanAtmoz (1), @voldemortensen (1), @jdgrimes (1), @curdin (1), @petitphp (1), @flixos90 (1), @jamesckemp (1), @paragoninitiativeenterprises (1), @nidhidhandhukiya (1), @kmadhak (1), @kapilpaul (1), @pbearne (1), @timothyblynjacobs (1), @dlh (1), @afragen (1), @devtanbir (1), @mhkuu (1), @TobiasBg (1), @cfinke (1), @sharjeelkhanvmi (1), @chaton666 (1), @davidbaumwald (1), @JosVelasco (1), @tobiasbg (1), @shetheliving (1), @dingo_d (1), @rafiahmedd (1), @wparslan (1), @monolithon (1), @glendaviesnz (1), @Ipstenu (1), @ChrisHardie (1), @oliverstapelfeldt (1), @maksimkuzmin (1), @henrywright (1), @gziolo (1), @juhise (1), @Dharm1025 (1), @garrett-eclipse (1), @jonny-s (1), @jorbin (1), @DrewAPicture (1), @dwainm (1), @giuseppemazzapica (1), @marybaum (1), @johnjamesjacoby (1), @SteelWagstaff (1), @allisonplus (1), @maartenj (1), @haritpanchal (1), @danfarrow (1), @allancole (1), @bengreeley (1), @cbravobernal (1), @ntsekouras (1), @manfcarlo (1), @helen (1), @grabmedia (1), @dilipbheda (1), @armondal (1), @youknowriad (1), @hakre (1), @talldanwp (1), @oandregal (1), @aljullu (1), @andregal (1), @adamsilverstein (1), @rolfsiebers (1), @celloexpressions (1), @laurent22777 (1), @tobifjellner (1), @jeremyfelt (1), @westi (1), and @annabansaghi (1).

    Congrats and welcome to our 18 (!!) new contributors of the week: @tahmidulkarim, @harshvaishnav, @jamesckemp, @kmadhak, @devtanbir, @mhkuu, @sharjeelkhanvmi, @monolithon, @oliverstapelfeldt, @maksimkuzmin, @jonnys, @dwainm, @giuseppemazzapica, @allisonplus, @maartenj, @grabmedia, @armondal, @laurent22777 ♥️

    Core committers: @audrasjb (40), @sergeybiryukov (24), @davidbaumwald (9), @hellofromtonya (5), @joedolson (3), @desrosj (3), @clorith (3), @gziolo (3), @azaozz (2), @spacedmonkey (1), @timothyblynjacobs (1).

    #6-1, #core, #meta5999, #meta6322, #week-in-core