A Week in Core – November 21, 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 November 14 and November 21, 2022.

  • 21 commits
  • 29 contributors
  • 76 tickets created
  • 50 tickets reopened
  • 4 tickets closed

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 missing escaping for a few strings used as HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. attributes – #57093

Build/Test Tools

  • Add additional details why MacOS jobs are separate – #56793
  • Improve how Composer dependencies are installed – #53841
  • Various minor 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/ Action improvements – #56793

Bundled Themes

  • Twenty Seventeen: Improve letter-spacing reset for non-latin alphabets – #56994

Coding Standards

  • Fix WPCSWPCS The collection of PHP_CodeSniffer rules (sniffs) used to format and validate PHP code developed for WordPress according to the WordPress Coding Standards. May also be an acronym referring to the Accessibility, PHP, JavaScript, CSS, HTML, etc. coding standards as published in the WordPress Coding Standards Handbook. issues in wp-admin/install-helper.php#43761

Docs

  • Correct type for the $post parameter of the {$adjacent}_post_link 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.#57047
  • Documentation for postTypes pattern property
  • Fix typo and improve DocBlockdocblock (phpdoc, xref, inline docs) formatting in wp-admin/install-helper.php#56792
  • Fix typo in the WP_Theme_JSON::PRESETS_METADATA constant description – #56792
  • Minor DocBlock edits for get_adjacent_post() and related functions – #56792
  • Split the “main part” comment in wp-login.php into two lines – #56843
  • Typo correction in get_registered_nav_menus() docblock – #57101, #56792
  • Update wp_count_posts and wp_count_attachments filter descriptions – #56792
  • Update various DocBlocks and inline comments per the documentation standards – #56792

Help/About

  • Fix inconsistency in auto-updates help tabs – #56921

Site Editor

  • Show correct theme per template or template part – #55437

Text Changes

  • Improve the wording of the email sent to confirm site deletion – #56921

Upgrade/Install

  • Delete the comments-query-loop folder in wp-includes/blocks#57080
  • Remove bundled theme files from $_old_files#56936

Users

  • Add missing escaping on the Add New User screen – #57133

Props

Thanks to the 29 people who contributed to WordPress Core on Trac last week: @SergeyBiryukov (7), @audrasjb (5), @mukesh27 (4), @NekoJonez (3), @desrosj (3), @jrf (3), @costdev (3), @sabernhardt (2), @kowsar89 (1), @nithins53 (1), @jorbin (1), @azaozz (1), @itpathsolutions (1), @amirrezatm (1), @apermo (1), @riccardodicurti (1), @ptahdunbar (1), @kebbet (1), @ntsekouras (1), @mcsf (1), @WoutPitje (1), @peterwilsoncc (1), @hztyfoon (1), @rudlinkon (1), @monzuralam (1), @jipmoors (1), @poena (1), @petaryoast (1), and @krupalpanchal (1).

Congrats and welcome to our 2 new contributors of the week: @WoutPitje, @monzuralam ♥️

Core committers: @sergeybiryukov (11), @desrosj (5), @audrasjb (4), and @jorgefilipecosta (1).

#6-2, #core, #week-in-core

Devchat agenda, November 23, 2022

(Update November 23, 2022 – post added to section 3)

1. Welcome

Expect a brief check-in, since the United States is observing Thanksgiving week, and WordPress 6.2 will likely not kick off the pre-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. period before some 2023 planning.

To refresh your memory, here is last week’s summary. Thanks to @dpotter05 for compiling it!

2. Announcements

The project will end support for WordPress 3.7 – 4.0 on December 1. To that end, @peterwilsoncc will lead one last release party for those versions on November 30.

The WordPress developer blogblog (versus network, site) is in public beta! Find out more from @bph and check it out. Also, see how to contribute!

3. Blog posts of note

Got one to share? Post it in the comments.

Update: Nov 23, 2022 by @webcommsat: A Week in Core has been published.

4. Upcoming releases

The next major is 6.2; the next minor is 6.1.2. Look for updates next week.

5. Tickets, components and open floor

In the spirit of the season, please feel free to share something you appreciate either in the comments or in the chat.

See you at 20:00 UTC!

#agenda, #core, #dev-chat

Dev chat agenda: Wednesday, November 16, 2022

How did it get to be mid-November already?

Thanks to @webcommsat, @desrosj, and @nalininonstopnewsuk for stepping in on almost no notice when @marybaum was unavailable last week.

1. Welcome

Last week’s summary – props to @webcommsat.

2. Announcements

WordPress 6.1.1 maintenance release has landed!

Nominations are open for 2023 Core Team rep.

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

From @audrasjb, A week in Core.

From @helen, Improving the contributor experience.

And from @jeffpaul last week, the release post for WordPress 6.1.1 RC1.

4. Upcoming releases

The next major is 6.2.

The next minor is 6.1.2.

5. Components and tickets

This is the 6.2 alpha period — time to work on your favorite enhancements. This is also the time in the cycle when the community settles on the main areas of focus for 6.2, based on the product roadmap.

6. Open floor

Got a topic? Add it to the comments.

#agenda, #core, #dev-chat

A Week in Core – November 14, 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 October 31 and November 7, 2022.

  • 47 commits
  • 120 contributors
  • 97 tickets created
  • 27 tickets reopened
  • 104 tickets closed

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 missing escaping for a few strings used as HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. attributes – #57093

Bundled Themes

  • Twenty Seventeen: Improve letter-spacing reset for non-latin alphabets – #56994

Canonical

  • Protect against error for term not exists queries – #55955

Coding Standards

  • Apply spacing changes after composer format#57057
  • Declare $wp_taxonomies global at the top of unregister_taxonomy()#57058
  • Use consistent spelling for “cacheable” in WP_Query::get_posts()#57012

Docs

  • Document the usage of $wpdb global in WP_Date_Query methods – #57033
  • Document the usage of globals in some functions – #57082
  • Fix block_editor_rest_api_preload() parameter type – #56810, #56792
  • Improve globals documentation in unregister_taxonomy() and wp_term_is_shared()#57058, #56792
  • Replace 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. links with HTTPSHTTPS HTTPS is an acronym for Hyper Text Transfer Protocol Secure. HTTPS is the secure version of HTTP, the protocol over which data is sent between your browser and the website that you are connected to. The 'S' at the end of HTTPS stands for 'Secure'. It means all communications between your browser and the website are encrypted. This is especially helpful for protecting sensitive data like banking information. in class-json.php docblocks – #57017, #56792
  • Replace HTTP links with HTTPS in class-pop3.php docblocks and JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. vendor readme file – #57017, #56792
  • Typo correction in get_registered_nav_menus() docblockdocblock (phpdoc, xref, inline docs)#57101, #56792
  • Various docblock fixes in Multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site administration functions – #56792

Editor

  • Avoid running certain logic around theme.json parsing unnecessarily for classic themes – #56945
  • Correctly style separator blocks when only a background-color is defined – #56903
  • Improve Archive template description – #57001
  • Improve frontend performance for get_default_block_editor_settings()#56815
  • Improve how min/max font sizes are calculated for fluid typography – #57075
  • Improve performance of WP_Theme_JSON class by reducing usage of expensive array functions – #56974, #57067
  • Update 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 packages to the latest 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. releases – #57038, #56818, #56955, #56923

Filesystem

  • Return FTPFTP FTP is an acronym for File Transfer Protocol which is a way of moving computer files from one computer to another via the Internet. You can use software, known as a FTP client, to upload files to a server for a WordPress website. https://codex.wordpress.org/FTP_Clients./FTP Sockets exists() methods to a previous state – #56966, #51170, #28013

Formatting

  • Check that both normalizer_* functions exist in remove_accents()#56980

General

  • Use HTTPS for the b2/cafélog link in readme.html#57018

Help/About

  • Fix inconsistency in auto-updates help tabs – #56921

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.

  • Always pass $locale to load_textdomain()#57060
  • Initialize textdomain registry in wp_load_translations_early()#57051

Media

  • Prevent decoding attribute corrupting JSONJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. data – #56969

Menus

  • Apply menu-item-has-children class in sub-menus – #56946, #28620

Networks and Sites

  • Replace “N/A” with “Not applicable” in choose_primary_blog()#57040

Posts, Post Types

Query

  • Bypass caching for filtered SELECTs – #57012
  • Don’t attempt caching if running a WP_User_Query before plugins_loaded – #56952
  • Prevent ID only queries erroring when starting the 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.#56948

Tests

  • Combine duplicate update_posts_count() tests – #57023, #56793
  • Correct the test for get_blogaddress_by_id() with a non-existing ID – #56793
  • Resolve WP_Query test failures on MariaDB due to indeterminate sort order – #57012
  • Restore blogblog (versus network, site) switching in update_posts_count() test – #57023

Text Changes

  • Improve the wording of the email sent to confirm site deletion – #56921
  • Remove capitalization on “site editing” – #57026
  • Replace “Full site editing” with “Site Editor” – #57026
  • Update @since mentions for [54786] changes – #57026

Themes

  • Improve WP_Query call getting global styles – #56900
  • Re-order valid link pseudo classes – #56928
  • Reduce usage of wp_get_theme function. – #57057
  • Revert one instance of wp_get_theme() from [54817] – #57057

Update/Install

  • Deactivate 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 version older than 14.1 – #56985

Upgrade/Install

  • Delete the comments-query-loop folder in wp-includes/blocks#57080

Props

Thanks to the 120 (!) people who contributed to WordPress Core on Trac last week: @mukesh27 (12), @SergeyBiryukov (12), @desrosj (11), @spacedmonkey (10), @peterwilsoncc (9), @audrasjb (7), @flixos90 (6), @costdev (5), @TimothyBlynJacobs (5), @ocean90 (4), @hellofromTonya (4), @sabernhardt (3), @aristath (3), @andrewserong (3), @NekoJonez (2), @wildworks (2), @mikachan (2), @dd32 (2), @ironprogrammer (2), @swissspidy (2), @upadalavipul (2), @miguelaxcar (2), @mxbclang (2), @czapla (2), @poena (2), @davidbaumwald (2), @mamaduka (2), @azaozz (2), @nithins53 (2), @ramonopoly (2), @kowsar89 (2), @joen (2), @cbravobernal (2), @namithjawahar (1), @rjasdfiii (1), @dilipbheda (1), @10upsimon (1), @Bjorn2404 (1), @itpathsolutions (1), @kadamwhite (1), @codesdnc (1), @nuvoPoint (1), @outrankjames (1), @oandregal (1), @manuilov (1), @pbiron (1), @webmandesign (1), @sippis (1), @petitphp (1), @mattkeys (1), @stentibbing (1), @rajeshraval786 (1), @pento (1), @pypwalters (1), @haritpanchal (1), @webaxones (1), @Chaton666 (1), @obenland (1), @oakesjosh (1), @subrataemfluence (1), @carazo (1), @johnwatkins0 (1), @claytoncollie (1), @Clorith (1), @chouby (1), @janthiel (1), @JeffPaul (1), @johnbillion (1), @amirrezatm (1), @lozula (1), @konyoldeath (1), @Mamaduka (1), @hiren1094 (1), @larsmqller (1), @LeonidasMilossis (1), @adamsilverstein (1), @innovext (1), @bernhard-reiter (1), @bph (1), @noisysocks (1), @mciampini (1), @talldanwp (1), @andraganescu (1), @scruffian (1), @get_dave (1), @isabel_brison (1), @ntsekouras (1), @ellatrix (1), @aaronrobertshaw (1), @gisgeo (1), @jchambo (1), @zodiac1978 (1), @gamecreature (1), @pkolenbr (1), @afragen (1), @jsh4 (1), @tyxla (1), @mcsf (1), @fpodhorsky (1), @kacper3355 (1), @davidvongries (1), @glendaviesnz (1), @mw108 (1), @joelmadigan (1), @rodricus (1), @jorbin (1), @azurseisme (1), @jrf (1), @vtad (1), @krunal265 (1), @ryankienstra (1), @riccardodicurti (1), @0mirka00 (1), @ndiego (1), @kevin940726 (1), @alexstine (1), @youknowriad (1), @cybr (1), @krupalpanchal (1), and @rajanpanchal2028 (1).

Congrats and welcome to our 31 (!!!) new contributors of the week: @miguelaxcar, @kowsar89, @rjasdfiii, @10upsimon, @Bjorn2404, @itpathsolutions, @codesdnc, @nuvoPoint, @outrankjames, @stentibbing, @carazo, @amirrezatm, @lozula, @konyoldeath, @larsmqller, @LeonidasMilossis, @innovext, @gisgeo, @jchambo, @gamecreature, @pkolenbr, @jsh4, @fpodhorsky, @kacper3355, @davidvongries, @mw108, @joelmadigan, @rodricus, @azurseisme, @krunal265, @riccardodicurti, ♥️

Core committers: @audrasjb (14), @sergeybiryukov (11), @peterwilsoncc (8), @desrosj (7), @flixos90 (3), @spacedmonkey (1), @ocean90 (1), @hellofromtonya (1), and @timothyblynjacobs (1).

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

A Week in Core – November 7, 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 October 31 and November 7, 2022.

  • 19 commits
  • 24 contributors
  • 93 tickets created
  • 8 tickets reopened
  • 53 tickets closed

WordPress 6.1 « Misha » was released on Tuesday November 2, 2022! 🚀

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

  • Remove role="img" from decorative SVG images – #56824

Build/Test Tools

  • Don’t ZIP theme ZIP files – #56898
  • Fix more set-output deprecated warnings – #56820, #56882, #56793
  • Combine duplicate update_posts_count() tests – #57023, #56793
  • Move update_blog_status() tests to their own file – #56793
  • Remove a custom callback for checking action call count in multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site tests – #56793
  • Restore blogblog (versus network, site) switching in update_posts_count() test – #57023

Bundled Themes

  • Twenty Twenty-One: Properly bump to version 1.7 – #56450

Coding Standards

  • Correct alignment in various files – #56791

Docs

  • Add brackets to a function name in get_page_template() description – #56792
  • Correct DocBlockdocblock (phpdoc, xref, inline docs) formatting for wp_sitemaps_enabled 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.#56792
  • Document the usage of globals in upgrade_550() and upgrade_560()#56983
  • Fix typo in a comment in wp_prepare_revisions_for_js()#56981
  • Replace 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. links with HTTPSHTTPS HTTPS is an acronym for Hyper Text Transfer Protocol Secure. HTTPS is the secure version of HTTP, the protocol over which data is sent between your browser and the website that you are connected to. The 'S' at the end of HTTPS stands for 'Secure'. It means all communications between your browser and the website are encrypted. This is especially helpful for protecting sensitive data like banking information. in class-json.php docblocks – #57017, #56792
  • Typo correction in wp_dropdown_users() docblock – #56792
  • Update comments in wp_nav_menu() tests per the documentation standards – #56792

Editor

  • Improve Archive template description – #57001
  • CategoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. specific templates always appear as not found – #56902

General

  • Use HTTPS for the b2/cafélog link in readme.html#57018

Props

Thanks to the 24 people who contributed to WordPress Core on Trac last week: @desrosj (2), @mukesh27 (2), @audrasjb (2), @upadalavipul (1), @elifvish (1), @ryokuhi (1), @sabernhardt (1), @viralsampat (1), @colorfultones (1), @bgardner (1), @wildworks (1), @ndiego (1), @Chaton666 (1), @dilipbheda (1), @webaxones (1), @jrf (1), @franz00 (1), @ockham (1), @mikachan (1), @mamaduka (1), @rajanpanchal2028 (1), @haritpanchal (1), @SergeyBiryukov (1), and @aleksganev (1).

Congrats and welcome to our 2 new contributors of the week: @franz00, @aleksganev ♥️

Core committers: @sergeybiryukov (11), @audrasjb (4), @desrosj (3), and @jorgefilipecosta (1).

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

A Week in Core – October 31, 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 October 24 and October 31, 2022.

  • 39 commits
  • 69 contributors
  • 43 tickets created
  • 13 tickets reopened
  • 46 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

  • Improve the wording of “Site Address” field description – #50629

Build/Test Tools

  • Ensure PHPCSPHP Code Sniffer PHP Code Sniffer, a popular tool for analyzing code quality. The WordPress Coding Standards rely on PHPCS. related workflows are properly marked as failed – #55652
  • Hardcode the ref for the workflow dispatch on failure – #55652
  • Introduce a workflow for testing and building default themes – #56898
  • Correctly restore the wp_installing() status in Ajax tests – #56793
  • Move dbDelta() tests to the db directory – #56793, #56782
  • Move wp_handle_comment_submission() tests to the comment directory. – #56793
  • Move wp_mail() tests to the pluggable directory. – #56793
  • Move some @covers tags in the formatting group to the class DocBlockdocblock (phpdoc, xref, inline docs)#56793
  • Move the tests for WP class methods to the wp directory – #56793, #56782
  • Move the tests for pluggable function signatures to the pluggable directory – #56793, #56782
  • Prevent wp_update_themes() from running in wp_ajax_update_theme() tests – #56793
  • Remove skipWithMultisite() and skipWithoutMultisite() from get_user_count() tests – #56793
  • Remove skipWithMultisite() from an Ajax test for attachments – #56793
  • Remove unused $user_ids property in Tests_Ajax_Autosave class – #56793
  • Rename classes in phpunit/tests/ajax/ per the naming conventions – #56793
  • Rename classes in phpunit/tests/comment/ per the naming conventions – #56793
  • Split the tests from category.php into individual test classes – #56793
  • Split the tests from multisite.php into individual test classes – #56793
  • Temporarily skip WOFF file test on PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8.1 – #56817

Bundled Themes

  • Twenty Twenty-Three: Merge the latest changes from 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/#56383

Coding Standards

  • Correct alignment in Tests_Ajax_Autosave::wpSetUpBeforeClass()#56793

Database

Docs

  • Add a @since note for object-fit support in safecss_filter_attr()#56855
  • Update a link to the Custom Elements spec in unsupported_valid_tag_names() unit testunit test Code written to test a small piece of code or functionality within a larger application. Everything from themes to WordPress core have a series of unit tests. Also see regression. docblock – #56792

Editor

  • Allow arrays for deprecated asset types 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. registration – #56707
  • Correctly apply Button block styles for classic themes – #56467
  • Ensure global styles are rendered for third-party blocks – #56915
  • Update packages for 6.1 Release Candidaterelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). 3 – #56467

Help/About

  • Add link to the 6.1 release video – #56357
  • Update About section images – #56357

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.

  • Change how WP_Textdomain_Registry stores the default languages path – #39210

KSES

  • Display a notice if any of the required globals are not set – #47357

Media

  • Add object-fit to the allowed list of CSSCSS Cascading Style Sheets. properties – #56855
  • Reverts get_attached_file() changes for normalized Windows paths – #56924

Query

  • Move cache key generation to its own method – #56802

Role/Capability

  • Revert the newly added update_role function for 6.1

Themes

  • Ensure custom global styles are imported properly – #56901

Upgrade/Install

  • Update $_old_files for 6.1 – #56934

Props

Thanks to the 69 people who contributed to WordPress Core on Trac last week: @SergeyBiryukov (9), @audrasjb (7), @peterwilsoncc (5), @desrosj (5), @spacedmonkey (4), @davidbaumwald (4), @bernhard-reiter (4), @hellofromTonya (3), @mukesh27 (3), @cbravobernal (3), @pbearne (3), @oandregal (2), @scruffian (2), @aristath (2), @flixos90 (2), @poena (2), @sergeybiryukov (2), @ndiego (2), @hellofromtonya (2), @ocean90 (2), @kebbet (2), @sabernhardt (2), @ironprogrammer (2), @andraganescu (2), @andrewserong (2), @mikeschroder (2), @jorbin (2), @costdev (2), @annezazu (2), @bosconiandynamics (1), @joedolson (1), @nendeb55 (1), @jrf (1), @TJNowell (1), @TobiasBg (1), @raduiason (1), @ckanderson22 (1), @KnowingArt_com (1), @pento (1), @pbiron (1), @doctorlai (1), @manfcarlo (1), @xknown (1), @seriouslysenpai (1), @ivanjeronimo (1), @adamsilverstein (1), @ramonopoly (1), @azaozz (1), @EidolonNight (1), @admwgn (1), @critterverse (1), @joen (1), @jpantani (1), @laurlittle (1), @cbringmann (1), @kellychoffman (1), @pablohoney (1), @mreishus (1), @tobifjellner (1), @anariel-design (1), @wildworks (1), @ajlende (1), @gigitux (1), @czapla (1), @richtabor (1), @digical (1), @kafleg (1), @mikachan (1), and @gziolo (1).

Congrats and welcome to our 3 new contributors of the week: @admwgn, @gigitux, @digical ♥️

Core committers: @sergeybiryukov (21), @davidbaumwald (5), @desrosj (4), @bernhard-reiter (3), @ryelle (2), @hellofromtonya (1), @antpb (1), @peterwilsoncc (1), and @swissspidy (1).

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

Dev Chat agenda: October 26,2022

1. Welcome

October 26 is the last dev chat of the 6.1 release cycle. Next week at this time, 6.1 will be live!

2. Announcements

WordPress 6.1 RC3 landed on Tuesday, October 25. Please download and test!

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

@audrasjb thanks all the people in the latest A week in Core.

@priethor has published a guide to the final release process. You can start testing and other preparations for the big day now!

@sabernhardt discusses some new markup and styles in the world of Multisite.

And @estelaris showcases a new design for HelpHub.

4. Upcoming releases

The next major is 6.1.

An impromptu 6.0.3 minor landed last week. The CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team also updated every version below 6.0 that is still under official support.

5. Components and tickets

@robinwpdeveloper, a developer in Bangladesh, has volunteered to maintain the Login/Registration component. He got inspired by this October 5 devchat thread and messaged @marybaum on October 23.

6. Open Floor

Got something to raise? Add it to the comments, and see you at devchat!

#agenda, #core, #dev-chat

WordPress 6.1 Release Day Process

Preparation for WordPress 6.1 final release is underway. This post shares the release process, including the timeline and how you can help. The post will be kept up to date as the release process evolves.

Release Timeline Overview

The current plan is:

Edit History

  • October 27th: Dry Run was rescheduled to start earlier, as proposed in #6-1-release-leads.
  • October 31st: Provided RC6 launch, 24-hour code freeze start time, and release party start time.

Dry Run ✅

The Dry Run is a key event as a final walk-through for the final release. As noted above, the current plan is to start it on 2022-10-31 14:00. You are invited to observe and/or participate. It’ll happen in the #core Slack channel.

What happens during the dry run?

  • Review 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. reports to determine if any are critical to warrant another RCrelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). (release candidaterelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta).).
  • Checks and any necessary updates are made in the src/wp-admin/includes/update-core.php file.
  • Pre-release scripts are run to ensure test suites, coding standards, and other automated checks pass.

If the results are acceptable, the release goes into a 24-hour code freeze period.

24-Hour Code Freeze⏳

After the dry run and before the release party starts, a mandatory 24-hour code freeze goes into effect. This locking period started on 2022-10-31 23:29.

What does this mean? No source code for 6.1.0 (i.e., in the 6.1 branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch".) can be changed during these 24 hours.

What happens if a critical bug is reported during this period? The release squad will meet with committers and maintainers to determine if the issue is a blocker.

  • If yes, another RC release happens, and the release process restarts (meaning the dry run is repeated, and then the 24-hour code freeze clock restarts).
  • If not, then the bug is targeted for 6.1.1.

The Stable Release Party 📅

The final release will occur on 2022-11-01 23:30 in #core.

The release party on November 1st will start no sooner than 24h after the code freeze starts, with the exact time to be determined accordingly. You are invited to observe and/or participate. It’ll happen in the #core Slack channel.

The release party walks through the steps in the Major Version Release process for anyone who wants to follow along.

Please note releasing a major version requires more time than releasing a 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. or release candidate. There are more steps in the process. If any last-minute issues need addressing, more time will be needed.

How You Can Help

A key part of the release process is checking that the ZIP packages work on all the different server configurations available. If you have some of the less commonly used servers available for testing (IIS, in particular), that would be super helpful. Servers running older versions of PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher and MySQLMySQL MySQL is a relational database management system. A database is a structured collection of data where content, configuration and other options are stored. https://www.mysql.com/. will also need testing.

You can even start this early by running the WordPress 6.1 RC3 packages, which are built using the same method as the final packages.

During the release party, options will be provided on how to help test the release package.

Tips on What to Test

In particular, testing the following types of installs and updates would be much appreciated:

  • Does a new WordPress install work correctly? This includes running through the manual install process, as well as WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/ https://make.wordpress.org/cli/ or one-click installers.
  • Test upgrading from 4.0.37, 4.9.22, 5.8.6, 5.9.5, 6.0.3, and 6.1 RC3, as well as any other versions possible.
  • Remove the wp-config.php file and test a fresh install.
  • Test single site and multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site/networknetwork (versus site, blog) (both subdirectory and subdomain) installations.
  • Does it upgrade correctly? Are the files listed in $_old_files removed when you upgrade?
  • Does multisite upgrade properly?

Testing the following user flows on both desktop and mobile would be great to validate each function as expected:

  • Publish a post, including a variety of different blocks.
  • Comment on the post.
  • Install a new 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/theme, or upgrade an existing one.
  • Change the site language.
  • If you’re a plugin developer, or if there are complex plugins you depend upon, test that they’re working correctly.

Props to @desrosj and @zoonini for peer review.

#6-1, #core, #release-process

A Week in Core – October 24, 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 October 17 and October 24, 2022.

  • 49 commits
  • 75 contributors
  • 63 tickets created
  • 12 tickets reopened
  • 51 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

  • Update the Dashboard welcome banner for 6.1 – #56703

Bootstrap/Load

  • Correct sending the X-Pingback 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. in WP::send_headers()#56840

Build/Test Tools

  • Ensure PHPCSPHP Code Sniffer PHP Code Sniffer, a popular tool for analyzing code quality. The WordPress Coding Standards rely on PHPCS. related workflows are properly marked as failed – #55652
  • Hardcode the ref for the workflow dispatch on failure – #55652
  • Remove use of set-output in Action workflows – #56820
  • Update third-party welcome Action – #56793
  • Add a test case for safecss_filter_attr() with object-position property – #56793
  • Correct the wp_theme_json_data_default 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. name in assertion messages – #56796, #56835
  • Increase test coverage for WP_Theme_JSON_Resolver#56835
  • Make the message for skipping some tests with an external object cache more consistent – #56793
  • Move padding-* test data in KSES tests into its own test case – #56793

Bundled Themes

  • Twenty Twenty-Three: Sync the latest fixes for RC2 – #56383

Coding Standards

  • Use strict comparison in wp-admin/update-core.php#56866

Docs

  • Add missing default parameter value in themes_api() docblockdocblock (phpdoc, xref, inline docs)#56862, #56792
  • Add missing default parameter value in trackback_response() docblock – #56867, #56792
  • Align spelling with American English – #56811, #56792
  • Align spelling with American English – #56811, #56792
  • Document the usage of $wp_query global in WP_Media_List_Table::display_rows()#56839

Editor

  • Add font size constraints for fluid typography – #56467
  • Fix legacy group inner 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. wrappers in constrained layouts – #56467
  • Fix modal height responsiveness on link popup editor – #53174
  • Update packages for 6.1 Release Candidaterelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). 2 – #56467
  • Allow arrays for deprecated asset types in block registration – #56707

Embeds

  • Broaden the Tumblr oEmbed matcher to include all Tumblr URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org structures – #56733

General

  • Correctly refer to “npm” and “Node.js” – #56816

Help/About

  • Restore the correct header image for WordPress 6.1 – #56703
  • Typo correction in Dashboard Screen Options – #56884
  • Update copy & style for About page and subpages – #56357
  • Update the About header image – #56703, #56357

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.

  • Change how WP_Textdomain_Registry stores the default languages path – #39210

KSES

  • Display a notice if any of the required globals are not set – #47357

Media

  • Add object-fit to the allowed list of CSSCSS Cascading Style Sheets. properties – #56855

Networks and Sites

  • Revert the use of the metadata 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. for *_network_options functions – #56845, #37181

Query

  • Remove placeholder from query cache key. – #56802

Role/Capability

  • Revert the newly added update_role function for 6.1

Upgrade/Install

  • Add a conditional to facilitate testing of the Rollbacks feature project – #56057

Props

Thanks to the 75 people who contributed to WordPress Core on Trac last week: @xknown (10), @peterwilsoncc (9), @audrasjb (8), @SergeyBiryukov (7), @martinkrcho (6), @bernhard-reiter (5), @costdev (5), @paulkevan (5), @jrf (4), @davidbaumwald (4), @kebbet (4), @sabernhardt (4), @spacedmonkey (4), @mukesh27 (4), @dd32 (3), @richtabor (3), @johnbillion (3), @andrewserong (2), @rezakhan995 (2), @ehtis (2), @timothyblynjacobs (2), @tykoted (2), @desrosj (2), @cbravobernal (2), @voldemortensen (2), @isabel_brison (2), @pbiron (2), @ironprogrammer (2), @poena (2), @webcommsat (1), @johnjamesjacoby (1), @bph (1), @courane01 (1), @strategio (1), @rinatkhaziev (1), @dlh (1), @chaion07 (1), @dansoschin (1), @dhl (1), @talldanwp (1), @noisysocks (1), @mikachan (1), @beafialho (1), @kafleg (1), @vortfu (1), @matveb (1), @annezazu (1), @Joen (1), @rebasaurus (1), @gziolo (1), @raduiason (1), @ckanderson22 (1), @ivanjeronimo (1), @seriouslysenpai (1), @manfcarlo (1), @doctorlai (1), @pento (1), @KnowingArt_com (1), @bosconiandynamics (1), @TJNowell (1), @nendeb55 (1), @sergeybiryukov (1), @pavelschoffer (1), @flixos90 (1), @ocean90 (1), @upadalavipul (1), @saumil1611 (1), @rakibwordpress (1), @ramonopoly (1), @TobiasBg (1), @afragen (1), @ryelle (1), @adampickering (1), @mikeschroder (1), and @peterwiloncc (1).

Congrats and welcome to our 9 new contributors of the week: @rezakhan995, @raduiason, @ckanderson22, @ivanjeronimo, @seriouslysenpai, @doctorlai, @KnowingArt_com, @pavelschoffer, @saumil1611 ♥️

Core committers: @audrasjb (14), @sergeybiryukov (12), @davidbaumwald (8), @desrosj (6), @ryelle (2), @jorbin (2), @bernhard-reiter (1), @swissspidy (1), @joedolson (1), @pento (1), and @spacedmonkey (1).

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

Dev Chat summary, October 19, 2022

Notes from the weekly WordPress developers chat held 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/..

The start of the meeting on Slack.

1. Welcome

@webcommsat and @ndiego led the weekly WordPress developers chat meeting on this agenda.

Last week’s summary – October 12, 2022.

2. Announcements

WordPress 6.1 Release Candidate 2 was released on Tuesday, October 18, 2022, and is available for testing. For reference on how to help test WordPress, check out this comprehensive guide.

The What’s new in Gutenberg Plugin 14.3 article was published last week detailing all of the enhancements in 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/ 14.3.

On Monday, October 17, 2022, there was a WordPress 6.0.3 Security Release. This is a major security update with a dozen of fixes. Everyone is encouraged to update to 6.0.3.

3. Blogblog (versus network, site) Posts of Note

4. Upcoming Releases

The next major WordPress release is 6.1. As mentioned above, WordPress 6.1 Release Candidate 2 is available for testing. You can find the latest developer notes at the dev-notes-6-1 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.).

@audrasjb gave a triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. report that we have 9 tickets in the milestone, and everyone is welcome to help move them toward a resolution before RC3.

@ndiego gave a triage report for the Editor that there is still a handful of issues/PRs that are being worked through.

@webcommsat shared that a couple more 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. scrubs are scheduled in the coming weeks.

@jeffpaul emphasized the need for help on the outstanding TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. and 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/ issues and encouraged folks to continue testing RC2. We are less than 2 weeks away from release!

@pbiron raised an issue related to the 6.0.3 security release: #56855: Featured Image bug in 6.0.3. The full discussion on this topic is available in Slack starting here, which resulted in a 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. being created.

Concerning the translationtranslation The process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization. of the upcoming release, @audrasjb indicated that there have been some string changes. @webcommsat shared that translations for WordPress can be submitted via the related projects on translate.wordpress.org. The newest default theme, Twenty Twenty-Three, is also available for translation. The monthly polyglot newsletter will be out soon and have more information on this.

5. Maintainers and Tickets

a) Component Maintainers updates

@sergeybiryukov reported that for Upgrade/Install, a call to action for testing the Rollback feature was posted on the Make Hosting blog. There was no major news for Build/Test Tools, Date/Time, 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., or Permalinks.

@webcommsat reported that the next bulk/edit and About/Help components scrub and triage will be held Monday, October 24, 2022, at 20:00 UTC. The scrub this week was postponed.

b) Tickets to highlight

There were no tickets highlighted.

5. Open Floor

@pbiron shared the patch that he put together for the Featured ImageFeatured image A featured image is the main image used on your blog archive page and is pulled when the post or page is shared on social media. The image can be used to display in widget areas on your site or in a summary list of posts. bug (#56855) that he highlighted in the Upcoming Releases section of the Dev Chat.

@webcommsat reported that the Documentation Team will be holding its first dedicated Contributor Day in #docs on October 25, 2022.

Next meeting: Wednesday October 26, 2022 at 20:00 UTC

Props to @webcommsat for meeting preparation and to @webcommsat and @ndiego for facilitating and collaborating on the summary.

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