New Contributors Meeting Recap – February 14th

On Wednesday, February 14th, the weekly new contributor meeting was held in the #core Slack room. Here is a recap of the meeting. A full chat log is also available.

Participants: @adamsilverstein @abdullahramzan @aduth @chetan200891 @clorith @desrosj @dougvanslembrouck @jorbin @joyously @lakenh @notnownikki @thrijith @welcher @williampatton @xkon

Discussion Highlights

Contributing with Git

Even though every change to WordPress core must pass through Trac/SVN eventually, SVN is not the only option for creating patches.

See these articles for more intofmation on creating patches with Git:

Coding standards

An easy way to make your IDE/editor aware of the WordPress coding standards regarding whitespace usage is to use the .editorconfig file that trunk contains. This file uses a common standard, and there are plugins available for almost all popular environments that automatically parse the file and adjust the whitespace settings for the project.

Extensions can be found on the website of the project. Some IDEs like PHPStorm already come with built-in tools for the WordPress coding standards.

Refreshing a patch

Older tickets often have attached patches that no longer apply to the current codebase. The older the ticket, the lower the likelihood that the associated patch will apply cleanly. If you find a ticket with a patch that does not apply, add the needs-refresh keyword to indicate this.

Over time, code shifts around and sometimes these patches only need a bit of reorganization to apply. Other times, you may find code that has been refactored and needs an alternative solution for the proposed bug/enhancement. Once this has been done, create a new patch with the clean code and submit it to the ticket.

While refreshing a patch, it’s also a good idea to make sure the patch is what you would consider the best approach and to verify that it follows the style guide.

See Contribute with Code handbook article for more information.

Ticket ownership

Ticket owner is generally responsible for moving the ticket forward. From the handbook:

When working on a ticket, the Owner field is typically left blank, even if you have contributed a patch. Committers utilize the field to offer traction for a ticket, to identify they are investigating, committing, or otherwise following a ticket, or to tentatively accept the bug or enhancement for core inclusion. It is also common during the feature development phase for developers to accept tasks in the area of responsibility for which they have volunteered, as well as related bug reports. Trusted contributors may assign tickets to others based on an inside knowledge of who should be responsible for reviewing it.

For good-first-bugs, the person who submitted the patch is assigned as an owner so that the ticket shows as “claimed” in the queue.

It’s OK to drop ownership if the ticket is no longer relevant for you, just reassign it to an empty field.

See The Bug Tracker (Trac) handbook article for more information.

Tickets brought up

  • @notnownikki has been working with @iseulde and @azaozz on #43187, which comes from an issue in Gutenberg.
  • @williampatton asked for feedback on #42057, specifically opinions on introducing an additional parameter for a function in a minor release, and more eyes on back compat to make sure nothing is broken by the change.

Thanks to everyone who attended! As always, please feel free to leave a comment below or reach out to any of the moderators (@adamsilverstein, @desrosj, @flixos90, @sergeybiryukov, @stevenkword, @welcher) with questions on Slack. Or, feel free to reach out to any core developer or component maintainer with questions specific to certain core areas.

#core, #new-contributors, #summary

WordPress 4.9.3 Release Candidate

WordPress 4.9.3 maintenance release fixes 34 issues reported against 4.9 and is scheduled for February 5th. The release candidate is now ready for testing.

Thus far WordPress 4.9 has been downloaded more than 34 million times since its release on November 16, 2017. Please help us by testing this RC to ensure 4.9.3 fixes the reported issues and does not introduce any new ones.

JSHint Removal

One of the important changes is the removal of JSHint from code editor due to its GPL-incompatible license. If your code relies upon JSHint from core, you should update it to include a copy of JSHint. See ticket #42850 for more details.

Changes Since 4.9.3 Beta

Code Editor

  • #42586 Add Ctrl/Cmd+F as aliases for persistent search for more intuitive behaviour.


  • #42450 Ensure customize_autosaved requests only use revision of logged-in user.
  • #42495 Ensure media playlists get initialized after selective refresh; expose new wp.playlist.initialize() API.
  • #42658 Ensure heartbeat keeps changeset locked when in branching mode.
  • #42991 Include nav menu item for Home custom link in search results for "Home".


  • #39859 Avoid page scrolling when opening the media modal.

For a full list of changes see the 4.9.3 Beta posttickets closed, and the changesets committed.


WordPress 4.9.3 Beta

As mentioned in the last dev chat, WordPress 4.9.3 maintenance release is scheduled for January 30th.

The beta package for 4.9.3 is now ready for testing. Please help us by testing this beta to ensure 4.9.3 fixes the reported issues and doesn’t introduce any new ones.

JSHint Removal

One of the important changes is the removal of JSHint from code editor due to its GPL-incompatible license. If your code relies upon JSHint from core, you should update it to include a copy of JSHint. See ticket #42850 for more details.

Other Changes

Other notable fixes and enhancements include:


  • #15397 redirect_guess_404_permalink() doesn’t guess posts with updated dates


  • #42646 Customizer cropper settings don’t respect flex-width=false and flex-height=false
  • #42686 Default selected changeset status should not be ‘publish’ when current user does not have publish capability
  • #42975 Customize: Previewing a changeset locks the changeset


  • #43109 RegEx in parse_db_host() can cause notices and headers sent too early


  • #42862 Update Twemoji to v2.4.0


  • #42643 No download link if a FLV file cannot be rendered


  • #42860 PHP 7.2 warning in WP_Query::set_found_posts()


  • #42597 “Term already exists” error no longer returns term ID


  • #42697 Missing Translations update section


  • #42503 Visual mode does not work in Internet Explorer 11
  • #42722 TinyMCE JS error preventing plugins from loading
  • #42908 Additional markup inserted when editing shortcodes and switching between Visual/Text tabs
  • #43090 Extra dots in in TinyMCE toolbar dropdowns in Microsoft Edge


  • #42693 WordPress sends an “admin email address was changed” message to on new install
  • #43103 Reduce plugin/theme API calls during core release windows


  • #42740 Image Widget does not support relative links
  • #42802 Custom HTML widget validation does not allow single-quoted attributes
  • #43003 HTML5 “required” attribute in Widget form() fails in ajax-actions.php during save
  • #43125 Deregistering WP_Widget_Media_Image breaks Text widget’s “Add Media” button

See the full list of closed tickets in Trac.


Dev Chat Summary: November 29th (4.9.1 week 2)

This post summarizes the dev chat meeting from November 29th (agenda, Slack archive).

4.9 feedback + 4.9.1 timing

WordPress 4.9.1 was released last week. It's a security and maintenance release for all versions since WordPress 3.7, users are strongly encouraged to update their sites immediately.

Notable bug fixes include:

  • Issues relating to the caching of theme template files.
  • A MediaElement JavaScript error preventing users of certain languages from being able to upload media files.
  • The inability to edit theme and plugin files on Windows based servers.

This post has more information about all of the issues fixed in 4.9.1 if you'd like to learn more.

Gutenberg usability testing + contributions

There are new usability tests for Gutenberg.

There was also a usability testing table for Gutenberg at WordCamp US this weekend, as well as a dedicated Gutenberg section at the Contributor day.

General announcements

@davefx: Looking for feedback on #42669.

#4-9-1, #core, #dev-chat, #gutenberg, #summary

Weekly Bug Scrubs for 4.4

There’s been a lot of activity on 4.4 already, let’s keep the momentum and start up weekly bug scrubs for the 4.4 cycle. Scrubs are a concentrated period of time for contributors to triage Trac tickets while other people are around at the same time.

Where: The scrubs will be held in the #core channel on Slack.
When: Each Friday, starting with Friday, September 4 2015 16:00 UTC.

The goal is to work for about an hour to triage tickets on the 4.4 milestone and try to provide feedback and make progress on as many tickets as we can, to keep the milestone under control.

See you there!

#4-4, #bug-scrub

Weekly Bug Scrubs

During the latest dev chat we’ve decided to schedule a weekly bug scrub in IRC for the next few weeks each Friday at 11AM Eastern/16:00 UTC, for two hours. Please join us if you’d like to participate in reviewing the patches currently slated for 3.6.

#3-6, #bug-scrub, #maintenance

Ticket Scrub

We’ll have a patch clearing session in IRC on Friday, February 8 at 11AM Eastern/16:00 UTC, for two hours. Let’s aim to go through the commit candidates and resolve some of the other tickets currently slated for 3.6.

#3-6, #bug-scrub, #maintenance