Tag Archives: 6.2

Jb Audras 8:09 pm on April 4, 2023
Tags: 6.2, ,   

Two Weeks in Core – April 3, 2023

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 March 20 and April 3, 2023. Sorry for not being able to publish a post last week, this one will cover two weeks!

  • 38 commits
  • 76 contributors
  • 120 tickets created
  • 19 tickets reopened
  • 86 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

  • Update dashboard welcome panel colors, remove broken link – #57759

Build/Test Tools

  • Fix issue with add method in object-cache.php – #57963
  • Add a@ticketreference forwp_list_pages()CSSCSS Cascading Style Sheets. classes test – #57841
  • Consistently sanitize expiration in the test suite’s Memcached implementation – #57841, #57963
  • Fix tests introduced in [55612] – #57814
  • Improveget_pages()tests organization – #57841
  • Movewp_dropdown_pages()tests to their own file – #57841
  • Move thewp_list_pages()test for CSS classes to a more appropriate place – #57841
  • Rename test class and improve tests for wp_get_global_stylesheet() – #57841, #57958
  • Split the tests frompost/template.phpinto individual test classes – #57841

Code Modernization

Coding Standards

  • Apply various alignment corrections fromcomposer format– #57994
  • Correct the closing PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 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.) placement in some adminadmin (and super admin) files – #58053
  • Escape some variables inwp-admin/includes/nav-menu.php– #57110
  • Escape the whole attributes inwp-admin/includes/nav-menu.php– #57110
  • Remove unused variable inWP_Plugins_List_Table::single_row()– #55132
  • Use strict comparison inwp-admin/includes/nav-menu.php– #57318
  • Use strict comparison inwp-admin/includes/user.php– #57317
  • Use the correct variable – #57318

Comments

  • Use correct escaping function inget_cancel_comment_reply_link()– #58025
  • Use wp_cache_get_multiple inWP_Comment_Query– #57803

Date/Time

Docs

  • Add missing@returntag forWP_Automatic_Updater::is_disabled()– #57680
  • Clarify the::hide_process_failed()return value 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 and theme installer – #57680
  • Document default values for optional parameters inwp_insert_attachment()– #58043
  • Use typed array notation forsearch_columnsinWP_Query::parse_query()– #57996

Editor

General

  • Remove Windows Live Writer manifest file – #41404

HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. 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.

  • Addhas_self_closing_flag()to Tag Processor – #58009

Help/About

  • Add Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. link – #57998
  • Make Field Guide link translatable – #57477
  • Updates to About page – #57477

Login and Registration

Options, 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. APIs

  • Improve the lazy loading meta API to include current object id – #57901

Posts, Post Types

  • Use WP_Query internally in get_pages – #12821

Script Loader

  • Return early in _wp_theme_json_webfonts_handler if theme.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. not present – #57814

Upgrade/Install

  • Include the removed Windows Live Writer manifest in$_old_files– #41404

Props

Thanks to the 76 people who contributed to WordPress Core on Trac last week: @sergeybiryukov (9), @spacedmonkey (6), @costdev (6), @hellofromTonya (6), @jrf (5), @mukesh27 (4), @flixos90 (4), @peterwilsoncc (4), @audrasjb (3), @desrosj (3), @ocean90 (3), @patelmohip (2), @jenilk (2), @johnbillion (2), @sabernhardt (2), @davidbaumwald (2), @laurlittle (2), @richtabor (2), @akmelias (2), @sakibmd (2), @ankitmaru (1), @wlindley (1), @ayeshrajans (1), @azouamauriac (1), @mikeschinkel (1), @nacin (1), @scribu (1), @filosofo (1), @jane (1), @garyc40 (1), @markoheijnen (1), @grandslambert (1), @kevinB (1), @dbernar1 (1), @ryokuhi (1), @atimmer (1), @mdawaffe (1), @helen (1), @benjibee (1), @joemcgill (1), @andraganescu (1), @get_dave (1), @mamaduka (1), @ntsekouras (1), @scruffian (1), @talldanwp (1), @jhabdas (1), @ironprogrammer (1), @tillkruess (1), @francina (1), @chintan1896 (1), @zenaulislam (1), @javiercasares (1), @oglekler (1), @clorith (1), @eboxnet (1), @wpfy (1), @vladytimy (1), @reputeinfosystems (1), @Rarst (1), @priethor (1), @nekojonez (1), @markjaquith (1), @codingchicken (1), @cbringmann (1), @tmatsuur (1), @joostdevalk (1), @faisalahammad (1), @zieladam (1), @dmsnell (1), @wtranch (1), @polevaultweb (1), @azaozz (1), @Frank Klein (1), @antonvlasenko (1), and @thomask (1).

Congrats and welcome to our 8 new contributors of the week: @patelmohip, @akmelias, @wlindley, @grandslambert, @benjibee, @wpfy, @reputeinfosystems, @wtranch ♥️

Core committers: @sergeybiryukov (20), @spacedmonkey (6), @hellofromtonya (6), @audrasjb (2), @ryelle (2), @bernhard-reiter (1), and @dd32 (1).

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

Héctor Prieto 4:30 pm on March 28, 2023
Tags: 6.2,   

WordPress 6.2 release date updated: March 29, 2023

The WordPress 6.2 release was due today, March 28, 2023. However, a regression with date formats has been spotted during the 24-hour freeze. Release leads have agreed to revert the ticketticket Created for both bug reports and feature development on the bug tracker. that introduced the 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., which will require another 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). version, restarting the 24-hour freeze timer, and a new release date on March 29th.

Ensuring the newest version of WordPress meets the best quality standards and doesn’t introduce a regression that can impact many popular business-oriented plugins is essential.

WordPress 6.2 Release Candidate 5 has been shipped, reverting the following changeset:

Following this 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, the 24-hour code freeze timer has been restarted, and the current target release date is 2023-03-29 at 17:00 UTC.

Props to @cbringmann, @costdev,@davidbaumwald, and @hellofromtonya for peer-reviewing this post.

#6-2, #releases

Héctor Prieto 7:47 pm on March 23, 2023
Tags: 6.2, ,   

WordPress 6.2 Release Day Process

Preparation for WordPress 6.2 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 as follows:

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 2023-03-27 16: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 candidate).
  • 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.

What does this mean? No source code for 6.2.0 (i.e., in the 6.2 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 blockerblocker A bug which is so severe that it blocks a release..

  • 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.2.1.

The Release Party 📅

UPDATE: Following a regression fixed during code freeze and the restart of the code freeze clock, the release party has been rescheduled to 2023-03-29 17:00 UTC

The release party on March 28th 29th 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 available server configurations. 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 start this early by running the WordPress 6.2 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.38, 4.9.22, 5.8.6, 5.9.5, 6.0.3, 6.1.1, and 6.2 RC4, 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.

Thanks to @cbringmann and @hellofromtonya for the peer review

#6-2, #core, #release-process

Lauren Stein 5:33 pm on March 23, 2023
Tags: 6.2, ,   

WordPress 6.2 Release Candidate 4

To get ready for the final release of WordPress 6.2 on March 28, 2023, an RC4 has been put together to help cover some last-minute fixes. 

Here’s what’s changed since RC3:

  • Revert changesets [55358] and [55360], restoring the wp_insert_user() function back to its previous state, to avoid a 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. on the related wp_update_user() function (see tickets #57967 and #57394).

Thanks to everyone who has assisted with testing this release. Your feedback and help in filing 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 keep the WordPress experience stable, smooth, and delightful. It’s critical work and a great way to contribute to the project—especially in these final moments before release day.

How to install RC4

This version of the WordPress software is under development. Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, it is recommended that you test RC4 on a test server and site. 

You can test WordPress 6.2 RC4 in three ways:

  • Option 1: Install and activate the WordPress Beta Tester 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 (select the “Bleeding edgebleeding edge The latest revision of the software, generally in development and often unstable. Also known as trunk.” channel and “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./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). Only” stream).
  • Option 2: Direct download the RC4 version (zip).
  • Option 3: Use the following 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/ command:

    wp core update --version=6.2-RC4

Keep WordPress bug-free—help with testing

Without your testing support, hitting important product milestones would be a much bigger challenge. It’s also a meaningful way to contribute to the project. If you’re new to testing, or it’s been a while, this detailed guide can help you get started. 

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

Test your plugins and themes

As you test your latest versions against RC4, make sure you update the “Tested up to” version in your plugin’s readme file to 6.2. If you find compatibility problems, please post detailed information to the support forums.

Check out the WordPress 6.2 Field Guide for more details about the major changes in this release.

Help translate WordPress

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

Release the haiku

What’s this? RC4?
Get those fixes out the door
Release day is close

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

#6-2, #development, #releases

Olga Gleckler 12:35 pm on March 23, 2023
Tags: 6.2, , ,   

Dev chat Summary, March 22, 2023

1. Welcome and housekeeping

@francina led the chat in the core channel of the Make WordPress Slack.

The agenda — thanks to @webcommsat, has a full list of 6.2 links. Highlighted posts are below.

Last week’s dev chat summary, March 15, 2023 – thanks to @marybaum

2. Announcements

  • Gutenberg 15.4 arrived Wednesday, March 22, 2023 — thanks to @greenshady and @welcher for getting the post out in such a short time after release.
  • WordPress 6.2 RC3 landed on Tuesday, March 21, 2023.
  • Silent RC4 will address a backward compatibility issue (#57967) on March 23. More on the 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. is in this discussion on Slack.

And:

  • The WordPress Developer Blog is out of 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., and officially launched! Please check it out. You are most welcome to:

3. Highlighted posts

And:

4 Tickets and components

  • The Bulk and Quick Edit component

@francina raised ticketticket Created for both bug reports and feature development on the bug tracker. #11302 “Bulk editing posts should pre-fill fields with the same value / allow for removal”

@oglekler brought up a related ticket: #19859 “Bulk Edit” Missing The Ability To Edit Tags

@azaozz suggested that it is time to make a large update to this component, taking care about bugs and enhancements.

@marybaum said the maintainers, who also include @webcommsat, @oglekler, and @nalininonstopnewsuk, will follow up. (Ed. note: Look for this starting in April, once the current release has landed.)

5. Open floor

WCEU 2023 preparations

@estelaris asked for help answering Interview questions for Make Teams reps about Contributor Day.

Documentation

@estelaris and asked for review and comments on ticket #48998 Documentation Structure Block Editor Handbook

The Developer Blogblog (versus network, site)

@azaozz suggested publishing dev notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. there as well (right now the 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. has only a link in the footer). 

@jeffpaul requested to auto-publish posts in the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. channel and @bph will follow up with it.

A week in Core

@bph suggested renaming ‘A week in Core’ to ‘A week in TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.’, because it doesn’t cover 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/ project activity on 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/, and they are highlighted separately in What’s New in Gutenberg. @francina offered to continue this discussion in the P2P2 A free theme for WordPress, known for front-end posting, used by WordPress for development updates and project management. See our main development blog and other workgroup blogs. (Ed. note: that is, this very Make/core blog) in the comments section of the last Week in Core.

Broad questions

@sereedmedia drew attention to a marketing ticket with a cornerstone What is WordPress?

@francina: What brought you to check dev chats in the first place? A lively, if brief, discussion followed. Francesca also suggested more discussion next week—and a post on the Core blog, to stimulate asynchronous conversations.

Next week’s dev chat will be Wednesday, March 29, 2023, at 11:00 PM GMT+3 in the Core Slack channel. See you there!

Props to @francina for leading dev chat, to @webcommsat for the agenda preparation, @oglekler for the summary, and @marybaum and @webcommsat for review.

#6-2, #dev-chat, #meeting, #summary

Jb Audras 8:57 pm on March 21, 2023
Tags: 6.2, ,   

A Week in Core – March 20, 2023

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 March 13 and March 20, 2023.

  • 30 commits
  • 70 contributors
  • 51 tickets created
  • 4 tickets reopened
  • 46 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

  • Define the $title global on the Menus screen for classic themes – #57918
  • Update dashboard welcome panel colors, remove broken link – #57759

Build/Test Tools

  • Fix issue with add method in object-cache.php – #57963
  • Revert [55553] – #57864
  • Add test class for wp_enqueue_stored_styles() – #57841
  • Add test class for wp_script_is() – #57841, #57958
  • Improve documentation and variable names in some formatting tests – #57841
  • Rename test class and improve tests for wp_get_global_stylesheet() – #57841, #57958
  • Use the data_ prefix for various data provider methods – #57841

Cache 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.

  • Add a warning when calling _get_non_cached_ids with invalidinvalid A resolution on the bug tracker (and generally common in software development, sometimes also notabug) that indicates the ticket is not a bug, is a support request, or is generally invalid. ids – #57593
  • Correct the second parameter’s name in _get_non_cached_ids() – #40420

Code Modernization

Coding Standards

  • Remove unused variable in WP_Plugins_List_Table::single_row() – #55132
  • Remove unused variables in WP_Comment_Query – #57482
  • Use single quotes for strings without variables in register_block_style_handle() – #57903

Date/Time

  • Remove usage of mysql2date in generate_postdata method – #57683

Docs

  • Fix typo in _validate_cache_id() description – #57593

Editor

  • Correctly load RTL stylesheets for non-core blocks – #57903
  • Show scheduled text when changing to new future dates – #31040
  • Update wordpress packages for 6.2 RC2 – #57471 – #57895
  • Update wordpress packages for 6.2 RC3 – #57471, #57929

External Libraries

  • Upgrade PHPMailer to version 6.8.0 – #57873

Filesystem API

  • Return false for empty paths in 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. ::exists() methods – #33058

HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. API

  • Add bookmark invalidation logic – #57788

Help/About

  • Add CDN images to About page – #57477
  • Updates to About page – #57477

KSES

  • Allow filter property to accept a URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org in safecss_filter_attr() – #57780

Posts, Post Types

  • Use WP_Query internally in get_pages – #12821

Quick/Bulk Edit

  • Show scheduled in status for future drafts – #38834

Widgets

  • Defer register inline script in WP_Widget_Custom_HTML and WP_Widget_Text – #57864

Props

Thanks to the 70 people who contributed to WordPress Core on Trac last week: @sergeybiryukov (8), @costdev (7), @hellofromTonya (6), @spacedmonkey (6), @flixos90 (4), @richtabor (3), @peterwilsoncc (3), @antonvlasenko (2), @audrasjb (2), @azaozz (2), @scruffian (2), @mamaduka (2), @ironprogrammer (2), @laurlittle (2), @jrf (2), @sabernhardt (2), @mkox (1), @joedolson (1), @ipstenu (1), @MrFlannagan (1), @oglekler (1), @upadalavipul (1), @dingo_d (1), @Rarst (1), @ayeshrajans (1), @Synchro (1), @Zdrobau (1), @tyxla (1), @dd32 (1), @pbiron (1), @mukesh27 (1), @bernhard-reiter (1), @dmsnell (1), @zieladam (1), @sakibmd (1), @westonruter (1), @nendeb55 (1), @david.binda (1), @tillkruess (1), @tobifjellner (1), @sdavis2702 (1), @jeryj (1), @markjaquith (1), @dbernar1 (1), @azouamauriac (1), @mikeschinkel (1), @nacin (1), @scribu (1), @filosofo (1), @jane (1), @garyc40 (1), @markoheijnen (1), @grandslambert (1), @kevinB (1), @wlindley (1), @atimmer (1), @ryokuhi (1), @mdawaffe (1), @helen (1), @benjibee (1), @johnbillion (1), @joemcgill (1), @andraganescu (1), @get_dave (1), @ntsekouras (1), @desrosj (1), @talldanwp (1), @thomask (1), @johnjamesjacoby (1), and @davidbaumwald (1).

Congrats and welcome to our 6 new contributors of the week: @MrFlannagan, @Zdrobau, @grandslambert, @wlindley, @benjibee, @thomask ♥️

Core committers: @sergeybiryukov (12), @hellofromtonya (7), @spacedmonkey (6), @ryelle (3), and @joedolson (2).

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

Abha Thakor 7:57 pm on March 21, 2023
Tags: 6.2, ,   

Dev Chat Agenda, Wednesday March 22, 2023

The next WordPress Developers Chat will on Wednesday, March 22, 2023 at 20:00 UTC in the core channel of the Make WordPress Slack.

1. Welcome and housekeeping

Dev Chat summary, March 15, 2023 – thanks to @marybaum

The meeting’s scheduled facilitator will be @francina

@oglekler and @webcommsat are on the rota for this week’s meeting summary.
If you would like to volunteer for the summary, do add a comment to this ticketticket Created for both bug reports and feature development on the bug tracker. for @webcommsat.

2. Announcements

WordPress 6.2 RC3

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/ 15.4 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). is scheduled (now available for testing)

3. Highlighted posts

Call for volunteers to help with 6.2 end user docs from the release docs group.

4. Releases

Useful information on the next major WordPress release 6.2.

The schedule release is now only two weeks away on March 28.

Also check the #6-2-release-leads channel for the latest updates.

For information:

  • WordPress 6.2 has branched.

More updates from the Release Squad to come in the meeting.

5. Request for help with tickets/ components/ blockers/

If you have a ticket or request to help, please add a comment to the agenda post. Please indicate if you will be attending the meeting live and be able to highlight the issue further if needed.

If you are unable to attend dev chat live, you can add further details of the issue you would like highlighted either in comments, or message CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team reps @webcommsat and @hellofromtonya with the additional information to raise in this week’s meeting for you.

6. Open floor

Items for this agenda item and the previous one are welcome from across time zones. Please add suggestions in comments on this post. Thanks.

Props for agenda preparation @webcommsat, review @hellofromtonya and @marybaum.

#6-2, #agenda, #dev-chat

marybaum 9:30 am on March 17, 2023
Tags: 6.2, , ,   

Dev chat Summary, March 15, 2023

1. Welcome and housekeeping

@francina led the chat. The meeting start on 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 agenda, prepared by @webcommsat, has a full list of 6.2 links, only new links are listed below.

Last week’s dev chat summary, March 8, 2023 – thanks to @ironprogrammer.

2. Announcements

WordPress 6.2 RC 2 landed on Tuesday, March 14, 2023! Please download and test, and remember that in the 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). period:

  • It takes two committers to commit code to the 6.2 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".
  • The 6.3 branch is open for early tickets, proposals and more
  • There’s a hard string freeze on the 6.2 branch

Gutenberg 15.3 landed Monday, March 13, 2023.

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/ 15.4 is underway.

3. Highlighted posts

@annezazu tells how and why the Navigation section of the Site Editor is gone from 6.2 RC 2.

@audrasjb recaps A week in Core.

@webcommsat adds these new links relating to 6.2:

The 6.2 live product demo Q&A

The 6.2 Field Guide

More developer notes for 6.2

4. Other release-related topics

@johnbillion raised #57916, about 6.2 server-side performance regressions. @hellofromtonya noted the ticketticket Created for both bug reports and feature development on the bug tracker. is about assessing performance and will not generate any late commits to 6.2.

@francina pointed the group to a Slack discussion on debugging tools.

5. Tickets and components

@oglekler raised ticket #23348 as a way to encourage more people to start contributing. A lively discussion followed.

@audrasjb reminded about the Old Trac Ticket Triage sessions..

@howdy_mcgee raised three tickets for early 6.3: #24142, #37255, and #18408.

@costev highlighted that he, @ironprogrammer, and @afragen are working on an update to the WordPress 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. Tester 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 that will add a section where users can report 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. right in the interface.

6. Open floor

No other items were raised.

Next week’s dev chat will be March 22, 2023 at 20:00 UTC in the Core Slack channel. See you there!

Props to @francina for leading dev chat, to @webcommsat for the agenda preparation,
@marybaum for the summary, and @oglekler and @webcommsat for review.

#6-2, #dev-chat, #meeting, #summary

Abha Thakor 8:44 pm on March 14, 2023
Tags: 6.2, ,   

Dev Chat Agenda, Wednesday March 15, 2023

The next WordPress Developers Chat will on Wednesday, March 15 2023 at 20:00 UTC in the core channel of the Make WordPress Slack.

1. Welcome and housekeeping

Dev Chat summary, March 8, 2023 – thanks to @ironprogrammer

The meeting is scheduled facilitator will be @francina and @marybaum will draft the meeting summary.
If you would like to volunteer for the summary, add a comment to this ticketticket Created for both bug reports and feature development on the bug tracker. for @webcommsat.

2. Announcements

WordPress 6.2 Release Candidate 2 (March 14, 2023). The schedule release is now only two weeks away on March 28!

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/ 15.4 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). is scheduled.

What’s new in Gutenberg 15.3? (March 13, 2023) – posted by @richtabor. This version tightens up the site editing experience, adds a new “Time to Read” 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., and some Duotone enhancements.

3. Highlighted posts

A Week in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., March 6-13, 2023 – thanks to @audrasjb

  • 48 commits
  • 62 contributors
  • 47 tickets created
  • 8 tickets reopened
  • 68 tickets closed

And welcome to the five new contributors from this week!

4. Releases

Useful information on the next major WordPress release 6.2:

New links/ key information this week:
– 6.2 live product demo Q&A – posted by @marybaum
– The 6.2 Field Guide and more Developer Notes for 6.2. 

WordPress 6.2 has branched.

Also check the #6-2-release-leads channel for the latest updates.

For information:

Any additional updates from the Release Squad will be shared in the meeting.

5. Request for help with tickets/ components/ blockers/

If you have a ticket or request to help, please add a comment to the agenda post. Please indicate if you will be attending the meeting live and be able to highlight the issue further if needed.

If you are unable to attend dev chat live, you can add further details of the issue you would like highlighted either in comments, or message Core Team reps @webcommsat and @hellofromtonya with the additional information to raise in this week’s meeting for you.

6. Open floor

Items for this agenda item and the previous one are welcome from across time zones. Please add suggestions in comments on this post. Thanks.

Props for agenda preparation @webcommsat, and review @hellofromtonya.

#6-2, #agenda, #dev-chat

annezazu 2:43 am on March 14, 2023
Tags: 6.2,   

FYI: Navigation section of new Site Editor experienced removed for 6.2 RC 2

Summary:  

The navigation section of browse mode (technical project name) is being removed for 6.2 RC 2. This does not impact the additional way of managing your menus within the 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. settings of the Navigation block. This was a joint decision across coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. editor tech leads, core editor triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. leads, and the design lead. Thank you to everyone who helped test, open issues, share designs, and ship PRs to both move this feature forward and make this decision to remove. It sets a strong foundation for reconsideration in future releases and work will continue with the feature remaining 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/ 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 to evolve.

Video explanation:

To better explain what’s changing and prevent any confusion, here’s a video detailing what’s being removed:

As a recap:

  • This change only impacts the Navigation section, meaning the Templates and Template Parts section will remain.
  • This change does not impact the additional way to manage menus with the block settings of the Navigation block.

Broader context:

6.2 introduces a new way of interacting with the Site Editor. Rather than being dropped directly into the template powering the homepage, you’ll be able to see the whole of your site. A dark-gray sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. contains a list of all templates and template parts; clicking on any of these components will preview it in the editor’s main canvas. This change in experience has used the project name “browse mode” (noted for anyone looking through 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/, 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/., etc). In Gutenberg 15.1, the last release to be fully included in 6.2, a navigation section was added to this new experience, allowing you to manage your primary navigation from the same dark-gray sidebar, preview the content of the menu items, and edit content within those templates (ie your main site structure pages). This offered a nice middle ground between fully re-introducing content editing and completely having it separated out for the release.

After being added and as 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 continued, various bugs and refinements started adding up. In particular, the top pain points revolved around which menu appears (and how to change it), needing a better description of what this newer section did, and improving the general experience of adding links from that section. For example, here’s a very short video showing how the Inserter didn’t prioritize more commonly used blocks, like a Page Link:

These issues led to various ideas for how to better contain the experience while still shipping something of value in the Site Editor, particularly to allow for some level of content editing. For example, prioritizing the Page Link in the inserter (48724) to allow for link editing or, later on, trying a “read only” view of the navigation sidebar (48971) to offer an even more locked down experience. The further in the work got though, the more changes to adapt to the browse mode section bled into other changes, like with the page list block, custom link handling, and the iterations to adding a new menu item. Even with trying to lock the experience further down, bugs continued to pop up and the experience isn’t polished enough to move forward with. This led to a decision amongst Core Editor Tech, Core Editor Triage, and the Design lead ahead of WordPress 6.2 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). 2 to remove that was then shared with the wider release squad.

This was an evolving conversation over the last few weeks that’s spread across core editor triage weekly check-ins, weekly triage for the betas/rcs/etc, Gutenberg PRs, and Gutenberg issues. For example, @Nick Diego and I have mentioned the navigation section as a pain point we’re collectively concerned about in various spots including weekly core editor triage update (including today). While this means the discussion was mainly public, it was also sprawling and took great effort to stay up to date. This leaves two main areas to improve upon: 1) recapping or having logistical discussion amongst the Core Editor Tech and Core Editor Triage more public than in either a private DM or buried in threads 2) bring more of the discussions amongst designers in the Gutenberg project into the release squad channel. This would be a great model to consider following in the future with a Gutenberg design focused discussion thread.

Related issues and PRs:

Here is a likely non comprehensive list of places where you can see discussions and iterations happening:

  • Page links are buried in the inserter and there’s a need to better prioritize commonly used blocks. Issue: 48612 PR: 48724 and 48752. You can see comments about punting to 6.3 there/what to include in 6.2 to get the experience where it needs to be.
  • Remove parent if page list block is the only block in a menu (and autoexpand): Issue: 48714. PR in progress: 48725.
  • Unclear which menu is prioritized and need to update the logic for it. PR: 48689.
  • Add a description and unify the + button placement with the other sections of browse mode. Issue: 48665. PR: 48689
  • Unable to edit page list or custom link after adding. Issue: 48593
  • Unable to edit Site Logo, Search, Spacer, Social Icon, Page List blocks. Issue: 48675.
  • Add descriptions to every single drilldown detail page: 48689
  • Prioritize Page Link in the inserter: 48724.
  • Make it possible to choose the page you link to: 48593.
  • [Bug] Submenus are added to empty page list or custom link blocks when you use the + button. Issue: 48741.
  • [Bug] Navigation section randomly changes which menu is shown if you seem to click on a page that 404s. Issue: 48744.
  • [Bug] Custom link UIUI User interface does appears outside canvas on the sidebar navigation. PR that fixed: 48633.

Once more, thank you to the immense work everyone has put into this!

If you have any questions/comments/concerns, please share below and I’ll follow up either directly or by tracking down the answer from someone who knows.

#6-2, #dev-notes-6-2