4.6.1 Release Candidate

A Release Candidate for WordPress 4.6.1 is now available. This maintenance release fixes 16 issues reported against 4.6 and is scheduled for final release on Wednesday, September 7.

Thus far WordPress 4.6 has been downloaded almost 7 million times since its release on August 16. Please help us by testing this release candidate to ensure 4.6.1 fixes the reported issues and doesn’t introduce any new ones.

All Changes

Here’s a list of all closed tickets, sorted by component:


  • #37680 – PHP Warning: ini_get_all() has been disabled for security reasons


  • #37696WP_Comment_Query loses sql_clauses with object cache


  • #37683$collate and $charset can be undefined in wpdb::init_charset()
  • #37689 – Issues with utf8mb4 collation and the 4.6 update


  • #37690 – Backspace causes jumping


  • #37736 – Emails fail on certain server setups

External Libraries

  • #37700 – Warning: curl_exec() has been disabled for security reasons (Requests library)
  • #37720 – The minified version of the Masonry shim was not updated in #37666 (Masonry library)


  • #37733cURL error 3: malformed for remote requests
  • #37768 – HTTP API no longer accepts integer and float values for the cookies argument

Post Thumbnails

  • #37697 – Strange behavior with thumbnails on preview in 4.6

Script Loader

  • #37800 – Close “link rel” dns-prefetch tag


  • #37721 – Improve error handling of is_object_in_term in taxonomy.php


  • #37755 – Visual Editor: Weird unicode (Vietnamese) characters display on WordPress 4.6



  • #37731 – Infinite loop in _wp_json_sanity_check() during plugin install



Dev Chat Summary: August 24, 2016

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

4.6.1 Schedule

4.7 Personnel and Schedule

  • @jorbin (engineering/development focus) & @jbpaul17 (PM focus) will be release deputies for 4.7
  • Full release schedule can be found at https://make.wordpress.org/core/version-4-6-project-schedule/
  • The scheduled release date is December 6.
  • Due to WCUS & US Thanksgiving holiday, we will have to treat RC as a true Release Candidate
  • There is no “merge window”, testing & feedback should be continuous before merge consideration

Potential Focus Areas

  • Many wishlist comments are specific developer-facing features as well as better media findability/organization, easier plugin management, and the initial theme setup experience
  • New default theme (aka Twenty Seventeen) likely, but to be confirmed within the next week or two
  • REST API content endpoints (posts, terms, comment, users, and their associated meta) to get defined roadmap for 4.7 delivery plus future roadmap to full management and admin API coverage (potential approach)
    • the next meeting will be August 29 at 23:00 UTC, where this will be further discussed
    • @krogsgard aiming to write spec for each item in the list by next meeting, open to acting as PM for this focus area
    • looking for a few committers with knowledge around the API to guide the process with a permanent or lead as their buddy
    • looking for review from outside WP community
    • will require documentation coverage for builders and consumers
    • Core endpoints will need to be reviewed by their respective component maintainers

Open Forum on Focus Areas

  • “find your media more effectively” (#22744)
  • taxonomy (aka media tagging) UX+UI work for assignment and filtering mechanisms
  • “find an accessible multi-select/autocomplete/tagging helper”
  • “smarter defaults”
  • Eliminating usability dead-ends in the customizer (#34923, #35395, #37661)
  • further refinements to the updates flow continuing from 4.6
  • low-fi mockup and testing of metabox for different publishing possibilities (including existing examples)
  • resolve some ancient annoying issues (e.g., #17817)
  • Content Authorship in Menus, with Live Preview
  • dashicons as svg sprite (Make/Core Post)
  • document dynamic hook aliases in core (finally) + adding DevHub support
  • initial theme setup experience

Teams and Weekly Updates

  • Teams are the contributor groups that form around components and major work items (e.g. features and big API changes)
  • Will continue to identify those Teams and a “spokesperson” for each
  • Teams should have a weekly scheduled meeting and a weekly update posted to Make/Core
  • @helen to continue the tradition of weekly jump start posts, so there will be a reminder of Team meetings each week

Wishlist Items

Bug Scrubs

  • Everyone is empowered to run a bug scrub (can be component based, or based on any other ticket report)
  • A post with information on how to run a bug scrub and who is empowered to do it (hint: it’s you) will be published on make/core soon
  • Bug Scrubs are a great experience in running a meeting, writing good responses, and building confidence in making those do-or-punt decisions
  • You do not need to be a dev to run a bug scrub, @hugobaeta and the design team has done some great scrubs
  • You don’t need to be a committer to run them, @chriscct7 has done some incredible scrubs on ancient tickets
  • “If 5 new people that have never run a bug scrub or other core meeting before, run one this release: I will write and record a parody of “No Scrubs” by TLC, but about Bug Scrubs.” — @jorbin Π

#4-6-1, #4-7, #core, #dev-chat, #summary

Bug Scrub for 4.6.1

The first bug scrub for 4.6.1 will be Tuesday 23 August, 15:00 UTC in #core.

There are currently 9 11 tickets open on the 4.6.1 milestone in various stages of verification, patching, and testing. Working with these over the next several days before the bug scrub will help determine when a 4.6.1 release will be necessary.

Any tickets reported against trunk at this point in the cycle should also be checked for issues that may have been introduced in 4.6.

All testing is helpful, so please take a look if you have time.

See you on Tuesday!


#4-6-1, #bug-scrub