grunt-patch-wordpress 1.0.0

I am proud to announce the immediate release of grunt-patch-wordpress version 1.0.0 which brings in the ability to change the location of files, reformats all of the code to bring it inline with the current WordPress coding standards, and fixes a small number of bugs. This release also bumps the minimum version of node.js to be inline with the current WordPress core minimum version.

File mapping is the big feature, as that will help with #43055 and any other future file reorganizations. 

Using the file_mappings option

If you'd like to map old file paths in your patch to new file paths during the patching process, you can pass a file mappings object as an option. Using this option can be helpful when the file paths in the project have been changed since you've created your patch.

The file mappings object should contain old file paths and the corresponding new file paths. In the Gruntfile.js of your project, this would look like this:

patch: {
	options: {
		file_mappings: {
			'old_path1': 'new_path1',
			'old_path2': 'new_path2',
			'old_path3': 'new_path3',

In this example, the patch task will look for 'old_path1', 'old_path2' and 'old_path3' in your patch and replace them during patching with 'new_path1', 'new_path2', and 'new_path3' respectively.

Thanks to @pento, @netweb, @boblinthorst, @ireneyoast, @omarreiss, and @herregroen for contributing to this release and to all of the contributors who have helped make grunt-patch- wordpress what it is today.

JSHint removed from CodeMirror in 4.9.3

CodeMirror was introduced to WordPress 4.9 for an improved code editing experience. For JavaScript linting, CodeMirror uses JSHint which unfortunately includes some code that isn't compatible with the GPL. Therefore, in WordPress 4.9.3, we are removing JSHint and replacing it with esprima and a custom wrapper to provide some basic linting for JavaScript. This allows the code editor to show compilation errors, but not errors in formatting. 

If your code relies upon JSHint from core, you should update that code to include a copy of JSHint.  Please note that as JSHint isn't currently GPL compatible, it can not be distributed in the WordPress Plugin Repository. 

For more info, please see #42850.

#4-9, #4-9-3, #codemirror, #dev-notes, #jshint

4.7 Retrospective

A retrospective meeting on the WordPress 4.7  release will be held during the week of December 19th. In order to properly prepare for that retrospective and make the time as productive as possible, I would like to encourage everyone to comment below with things they would like to bring up. To help, here are three good questions to ask yourself:

  • What should WordPress start doing as a part of the development process?
  • What should WordPress stop doing as a part of the development process?
  • What should WordPress continue doing as a part of the development process?

Please remember when commenting to keep the discussion professional and focused on ways the process of creating WordPress is either already working great or can be improved.

#4-7, #retrospective

WordPress 4.7 Field Guide

WordPress 4.7 is shaping up to be the best WordPress yet!  Users will receive new and refined features that make it easier to “Make your site, YOUR site”, and developers will be able to take advantage of 173 enhancements and feature requests added.  Let’s look at the many improvements coming in 4.7…

RESTing, RESTing: 1, 2, 3

The foundation for RESTful APIs has been in core since 4.4, and 4.7 sees the addition of Content Endpoints after a healthy discussion. We’ve defined four success metrics as part of the merge discussion and you can help by building themes and plugins on top of the API, using the API in custom development projects, and utilizing the API for a feature project, core features, or patches. So, dive in, start playing around, and let us know what you build!


It don’t mean a thing, if you ain’t got a theme

No matter if you are building themes for public consumption, as a bespoke project for a major public company, or anything in between WordPress 4.7 has something to help you.

The Voyages of USS Media

Two notable changes, enhanced PDF support in the media library and changes to the default fallbacks for image alt attributes, are explained in separate posts.

Media also received other exciting enhancements and bug fixes you should check out.

Around the World

The way users understand the words on WordPress are important and now users will be able to select their personal preferred language.


For Whom Customization Tolls

The customize component will now support the ability to create pages within live preview during site setup; will have a faster, smoother, and more accessible navigation; will automatically persist your changes in the background while you browse your site and switch themes; and will let you fine-tune your site with custom CSS.


Reading, Writing and Teriffic

Whether you’re creating content in the WordPress Admin or concerned about comment moderation, we’ve got updates that will be sure to please you.


The Foundation of WordPress

For those who like to get “under the hood” of WordPress, we’ve got some improvements that will hopefully make your life easier.


But Wait, There is More!

Over 447 bugs, 165 enhancements, 8 feature requests, and 15 blessed tasks have been marked as fixed in WordPress 4.7. Some additional ones to highlight include:

  • Make media library searchable by file name (#22744)
  • Improved Custom Background Properties UI (#22058)
  • Hue-only Color Picker (#38263)
  • Fix Sections that .cannot-expand (#37980)
  • Allow Plugins to do Comprehensive Late Validation of Settings (#37638)

Please, test your code. Fixing issues now, before 4.7 is released, helps you and helps millions of WordPress sites.

#4-7, #dev-notes, #field-guide

Dev Chat Agenda for November 1 (4.7 week 11)

This is the agenda for the weekly dev meeting on November 1, 2016 at 20:00 UTC:

  • Schedule reminder:  The Chat remains at 20:00 UTC.  Day Light Savings Time means that 20:00 UTC may be a different time for you already, or it may be a different time soon.
  • Schedule reminder: Today is the target for Beta 2! That leaves us one week until the final scheduled beta, where the list of tickets should be at zero. It is currently at 74.
  • Ticket reminder: For any tickets you’ve moved into the milestone, please make sure these are active tickets, with some kind of activity in the last 7 days.
  • Call For Bug Scrubs:  Can you run a scrub to help ensure tickets move forward?
  • Dev Notes:  These should all be published this week this week
  • Beta 2:  What needs to be done to get this out the door?
  • 4.6 open ticket scrub

If you have anything to propose to add to the agenda or specific items related to the above, please leave a comment below. See you there!

#4-7, #agenda, #dev-chat

Bug Scrubs for the week of October 3

There are a few upcoming bug scrubs in addition to the regular component ones that you should plan on attending. Both of these scrubs will be taking place in the #core slack room.

There are only 3 weeks remaining until the first beta for 4.7. To hit this target, there must be no remaining enhancements or feature requests. As of today, there are 72 open tickets that must be closed or punted before October 26.

Want to run a bug scrub? Learn about running your own.

#4-7, #bug-scrub

Bug Scrubs This Week

There are a few upcoming bug scrubs in addition to the regular component ones that you should plan on attending. Both of these scrubs will be taking place in the #core slack room.

Additionally, thanks to @desrosj for running a 4.7 focused scrub on Monday.

Want to run a bug scrub? Learn about running your own.

#4-7, #bug-scrub

Dev Chat Agenda for September 21 (4.7 week 5)

This is the agenda for the weekly dev meeting on September 21, 2016 at 20:00 UTC:

If you have anything to propose to add to the agenda or specific items related to the above, please leave a comment below. See you there!

#4-7, #agenda, #dev-chat

Dev Chat Summary: September 14 (4.7 week 4)

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


As of this meeting, we are 5 weeks from the final deadline to merge major features.
There are a lot of tickets in the milestone and owners / people who milestoned them need to make sure they are active and moving, or else punt. You can use this report see tickets in the milestone grouped by who moved it there:

Components and features

Twenty Seventeen (@davidakennedy, @melchoyce)

Make sure to checkout both the Announcement post and the latest update. There is no formal meeting this week. Development has started on GitHub. Like many feature projects, it will live on GitHub until it is ready to come into SVN (within the next 5 weeks).

REST API (@krogsgard, @kadamwhite, @joehoyle, @rmccue)

Core patches, documentation, and reducing the issue backlog have been the primary focuses. There is a settings registry up ( with a corresponding core patch (

Feedback is needed on #37885.  Please take a look.

#38056 is needed for password posts. (update: it has landed).

The next dev chat is Monday September 19 1400 UTC.

Media (@mikeschroder, @joemcgill)

  • Still looking for feedback/testing on #22744, but planning to commit soon.
    • If you have a large media library, your help in testing would be particularly helpful.
  • @paaljoachim continued researching UI flows in other platforms and posted a bunch of screenshots in #core-images.
  • Joe shared an outline of what we’re trying to accomplish longer term here in#core-images and would like to talk more about it design side of things during the #design meeting tomorrow, if possible.
  • Still waiting to hear back from folks who were involved in starting up the Core Media Widget #32417 work, but travel has been an issue. Hopefully we’ll have a better update there next week.

Customize (@westonruter, @celloexpressions)

  • @boone is thinking about/investigating ⁠⁠⁠⁠term_status⁠⁠⁠⁠ for #38015. We have some time to think about it, and could potentially use shadow/draft taxonomies as a workaround for #38014 in 4.7 if needed.
  • tracking the ability to add page stubs or create pages directly from the static front page controls along with this project to facilitate creating pages for initial site setup within the customizer. @westonruter is leading the way on #38013.
  • #34391 is a significant refactoring of code that themes and plugins are encouraged to extend. A corresponding make/core post will follow soon after.
    • Already working with some plugin, theme, and framework authors to minimize breakage.
  • We need some feedback now on #35395 – Custom CSS – @johnregan3 is making great progress.  Please check out the ticket.

i18n (@swissspidy)

  • #29783 (User Admin Language): in good shape, but not much testing happening so far. We could do much more when #26511 is in core though…
  • #26511 (switch_to_locale()): needs some much needed performance testing. If anyone runs a large WordPress site, I could use your help!
    Also since there are some similarities with switch_to_blog(), I’ll open a new ticket to suggest adding a WP_State interface for such switching functions. Think WP_Site_State, WP_Locale_State, WP_Post_State (see #19572), etc. Not a blocker, but worth keeping in mind for future compatibility.
  • #20491 (JS i18n): I documented the current state in the tasks with responsibilities etc. As of tomorrow I’ll have more time to work on it (mainly on the GlotPress side of things). Also have been thinking about a switch_to_locale() function in JS via Ajax…

Editor (@azaozz, @iseulde)

  • Post your wishlist items for the editor.

HTTPS (@johnbillion)

  • Plan of attack for HTTPS work will be published on Make/Core.

Open floor for tickets and any lingering 4.7 ideas.

Please review and comment on these tickets:

#4-7, #dev-chat, #summary

The Upcoming Week in 4.7: 12 September – 18 September

This is the jump-start post for the third week of the WordPress 4.7 release cycle. This release is off to a 🚀 start, and there are 5 weeks remaining for feature projects to be merged. 

Priorities this week:

#17817: do_action/apply_filters/etc. recursion on same filter kills underlying call landed recently.  Please make sure to read the associated post and test.

42 tickets currently milestoned for 4.7 need a patch or unit tests.

A Media Widget is a commonly requested feature; get involved with #32417 if you would like to make it a reality.

Core meetings this week:

All meetings in the WordPress Slack #core channel unless specified otherwise.

Things to do this week:

#4-7, #jump-starts