Wayback Machine
«OCT NOV DEC »
Previous capture 6 Next capture
«2020 2021 2022
0 captures
31 Oct 19 - 28 Oct 22
Close Minimize Help

WordPress.org

Welcome!

The WordPress core development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:

Communication

We use Slack for real-time communication. Contributors live all over the world, so there are discussions happening at all hours of the day.

Our core development meetings are every Wednesday at 20:00 UTC in the #core channel on Slack. Anyone can join and participate or listen in!

Make WordPress Core

Keyboard Shortcuts | Hide comment threads

Bug Scrub Schedule for 5.9

With 5.9 well underway, we’re ready to schedule the 5.9 bug scrub sessions. These 5.9 specific ticket scrubs will happen each week until the final release.

Alpha Scrubs:

Hosted by @audrasjb

Hosted by @chaion07 (APAC-friendly)

Beta Scrubs:

Focus: issues reported from the previous beta.

RC Scrubs:

Focus: issues reported from the previous RC

Check this schedule often, as it will change to reflect the latest information.

What about recurring component scrubs and triage sessions?

The above 5.9 scheduled bug scrubs are separate and in addition.

For your reference, here are some of the recurring sessions:

  • Twenty Twenty-Two Triage: Every Monday 15:00 UTC in the #core-themes channel.
  • Gutenberg Design Triage: Every Tuesday 16:00 UTC in the #design channel.
  • Accessibility Scrub: Every Friday 15:00 UTC in the #accessibility channel.
  • Testing Scrub: Every Friday 13:15 UTC in the #core-test channel.
  • CSS Scrub: First Thursday of every month 20:00 UTC in the #core-css channel.
  • Upgrade/Install Component: Every Tuesday at 17:00 UTC in the #core-auto-update channel.
  • Help/About Component: Every Monday, 19:00 UTC in the #core channel.

Want to lead a bug scrub?

Did you know that anyone can lead a bug scrub at anytime? Yes, you can!

How? Ping @audrasjb or @chaion07 on slack and let us know the day and time you’re considering as well as the report or tickets you want to scrub.

Planning one that’s 5.9-focused? Awesome! We’ll add it to the schedule here. You’ll get well deserved props in the weekly Dev Chat, as well as in the #props Slack channel!

Where can you find tickets to scrub?

  • Report 5 provides a list of all open 5.9 tickets:
    • Use this list to focus on highest priority tickets first.
    • Use this list to focus on tickets that haven’t received love in a while.
  • Report 6 provides a list of open 5.9 tickets ordered by workflow.

Need a refresher on bug scrubs? Checkout Leading Bug Scrubs in the core handbook.

Questions?

Have a question, concern, or suggestion? Want to lead a bug scrub? Please leave a comment or reach out directly to @audrasjb or @chaion07 on slack.

Thanks @jeffpaul for proof-reading.

#5-9, #bug-scrub

CSS Chat Agenda: November 4, 2021

The next weekly CSS meeting is today Thursday, November 4, 2021, 05:00 PM EDT in the #core-css channel in Making WordPress Slack. If there are any other topics you’d like to discuss, please leave a comment on this post.

There will also be a Core CSS Triage starting at 20:00pm UTC, an hour before the meeting.

Meeting Agenda

  • Welcome (21:00pm UTC)
  • Announcements & housekeeping
  • CSS Custom Properties (#49930)
  • Open floor / CSS link share

See you there!

#agenda, #core-css

Dev Chat Summary: November 3, 2021

@francina led the weekly meeting at 20:00 UTC. Here is the meeting agenda.

Link to this <dev-chat> in #core on Making WordPress Slack.

Notable news and blog posts

Component Team Updates

Core

  • PHP 8.1 compatibility fixes #53635
  • PHP Coding Standards fixes for 5.9 #53359
  • Removed role="navigation" from Core & Bundled Themes #54054
  • Permalinks: sanitize non-visible characters. #47912

@francina and @audrasjb highlighted the call for new Core Team reps for the next calendar year, emphasized reps do not need to be experienced contributors or developers to fill the role and outlined some of the main tasks.

Also, contributors are still needed for the WordPress 5.9 Release Squad (details on the responsibilities).

Build/Test Tools

  • Preliminary work on visual regression tests in Core. #49606
  • Continuing work on end-to-end (e2e) tests in Core. #49507
  • Add missing @covers to PHPUnit tests. #39265
  • Improving Slack Notifications via GitHub Actions. #53363

Date/Time

  • Improved inline documentation #53399

About/Help

Editor

  • Gutenberg 11.9 (the last release going into WordPress 5.9) has an RC cutoff of November 5.

Open Floor

  • @hellofromtonya called out the WordPress 5.9 Feature Freeze is November 9. Work then shifts to defect tickets until the 5.9 Beta 1 target date of November 16.
  • @francina brought up a Gutenberg PR (36168) to remove the Customizer menu item when Block Themes are active. @johnbillion raised #54370 in relation to this change. If you build a Plugin extends the Customizer, please test with this change!

Watch For

#5-8-2, #5-9, #dev-chat, #summary

Performance team meeting summary – November, 2 2021

@justinahinon led the meeting. You can also read the Slack logs.

Performance team resources/reading materials

If this is the first time you are hearing about the WordPress performance team, here are some links to get you started:

Defining focus areas and working groups

Since the initial post on the proposal to create the team, there have been additional ideas on what it should work on. We need a bit of prioritization. Of course all performance work is important, and all contributions are welcome, as always.

To have a guideline for the next steps, the attendees decided to choose in the spreadsheet mentioned above from the aspects that have the highest number of interested contributors. These topics will be organized in working groups, that will be discussed during the weekly meetings.

Here are the working groups:

  • Images: Serving images in good quality but as small as possible
  • JavaScript: Optimizing JavaScript orchestration
  • Site Health: Providing the user with data to understand performance
  • Measurement: Compiling data and analysis, and reporting on performance

To make sure we are making steady progress, we asked for at least one volunteer per working group to commit to attending weekly meetings to give updates on what is being done, and possibly how other contributors could help. Here’s the thread on Slack where you can express your interest in doing so.

Next steps for this team

The next steps for the team and the working groups are the following:

  1. Define the logistics for each group (tracking, POCs etc.)
  2. Kickoff meeting for each 4 area

If you are interested in exploring or helping with one of these, please feel free to add their .org username in the Focus Area speadsheet.

Open Floor

Several ideas were brought up during the meeting, about the organization of the team, potential tools or ideas for exploration. Here are some of them:

About tooling/documentation/information about performance and monitoring

About some work that is already being done for performance

@audrasjb is doing some work for the Site Health focus. Audras is working on a feature plugin on Benchmarks in Site Health, number of CSS/JS assets loaded.

Thanks @francina and @tweetythierry for the peer review

#meeting, #performance, #performance-chat, #summary

Dev Chat Agenda for November 3, 2021

Here is the agenda for this week’s developer meeting to occur on Wednesday, November 3, 2021 at 08:00 PM UTC.

Please note that depending on your timezone, the time may have changed with the end of daylight saving time.

Blog Post Highlights and announcements

Bringing to your attention some interesting reads and some call for feedback and/or volunteers:

Next releases status update

Have you been working on 5.9 related issues? Let everyone know!

Components check-in and status updates

  • Check-in with each component for status updates.
  • Poll for components that need assistance.

Open Floor

Do you have something to propose for the agenda, or a specific item relevant to the usual agenda items above?

Please leave a comment, and say whether or not you’ll be in the chat, so the group can either give you the floor or bring up your topic for you accordingly.

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

#5-9, #agenda, #core, #dev-chat

I am not sure I’ll be able to attend – I’ll do my best.
Nevertheless, I’d like to bring up this PR http://wayback.fauppsala.se:80/wayback/20211106150451/https://github.com/WordPress/gutenberg/pull/36168
The reasoning is sound, but there might be an issue with plugins that rely on the customizer. They will need it also if the website has a block theme activated.
Will they be able to perform the same actions “somewhere else” (blocks, plugin settings, etc…)? cc @ipstenu
Thanks!

@francina Sorry, I was nasty-sick yesterday. Not sure what the question is?

WordPress 5.8.2 RC 1

WordPress 5.8.2 Release Candidate 1 (RC1) is available for testing!

Some ways you can help testing WordPress 5.8.2 RC1:

What’s in this release candidate?

5.8.2 Release Candidate 1 features 3 bug fixes on Core.

The following core tickets from Trac are fixed:

  • #54207 – ca-bundle.crt contains expired certificate DST Root CA X3
  • #54129 – Undefined index posts_per_page in ajax-actions.php
  • #54323 – Too few arguments for function (closure)

What’s next?

The dev-reviewed workflow (double committer sign-off) is now in effect when making any changes to the 5.8 branch.

As per the proposed WordPress 5.8.2 schedule, the final release is expected on Wednesday, November 10, 2021. Please note that this date can change depending on possible issues after RC1 is released. Coordination will happen in the WordPress.org Slack #5-8-release-leads channel.

A special thanks to everyone who helped test, raised issues, and helped to fix tickets. With this release candidate testing continues, so please, help test!

The 5.8.2 release is being led by @desrosj and @circlecube.

Props @circlecube and @audrasjb for peer review.

#5-8, #5-8-2, #minor-releases, #releases

Core Editor Improvement: Introducing template part focus mode

These “Core Editor Improvement…” posts (labelled with the #core-editor-improvement tag) are a series dedicated to highlighting various new features, improvements, and more from Core Editor related projects. 

With more tools to edit your entire site, this new view was created to allow folks to have a space to focus specifically on editing a single template part, like a header or footer. At a high level, this focused mode helps eliminate distractions when editing template parts, provide a pathway for backwards compatibility, and opens up new possibilities around permissions.

You will be able to access this mode in a few ways once Gutenberg 11.9 is released and, if all goes well, in WordPress 5.9: 

  • Select the template part in the Site editor > Click on the three dot menu > Select “Edit Header” or the respective template part name. 
  • Select the template part in List View > Click on the three dot menu > Select “Edit Header” or the respective template part name. 
  • From the Browsing sidebar > Navigate to Template Parts > Select the template part you want to customize.
  • From the Top Toolbar > Click on the three dot menu under “Areas” next to the template part you want to customize.

Keep in mind that some of these flows may change as the site editing flows get prepared for 5.9!

As you explore this mode, you’ll notice a few extra touches too, including the visual background similar to the template editor mode to indicate that you’re in a new editing environment and the ability to resize the editing field horizontally with drag handles. There’s always more to be done though, particularly around clarifying when different edits are global vs local.

Looking forward, this work will ultimately pave the path for a smooth transition into block themes by turning existing widget areas into block template parts. It also creates the ability to have only folks with certain permissions the ability to edit a template part directly, building on the work around template locking. The UX lessons learned from this effort will inevitably benefit future projects like the Navigation Editor too!

For a deep dive of all that went into this project, check out this overview issue. To be on the cutting edge, use Gutenberg 11.9 when it’s released or check out the current version today to get a sense of what it can do without the latest and greatest PRs. If you’re game to wait a bit longer, expect to see it in WordPress 5.9 coming in December. 

Thank you to @jameskoster for the video and @priethor @bph @kevin940726 for reviewing the content.

#core-editor, #gutenberg

Editor Chat Agenda: 03 November 2021

Facilitator and notetaker @ajitbohra

This is the agenda for the weekly editor chat scheduled for Wednesday, 03 November 2021, 14:00 UTC.

This meeting is held in the #core-editor channel in the Making WordPress Slack.

Even if you can’t make the meeting, you’re encouraged to share anything relevant for the meeting in the comments below:

  • If you have anything to share for the Task Coordination section, please leave it as a comment on this post.
  • If you have anything to propose for the agenda or other specific items related to those listed above, please leave a comment below.

#core-editor #core-editor-agenda #agenda #meetings

For task coordination

During the past week, I’ve been focused on reviews to move 5.9 tasks forward, bug fixes, and a couple of bigger things:

  • Migrate theme.json v1 to v2. Existing themes with theme.json v1 still work as expected, but we’re preparing things to land in 5.9, which means cutting a new version for theme.json.
  • The PR to show colors from different sources uncovered a dormant bug that did not have any effect until now and that we’re fixing here. The fix is to stop retrofitting the filtered settings from the `block_editor_settings` into theme.json and instead use the theme supports directly. This may affect plugins that used the `block_editor_settings` to change theme support values, and they should be updated to use the `after_theme_setup` filter instead.

For next week, I plan to keep helping with reviews, bug fixes, and porting code to WordPress core.

A Week in Core – November 1, 2021

Welcome back to a new issue of Week in Core. Let’s take a look at what changed on Trac between October 25 and November 1, 2021.

  • 33 commits
  • 38 contributors
  • 44 tickets created
  • 5 tickets reopened
  • 34 tickets closed

The Core team is currently working on the next point (5.8.2) and major (5.9) releases 🛠

Worth noting that each feature slated to the 5.9 milestone has been validated, that the Twenty Twenty-Two Theme development is on the way, and the 5.9 bug scrub schedule has been published 🚀

Ticket 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

  • Hide mobile menu on focusout – #53587

Application Passwords

Build/Test Tools

  • Adjust Slack notifications for scheduled and workflow_dispatch events – #53363
  • Escape $ within commit messages for $variables#53363
  • Ignore “null to nullable” deprecations for select tests – #53635
  • Use correct URL for a GitHub Action workflow run – #53363
  • Some test improvements for clean_dirsize_cache() tests: – #52241, #53363

Coding Standards

  • Correct alignment in WP_Site_Health::get_test_update_temp_backup_writable()#51857, #53359
  • Correct alignment in wp_enqueue_global_styles()#53359
  • Rename the $process variable to $processed_response for clarity in WP_Http_Streams::request()#53359

Date/Time

  • Improve the docblocks for various date and time related functions – #53399, #28992, #40653

Docs

  • Add a @since note for the rest_namespace argument of register_post_type() and register_taxonomy()#53399
  • Add a @since note to WP_REST_Post_Types_Controller::get_item_schema() for the supports and visibility properties – #53399
  • Document the usage of some globals in wp-includes/script-loader.php#53399
  • Further update the debug_information filter description per the documentation standards – #53399
  • Miscellaneous docblock improvements – #53399
  • Miscellaneous docblock improvements – #53399

Editor

  • Include post’s title in editor title element – #52314

General

  • Remove role="navigation" from nav elements – #54054

HTTP API

  • add suggested filename support to download_url()#38231

KSES

  • Add options for restricting tags based upon their attributes – #54261

Media

  • Close attachment details modal with esc key – #53924
  • Remove deprecated click function in media uploader – #53261

REST API

  • Add visibility information to the Post Types controller – #54055
  • Send a 500 status code when JSON encoding fails – #53056
  • Support custom namespaces for custom post types – #53656
  • Support custom namespaces for taxonomies – #54267

Role/Capability

  • Add support for capability queries in WP_User_Query#16841

Script Loader

  • Correct the number of arguments passed to the closure in enqueue_block_styles_assets()#54323

Site Health

  • Correct and improve the documentation for the debug_information hook – #53399
  • Internationalizes count in the info section headings – #54341

Widgets

  • Use a text-based button to select location – #53311

Props

Thanks to the 38 people who contributed to WordPress Core on Trac last week: @swissspidy (5), @sabernhardt (4), @spacedmonkey (4), @peterwilsoncc (3), @costdev (3), @dd32 (2), @jrf (2), @ocean90 (2), @AmethystAnswers (1), @sourovroy (1), @kaneva (1), @vondelphia (1), @boonebgorges (1), @scribu (1), @lgladdly (1), @SergeyBiryukov (1), @aristath (1), @shimon246 (1), @gziolo (1), @cklosows (1), @johnjamesjacoby (1), @kapilpaul (1), @jorbin (1), @desrosj (1), @lalitjalandhar (1), @hermpheus (1), @pento (1), @isabel_brison (1), @kevin940726 (1), @juhise (1), @justinahinon (1), @mukesh27 (1), @hellofromTonya (1), @audrasjb (1), @alexstine (1), @skierpage (1), @johnbillion (1), and @psrpinto (1).

Congrats and welcome to our 5 new contributors of the week: @shimon246, @lalitjalandhar, @sourovroy, @vondelphia, and @kaneva ♥️

Core committers: @sergeybiryukov (9), @joedolson (6), @johnbillion (5), @timothyblynjacobs (4), @hellofromtonya (3), @desrosj (3), @pento (1), @swissspidy (1), and @johnjamesjacoby (1).

#5-8-2, #5-9, #core, #week-in-core

Editor chat summary: 27 October, 2021

This post summarizes the weekly editor chat meeting (agenda here) held on  Wednesday, October 27 2021, 04:00 PM GMT+1. in Slack. Moderated by @andraganescu.

General updates

Future agendas we should drop the “What’s Next in ..” reminder link as the Go/No Go post supersedes the “What’s Next”.

@juanmaguitar asked who are the Proposed WordPress 5.9 Leads and got directed to the early squad list here that should be published soon.

@noisysocks mentioned Gutenberg 11.9 is the last plugin release which will make its way into WP 5.9. It will be “cut” on November 3 which is very soon.

Key project updates

Based on the scope for Site Editing projects.

Template Editor

Global Styling

@jorgefilipecosta provided an update:

  • A PR proposing the new color palette editor and a PR that makes multiple color palettes from different sources available to users were proposed PR 35783PR 35783.
  • The new global styles REST API endpoints are also in progress PR 35801PR 35985, and at least the endpoint for user styles should be merged in the next hours.
  • The new design is based on progressive disclosure UI where all the options are not visible right away that is based on using the new tools panel on the multiple block supports that exist, and that work is also in progress for colors and borders PR 33743PR 34027

Patterns

  • @ntsekouras explained that while the  patterns tracking issue suggested to implement a way for allowing themes to surface specific patterns from the pattern directory, in reality development is tightly coupled with the pattern directory and the current ‘closed’ submission system, so more exploration needs to happen.

Navigation Block & Navigation Editor

@getdave provided an update:

Mobile Team

@hypest provided an update:

Shipped

  • Rolled out in-editor Help screen and new-block Inserter Badge to all users.

Fixes

  • Pin Node to v14 on CI to match Gutenberg web’s CI.
  • Autosave issue in the Unsupported Block Editor.
  • iOS Safe Areas issue in the in-editor Help screen.
  • Fixed a loading glitch in the embed blocks.

In Progress

  • Adding more tests for the Embed block.
  • GSS Font size, line height, colors.

Task Coordination

@mamaduka

@jorgefilipecosta

@bph

  • Tomorrow Live Q & A on Converting classic Widget to blocks w/ Buddy Press team @imath  @vapvarun and @dcavins  – Join us and/or share in your network. It will be streamed to YouTube as well. (by the time meeting notes come out we might have a recording on YouTube. )
  • Prep and recording of Gutenberg Changelog episode 54 – Gutenberg 11.8 and more. w/ @gziolo
  • Developer Hours to start mid November. Coordination work ongoing.
  • Preliminary prep for WordPress 5.9 documentation

@getdave

@ajlende

@annezazu

  • accepted test co-lead for 5.9 along with helping with user docs
  • working on the next round of FSE answers,
  • working on figuring out next call for testing,
  • doing some light triage + testing!

@colorful-tones

  • I’m looking for some guidance on Global Styles: Form elements. I’m looking to dive in today and get a PR going, but want to make sure I have scope and scale in mind for adding any features.

Open Floor

@cbravobernal asked about issues because of getting block attributes with style and class together in a string and pointed to the trac issue.

@overclokk raised an issue detailing a proposal to remove block-templates and block-templates-parts directories for FSE – Full site editing

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

s
search
c
compose new post
r
reply
e
edit
t
go to top
j
go to the next post or comment
k
go to the previous post or comment
o
toggle comment visibility
esc
cancel edit post or comment
0
:)