A Week in Core – September 13, 2021

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

  • 37 commits
  • 30 contributors
  • 40 tickets created
  • 4 tickets reopened
  • 25 tickets closed

As expected, WordPress 5.8.1 was released last week! Props to @desrosj and @circlecube for leading this new point releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. 🌟

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

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

  • AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility): Improve aria-label on networknetwork (versus site, blog) adminadmin (and super admin) Themes screen – #24442

Build/Test Tools

  • Fix CI for running tests on PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8.1 – #53945
  • Add more 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. IP test cases and @covers to Tests_Functions_Anonymization#53363
  • Add tests for wpdb::_real_escape()#53363
  • Fix “null to non-nullable” deprecation notice in Tests_Admin_IncludesPlugin::test_get_plugin_files_folder()#53635

Bundled Themes

  • Twenty Eleven: Set a fixed height for search form when 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. image is added – #40398

Code Modernization

  • Fix “passing null to non-nullable” deprecation in wpdb::_real_escape()#53635
  • Fix “passing null to non-nullable” deprecation notice in WP_Comment_Query::get_comment_ids()#53635
  • Fix “passing null to non-nullable” deprecation notices in WP_Http::normalize_cookies()#53635
  • Fix last parameter name mismatches for parent/child classes in Walker::start_el()#51553
  • Fix null to non-nullable deprecation in term_exists()#53635
  • Fix null to non-nullable deprecation in wp_privacy_anonymize_ip()#53635
  • Fix null to non-nullable deprecations in WP_Meta_Query::get_sql_for_clause()#53635
  • Fix parameter name mismatch with parent in WP_Customize_Custom_CSS_Setting::validate()#51553
  • Fix parameter name mismatches for parent/child classes in WP_Customize_Setting::sanitize()#51553
  • Fix parameter name mismatches for parent/child classes in WP_Customize_Setting::update()#51553
  • Fix parameter name mismatches for parent/child classes in WP_Image_Editor::save()#51553
  • Fix parameter name mismatches for parent/child classes in WP_List_Table::column_cb()#51553
  • Fix parameter name mismatches for parent/child classes in WP_List_Table::handle_row_actions()#51553
  • Fix parameter name mismatches for parent/child classes in WP_REST_Controller::prepare_item_for_response()#51553
  • Fix parameter name mismatches for parent/child classes in WP_Sitemaps_Provider::get_max_num_pages()#51553
  • Fix parameter name mismatches for parent/child classes in WP_Sitemaps_Provider::get_url_list()#51553
  • Fix parameter name mismatches for parent/child classes in WP_Upgrader_Skin::error()#51553
  • Fix parameter name mismatches for parent/child classes in WP_Widget::update()#51553
  • Fix reserved keyword and parameter name mismatches for parent/child classes in WP_Upgrader_Skin::feedback()#51553
  • Fix reserved keyword and parameter name mismatches for parent/child classes in Walker::end_el()#51553
  • Fix reserved keyword and parameter name mismatches for parent/child classes in Walker::start_el()#51553
  • Improve @since message in WP_List_Table::column_default()#51553

Documentation

  • Correct documentation for the in_plugin_update_message-{$file} 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.#40006

Editor

  • Revert [51748] and [51649]. They intorduced 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. where wp.editor may be replaced with wp.oldEditor in certain cases – #53762
  • Editor: fix the replacement of wp.editor with wp.oldEditor in the inline script outputted when enqueueing the old editor – #53762

External Libraries

  • Update jQuery UIUI User interface to 1.13.0-rc2 – #52163

General

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

Site Health

  • Add Intl to the list of recommended PHP extensions – #52654
  • Site Health: Move the Imagick entry higher in the list of recommended PHP extensions – #52654

Users

  • Introduce a meta_input argument for wp_insert_user()#41950

Widgets

Props

Thanks to the 30 people who contributed to WordPress Core on Trac last week: @hellofromTonya (26), @jrf (26), @azaozz (19), @desrosj (18), @johnbillion (15), @sergeybiryukov (15), @audrasjb (2), @david.binda (2), @sabernhardt (2), @Clorith (2), @Soean (1), @davidmosterd (1), @BinaryKitten (1), @donmhico (1), @peterwilsoncc (1), @mdawaffe (1), @get_dave (1), @grantmkin (1), @fullofcaffeine (1), @lukecavanagh (1), @josklever (1), @mukesh27 (1), @zieladam (1), @andraganescu (1), @fedepia (1), @zodiac1978 (1), @mgol (1), @JavierCasares (1), @zeo (1), and @SergeyBiryukov (1).

Congrats and welcome to our new contributor of the week: @josklever ♥️

Core committers: @hellofromtonya (26), @sergeybiryukov (6), @azaozz (3), and @johnbillion (2).

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

Week in Core: Sept. 21-27, 2015

Oh Snap!, it’s time to usher in a new edition of Week in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.! If you have the time, throw a house party with some friends and read the full force of changes on Trac; if not, don’t sweat it — take simple pleasure in these highlights.

This post covers changesets [34362][34658], committed during Sept. 21–27, 2015. Let’s give a hi-five and some TLC to the 102 contributors for a combined 296 updates! Together, we’re making WordPress nice & smooth.

Continue reading

#4-4, #week-in-core

Component Page Updates for 4.4

Now that 4.4 is underway, let’s update the component pages to reflect 4.4 activity. The Customize, Editor, and Press This pages serve as good templates, though they all need 4.4 updates. The component pages are targeted at 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. testers. They should describe the component, list milestones (roadmap), and explain what needs testing and how to test it. Good component pages assist triage. For details, see the previous round of component page updates.

Also, if your component has a corresponding 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/. chat, link to the component page from the chat’s channel topic. This assists using Slack in beta testing flows.

Component maintainers, here are your component pages…

Continue reading

#components, #maintainership

Commit announcements for 3.9

Lots of news to share! First: Helen Hou-Sandí has had guest commit for the past three release cycles. She’s been spending the last year reviewing contributions, mentoring contributors, and working on some of our larger UIUI User interface projects. I’m proud to announce @helen is now a permanent committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. to WordPress!

We’ve invited John Blackbourn (@johnbillion) to be a committer for the 3.9 cycle. His strong, consistent contributions have been backed by excellent judgment and temperament.

Matt Thomas, who led the dashboard redesign in 3.8 (and 3.2, and 2.7, etc.), will keep his commit to continue to maintain and improve WordPress UI. He’s been a great mentor to many contributing designers and his long-term impact is indelible.

For the last few years, we’ve been granting commit access on per-cycle basis, sometimes for a particular component, feature, etc. Generally, after about a year, a guest committer can be considered for permanent commit access. Dominik Schilling, Sergey Biryukov, Drew Jaynes, and Scott Taylor have all had their commit extended for 3.9.

Drew (@DrewAPicture) was given temporary commit for inline documentation starting with 3.7. He’s been heading up the long-running initiative to document every hook in WordPress. Scott (@wonderboymusic) also started committing during 3.7, and has a particular penchant for digging deep into the query and taxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. https://codex.wordpress.org/Taxonomies#Default_Taxonomies. APIs. And Sergey (@SergeyBiryukov) and Dominik (@ocean90), well, they are forces of nature.

(@aaroncampbell was also given guest commit in 3.7, but he ended up not having much time to use it.)

Here’s a full list of those with permanent commit: @markjaquith, @ryan, @westi, @matt, @azaozz, @dd32, @koopersmith, @duck_, @helen, and me (@nacin); @lancewillett for bundled themes; @iammattthomas for UI. You might have also seen commits before from @josephscott (XML-RPC), @nbachiyski (internationalization), and @mdawaffe (secret weapon for really tricky problems).

Next weekly meeting is January 8. Happy new year, everyone. Here’s to a great 2014.

#3-9, #commit

Revisions Update, 2/5

Yesterday’s meeting focused on revisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. to the revisions interface :). @lessbloat joined us to ask some great questions, and helped refocus the UIUI User interface changes that have been proposed and mocked up so far. We started off by trying to identify the major uses of revisions, and settled on two primary cases: undoing mistakes by finding the last correct revisions, and reviewing changes as part of an editorial workflow.

In light of those focuses, we’ve decided to revisit the UI mockups we’ve (namely, @karmatosed and @adamsilverstein) worked on so far. The general consensus is that they’ve become overly complicated, and led to feature creep (looking at you, line-by-line accept/reject capabilities). @karmatosed is working on some new mockups for Thursday’s office hours. One possible source of inspiration may be @benbalter’s post forking plugin.

On the code side, @mdawaffe worked out a pretty comprehensive patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. for the display of incorrect authors on revisions (#16215). We’ll be reviewing that, along with the patches added to the other tickets we’ve scoped for 3.6. As was the case when I last posted, progress is slow at this point due to travel and the ongoing UI discussions.

[IRC log]

#3-6, #revisions

Write a tutorial for setting up a local dev environment

A section of the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. contributor handbook will be about how to set up a local test install, including a web server, Subversion, and WordPress. Because of the various operating systems and software packages out there, we’re going to need a few different tutorials.

I need some people willing to write up procedures for a number of standard setups. This includes:

  • WordPress on XAMPP (both Windows and Mac) MAMP, and MacPorts
  • TortoiseSVN and a tutorial on command-line Subversion usage, including co, up, revert, diff; 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.; conflicts, etc.
  • Whatever you Linux guys use 🙂

I’d also love an article on getting the test suite up and running. Anything I’m missing?

So, for these procedures, people can volunteer (probably for their current setup). Once steps are written, others will need to test them. Many procedures may heavily borrow from or link to outside resources (such as the vendor sites themselves) — this is fine. And, there may already be some good things in the Codex or on other sites about getting WordPress running. Again, fine. (There are SVNSVN Subversion, the popular version control system (VCS) by the Apache project, used by WordPress to manage changes to its codebase. articles by both @westi and @markjaquith, and those are probably great to start from.) Gather links, screenshots, further reading, whatever will help.

So, who is in?

#core-contributor-handbook

/extend is currently being upgraded. Cur…

/extend is currently being upgraded. Currently @mdawaffe is working on the plugins directory. Please excuse any ceiling tiles if you’re hit with one.

#3-org, #infrastructure