Make WordPress Core

Recent Updates Page 2 Toggle Comment Threads | Keyboard Shortcuts

  • Pascal Birchler 1:29 am on April 22, 2016 Permalink |
    Tags: , ,   

    4.5.1 Release Candidate 

    A Release Candidate for WordPress 4.5.1 is now available. This maintenance release fixes 11 issues reported against 4.5 and is scheduled for final release next Tuesday, April 26.

    Thus far WordPress 4.5 has been downloaded nearly 5 million times since its release on April 12. Please help us by testing this release candidate to ensure 4.5.1 fixes the reported issues and doesn’t introduce any new ones.

    Notable Bug Fixes

    As noted in the previous post about 4.5.1, there are  two more severe bugs fixed in this release:

    • #36545 – WordPress TinyMCE toolbar/tabs unresponsive in Chrome Version 50.0.2661.75 beta-m (64-bit) and
    • #36510 – Twenty eleven page templates with widgets incorrectly styled.

    All Changes

    Only a few components received changes. Here’s a list of all closed tickets, sorted by component:

    Build/Test Tools

    • #36498 Shrinkwrap npm dependencies for 4.5

    Bundled Theme

    • #36510 Twenty eleven page templates with widgets incorrectly styled


    • #36457 Customizer Device Preview: Use px units for tablet preview size


    • #36629 Database connect functions can cause un-catchable warnings


    • #36458 Fix support for Safari + VoiceOver when editing inline links


    • #36604 Emoji skin tone support test incorrectly passing in Chrome


    • #36620 Feeds using an rss-http content type are now served as application/octet-stream


    • #36501 Fatal error: Undefined class constant 'ALPHACHANNEL_UNDEFINED'
    • #36578 wp_ajax_send_attachment_to_editor() bug
    • #36621 Don’t cache the results of wp_mkdir_p() in a persistent cache

    Rewrite Rules

    • #36506 Duplicate directives in web.config after WordPress 4.5 installation on Windows


    • #36545 WordPress TinyMCE toolbar/tabs unresponsive in Chrome Version 50.0.2661.75 beta-m (64-bit)

    Update: We’ve released 4.5.1-RC2, which includes the fix for #36629.

    • abhay.sonak 2:05 am on April 22, 2016 Permalink | Log in to Reply

      Is “Headers and client library minor version mismatch” error is fixed in 4.5.1?… As we understand, its not an error, it was a message suppressed in earlier WP version which is rightfully been revoked in WP 4.5… But is there a simple way we can fix this thru dashboard or a plugin?..

      • Gary Pendergast 5:27 am on April 22, 2016 Permalink | Log in to Reply

        Thank you for the report! We’ve seen a few other reports of similar warnings, so I’ve added a fix for it – see #36629 for further information. The fix is in the just-released 4.5.1-RC2 package.

    • programmin 4:52 am on April 22, 2016 Permalink | Log in to Reply

      Nice! but, is it just me or is (4.5.1-alpha-37289) the latest you can update to with the Beta plugin enabled to point release nightlies?

      • Gary Pendergast 5:15 am on April 22, 2016 Permalink | Log in to Reply

        Thanks for the reminder! I just refreshed the nightly build for the 4.5 branch, you should see 4.5.1-RC available now. 🙂

  • Adam Silverstein 10:56 pm on April 20, 2016 Permalink |
    Tags: 4.5.1   

    4.5.1 Release Candidate Tomorrow, April 21st 

    We are planning a 4.5.1 Release Candidate tomorrow, April 21st, then shipping 4.5.1 next Monday or Tuesday. One goal of doing a release candidate is to let the TinyMCE update get wider testing (see below).

    There are two (fixed in trunk) bugs that prompted us to want to release 4.5.1 as soon as possible:

    • #36545 – WordPress TinyMCE toolbar/tabs unresponsive in Chrome Version 50.0.2661.75 beta-m (64-bit) and
    • #36510 – Twenty eleven page templates with widgets incorrectly styled.

    We could use help testing TinyMCE for #36545.  #36545 is a TinyMCE bug with certain versions of Chrome, and is now fixed in TinyMCE upstream. Details on the ticket.

    In #36510 we added a singular class for singular items; so did some existing themes – including Twentyeleven – leading to unexpected results.

    We held a bug scrub yesterday and went thru all the tickets in the 4.5.1 milestone. From that original list #36506 and #36578 still need commits/backporting. Since yesterday, a couple of new tickets have been added to the milestone. If the new tickets can’t be resolved satisfactorily by tomorrow they will likely be punted.

  • voldemortensen 10:08 pm on April 20, 2016 Permalink |
    Tags: , , ,   

    Dev Chat Summary, April 20th 2016 

    Update on WordPress 4.5.1

    • #36510 and #36545 are large bugs that are prompting an earlier release than was anticipated.
    • #36510: a ‘singular’ class was added for singular items, but some existing themes -including Twentyeleven – already used ‘singular’ in a different way leading to unexpected result.
    • #36545: is a potentially bad TinyMCE bug with chrome vs. 50 (now stable) is fixed in TinyMCE upstream; although testers have been unable to reproduce this bug, the point upgrade MCE squashes some known bugs and seems worthwhile to include.

    Other items remaining

    • #26506: Press This: “Add Photos” box doesn’t have enough height
    • #36578: wp_ajax_send_attachment_to_editor() bug

    Discussion about release date

    Several people raised concerns about rushing out an early point release. In an effort to encourage testing before release, 4.5.1-RC will be tagged either today or tomorrow (April 20th, 2016 or April 21st, 2016). A make/core post about changes in 4.5.1 will also be posted.


    • All committers will have their commit access renewed.
    • @voldemortensen will be the release deputy for 4.6.
    • @ebinnion, @rockwell15, and @grantpalin will continue their superb Week in Core posts.
    • WordPress 4.6 will focus on fixing bugs and refining existing features.
    • Other goals include increasing collaboration between features/components, increasing communication via make/core, and give user testing and UX a bigger focus.

    Release Schedule

    Community Wish List

    • @helen gave an update on feature projects (https://make.wordpress.org/core/features/). Feature projects have a bi-weekly meeting (every two weeks) at variable times to allow more contributors to attend. Next meeting is on May 3, 15:00 UTC in the #core Slack channel. More feature projects will be added to the page as their statements of purpose are refined.
    • @ocean90 and @voldemortensen will be tracking the wish list of tickets for 4.6 and providing updates here: https://make.wordpress.org/core/4-6/. (Component maintainers can help up by updating the list as well.)

    Component Maintainers

    General Discussion

    • The Two-Factor feature plugin needs a UX designer. Please reach out to @georgestephanis directly or in #core-passwords on Slack if interested.
    • #34941 (Make the main bootstrap process in ms-settings.php testable) needs some eyes. Please leave comments on the ticket or in #core-multisite if you have questions, comments, or concerns.
    • PHPMailer has decided to drop support for anything lower than PHP 5.5. Security updates will be backported, but there will be no new feature development. Reference.

    Full meeting logs: https://wordpress.slack.com/archives/core/p1461182382001002

  • Dominik Schilling (ocean90) 8:25 pm on April 20, 2016 Permalink |
    Tags: ,   

    WordPress 4.6 Deputy 

    I’m excited to announce my deputy for WordPress 4.6. It’s …

    Garth Mortensen

    … Core Contributor Garth Mortensen (@voldemortensen)! He’s a proud father and husband, former project manager, and now working as a developer.

    You’ll see him around both on the make blogs and Trac helping to manage the release.
    Please join me in congratulating him, and feel free to ping one of us with release questions.

  • Andrew Rockwell 3:23 pm on April 20, 2016 Permalink |
    Tags: ,   

    Week in Core, Apr 12 – Apr 19 2016 

    Welcome back the latest issue of Week in Core, covering changes [37191-37253]. Here are the highlights:

    Ticket numbers based on trac timeline for the period above.

    Code Changes


    • Fix default avatar handling in Settings -> Discussion. [37227] #34744


    • Allow for ABSPATH to be defined outside of wp-load.php, e.g. in a script loaded via auto_prepend_file. [37207] #26592

    Build/Test Tools

    • Add test for multiple site path segments in bootstrap This [37241] #36566
    • Add missing params to doc blocks. Simplifies parameter names in test_get_network_by_path() [37239] #36566
    • Use a data provider to test multisite’s bootstrap. Also helps to get things in order before the introduction of a more testable multisite bootstrap function in #34941. [37238] #34941, #36566
    • Use a data provider in get_site_by_path() tests [37237] #36566, #34941
    • Use a data provider to test get_network_by_path() [37236] #36566, #34941
    • Share test fixtures in multisite bootstrap tests [37234] #36566, #34941
    • Improve get_blog_count() tests [37233] #36566
    • Improvements to /post/query test class. [37224] #
    • Run image tasks only if there are changes [37211] #36528
    • Don’t run the build task twice in grunt prerelease (it already runs via the precommit:js task). [37206] #36489
    • Run network option tests as single and multisite [37222] #36552
    • Update grunt-contrib-uglify from ~0.10.0 to ~1.0.1 [37212] #36520


    • Add parameters to edit_comment_link() to allow specifying a Comment and link class. [37215] #36538
    • Allow for default comment form action, /wp-comments-post.php, to be changed via the comment_form_defaults filter. [37208] #26841



    • Properly notate optional parameters as such in a variety of DocBlocks in wp-includes/link-template.php. [37252] #30406
    • Fix typo in a comment in wp-admin/js/postbox.js. [37195] #36349
    • Fix typo in get_image_send_to_editor() description. [37194] #36349
    • Fix typo in wp_update_theme() description. [37193] #36349
    • Clarify that is_tax() and WP_Query::is_tax() return false for built-in taxonomies (category and tag archives). [37235] #36331
    • Correct description for override_load_textdomain and override_unload_textdomain filters. [37214] #36537
    • Use third-person singular verbs in DocBlock and hook doc summaries in wp-includes/link-template.php. [37213] #30406
    • Fix typo in wp_cache_switch_to_blog() and WP_Object_Cache::switch_to_blog() description. [37216] #36548
    • Reference the correct variable in WP_Ajax_UnitTestCase::_handleAjax() documentation. [37199] #36522
    • Clarify possible types passed to the themes_api_result filter. [37209] #32246



    • Remove tags from translatable string in wp-admin/options-writing.php. [37198] #36249
    • Add translator comment for a string with a placeholder added in [36806]. [37201] #36493

    Login and Registration

    • Add login_header action that fires in the login page header after the body tag is opened and complements login_footer. [37243] #22139
    • Add noindexing to the default wp_die() handler to avoid unnecessary crawl errors in web search engines. [37210] #34401


    • Resolve fatal error on resize with ImageMagick < 6.4.6 Merge of [37192] to the 4.5 branch. Fixes #36501. [37245] #36501
    • Change the close “X” in the Media “Attach to existing content” modal in a button. [37231] #36554
    • Resolve fatal error on resize with ImageMagick < 6.4.6 Fixes #36501. [37192] #36501
    • Make $current_site and $current_blog explicitly global. [37226] #34941
    • Fire a clean_site_cache action when a site’s cache is cleared [37204] #36203
    • Remove theme from network allowed themes when deleted [37203] #34182
    • Introduce WP_Theme methods to network enable/disable themes. [37202] #30594
    • Relocate revoke_super_admin() and grant_super_admin() [37200] #21788
    • Do not set network options to autoload in single site [37223] #22846


    • Show the upload form in place rather than sending users to the devoted upload plugin page. [37221] #35429
    • Properly wrap long tab names to a second line in plugin details modal. [37218] #33221

    Posts, Post Types

    • Pass thumbnail ID to the admin_post_thumbnail_html filter. [37196] #36443
    • In sanitize_post_field(), only run ‘attribute’ or ‘js’ escaping when necessary. [37220] #34900



    • Adding the singular class per default to the list of body classes is breaking the layout of Twenty Eleven and other themes. Merge of [37249] to the 4.5 branch. [37249-37250] #36510
    • After [37217], add other embed templates to file descriptions. [37232] #34561, #34561
    • Account for longer strings in Theme Details bar on Themes screen. [37219] #27939
    • Add embed.php to file descriptions. [37217] #36551
    • Fix single theme modal on collapsed menu. [37205] #36504



    • Use a strict comparison to ensure that a non-numerically-indexed array is not incorrectly matched as a numeric array. [37244] #36586


    Thanks to @afercia, @azaozz, @barry, @bobbingwide, @boonebgorges, @borkweb, @celloexpressions, @Cheffheid, @Chouby, @christophherr, @cliffseal, @dd32, @dimadin, @DrewAPicture, @ericlewis, @flixos90, @Frozzare, @gblsm, @hardeepasrani, @henrywright, @iamfriendly, @igmoweb, @Ipstenu, @iseulde, @jeremyfelt, @joedolson, @johnbillion, @johnjamesjacoby, @jorbin, @meitar, @michaelarestad, @mikeschroder, @netweb, @obenland, @ocean90, @postpostmodern, @rachelbaker, @ramiy, @rodrigosprimo, @SergeyBiryukov, @shahpranaf, @spacedmonkey, @swissspidy, @TacoVerdo, @tfrommen, @theMikeD, @thomaswm, @voldemortensen, and @yoavf for their contributions!

  • Dominik Schilling (ocean90) 8:49 am on April 20, 2016 Permalink |
    Tags: , ,   

    Weekly Dev Chat Agenda for Apr 20 — 4.6 Kickoff 

    Agenda for the weekly dev meeting on April 20 at 20:00 UTC:

    • Update on WordPress 4.5.1
    • Announcements
    • Release Schedule
    • Results of the Community Wish List
    • Component Updates
    • Open Discussion

    If you have anything to propose to add to the agenda, please leave a comment below.

    See you in the chat!

  • Dominik Schilling (ocean90) 8:31 am on April 20, 2016 Permalink |
    Tags: ,   

    I18N Kickoff for 4.6 

    This Thursday, 21 April, 13:00 UTC we’ll have an I18N chat in #core-i18n to discuss the roadmap and ideas for 4.6.

    Some of the bigger tasks on which could be worked during the cycle:

    JavaScript i18n:

    • #20491: Introduce JavaScript i18n functions
    • #22229: Plurals in JavaScript

    User Admin Language:

    • #29783: Main ticket
    • #26511: Separate locale for the admin toolbar
    • #32879: Live switching Language

    Language Packs:

    • #34213: Change priority for loading theme/plugin translations
    • #34114: Remove the requirement to call load_plugin_textdomain() or load_theme_textdomain()

    Database Collation:


    There are currently 77 open tickets in the I18N component which we should try to reduce. It would be nice to get our long planned handbook page about best practices for Internationalization in core (see also Spelling) finalized too.

    Please share in the comments below if there are any specific features and tickets that you want to contribute in this next release. Otherwise, please also join us in #core-i18n chat to discuss.

  • Adam Silverstein 2:12 pm on April 19, 2016 Permalink |
    Tags: ,   

    Bug Scrub for 4.5.1 

    We will be meeting today, Tuesday 19 April , 20:00 UTC (at the usual core dev chat time) in #core to scrub bugs milestoned for 4.5.1.

    Although only a few bugs have been milestoned for 4.5.1, there are two bugs of particular concern that potentially effect many users and will likely result in a point release sooner rather than later:

    • Twenty eleven page templates with widgets incorrectly styled (#36510) which affects sites using Twentyeleven or otherwise already using on the singular body class; the proposed fix is to revert the original change introduced in [36112].
    • WordPress TinyMCE toolbar/tabs unresponsive in Chrome Version 50.0.2661.75 beta-m (64-bit)
      (#36545) which breaks TinyMCE in current beta (and soon stable) versions of Chrome. The fix is an update to TinyMCE  to version 4.3.10; changelog. Testing help in particular needed for this ticket.

    Please join us to help fix these bugs and get some patches committed!

  • Jeremy Felt 6:10 am on April 19, 2016 Permalink |
    Tags: ,   

    Multisite Kickoff for 4.6 

    Let’s have an official multisite kickoff chat this April 21 19:00 UTC in #core-multisite to discuss some of the things we’d like to cover in 4.6.

    A few ideas to ponder…

    • I’d like to reframe our weekly office hours as weekly bug scrubs for this cycle and see how that goes. We can keep tabs on the status of bigger initiatives throughout the week and use the weekly hour to walk through portions of the 217 open multisite tickets in Trac that need walking through.
    • I’d also enjoy moving to a new time for these weekly bug scrubs starting April 26 16:00 UTC. Earlier and easier to schedule for me. How about you?
    • The REST API team is looking for help from component maintainers to build up and maintain parts of the REST API related to those components. If this is something that interests you, let’s chat!

    And the bigger initiatives already in progress:

    • #35791 (previously #31148), in which we introduce WP_Site_Query and use it throughout. 👏
    • #15800, in which we DRY up a bunch of network admin code and enable the extension of the network admin interface.
    • #34941 (and #36566) to further the testability of the multisite bootstrap process, which will in turn lead to fixing things like #17376 with greater confidence.

    And now it’s your turn! Leave ideas in the comments for what we should spend time fixing or breaking in multisite for the 4.6 cycle. 😅


    • websupporter 6:20 am on April 19, 2016 Permalink | Log in to Reply

      Its not completely internal multisite, but maybe we ( I would love to participate in this ) could evaluate a bit the question of the user_status raised in https://core.trac.wordpress.org/ticket/34316 I don’t know, maybe it is a to huge task as it implies database changes which might effect some plugins. And maybe its more a User component, but it is insofar related to multisite as it tangles the `spam` column in the user database, which is only used by multisite and actually this is almost the only real used user_status around. If you think its multisite OT, just let me know 🙂

      I’ll try to make it to the meeting. 19 UTC is a good time for me (its 22:00 in my timezone and my baby sleeps 😀 )

      • Jeremy Felt 3:41 pm on April 21, 2016 Permalink | Log in to Reply

        There are fascinating possibilities with that ticket. We should talk the steps a database upgrade routine would need to take and how we can ensure back-compat for any plugins currently relying on user status.

    • csigncsign 8:43 am on April 19, 2016 Permalink | Log in to Reply

      there are several conflicts due to the fact, that the main blog of a multisite adds an additional “blog” slug to the permalinks.

      • Jeremy Felt 3:35 pm on April 21, 2016 Permalink | Log in to Reply

        This should be easier to work around after we tackled #12002 in 4.4. “blog” is still used as the default, but once you change it, WordPress won’t try to bring it back.

    • Boone Gorges 2:22 pm on April 19, 2016 Permalink | Log in to Reply

      UI for managing registrations: https://core.trac.wordpress.org/ticket/16001 Not strictly Multisite-only, but critical for any Multisite installation with open registration. A large amount of work has been done on patches, but there is some concern about how the confirmation workflow fits alongside adding users to sites. It would be great to sketch what needs to be done for this ticket to move forward – even if it means that some of the odder edge cases (a pending user being added to more than one site) are not handled smoothly in the UI for the time being.

    • zakkates 3:37 pm on April 19, 2016 Permalink | Log in to Reply

      omg, yes! WP_Site_Query

      I’ve been using: Network_Query from http://rudrastyh.com/plugins/get-posts-from-all-blogs-in-multisite-network – Maybe you can get some tips on how they used it.

    • Felix Arntz 4:03 pm on April 19, 2016 Permalink | Log in to Reply

      I’d like to continue work on the Network Settings API (https://core.trac.wordpress.org/ticket/15691) as it will address the needs of many plugin developers who currently use their own kind of hack to handle options in the network admin. Right now I’m basically waiting for some more feedback, maybe we can talk about it in the meeting as well.

  • Helen Hou-Sandi 2:48 am on April 19, 2016 Permalink |
    Tags: feature projects   

    New time for feature projects chat on Tuesday, April 19 

    Time change

    Per the comments on the introduction post, the next feature project chat will be held at April 20 01:00 UTC. This will alternate with the first meeting’s time of 15:00 UTC (1:00PM Eastern). Since there are a number of people in place where only one of the times is at a reasonable hour, as activity picks up we will likely move to weekly meetings that alternate times; for now, we will remain at biweekly (i.e. each time will occur every 4 weeks).

    Meeting Agenda

    • A look at feature project pages.
    • Check-ins with existing feature projects.
    • Call for feature projects and feature project ideas.
    • Open floor.

    To help keep us on track and prevent us from missing things, please comment below with any feature projects/ideas and a brief statement of purpose, as seen on the feature projects page. If you have items for the open floor, also add those in the comments.

    • David Shanske 2:47 am on April 20, 2016 Permalink | Log in to Reply

      At the feature project meeting, I had proposed a feature project to refresh Linkbacks in WordPress. Trackbacks and Pingbacks are the implementations of the concept of a linkback…sending notification that another site has linked to your own.

      However, the current implementation with Pingbacks and Trackbacks leaves much to be desired as a user experience. The default display is limited and the code is in need of a serious look. There is also a newer protocol, webmentions, which was designed as an update/replacement for Pingbacks, that would be worth integrating into WordPress in future.

      I’ve been trying to boil this down to a simple project brief, and am having trouble, so I could use some help. There is an existing Webmentions ticket(#35435) and one for Improving Linkback Presentation(#32653).

      At the same time, the biggest comment people who see no utility(yet) in pingbacks as they exist now is that they are subject to abuse. There is also a ticket to update the code itself(#34419). So concurrent with looking at improving what exits the code, it is an opportunity to see about how Core can better handle abuse and/or support plugins to do same.

      Doing this correctly may span releases, because it needs not only to incorporate above, but needs user testing and feedback.

      Looking for help boiling down the concept into brief and working on it, if it is accepted as a project.

    • Konstantin Obenland 5:00 pm on April 26, 2016 Permalink | Log in to Reply

      For Shiny Updates:

      Shiny Updates replaces The Bleak Screen of Sadness™ with a simpler and more straight forward experience when installing, updating, and deleting plugins and themes. Progress updates for these actions don’t add a benefit, they are disruptive and confusing. Shiny Updates deals with these details behind the scenes, leaving users with clear actions and results.

      This caters to two core principles of WordPress, designing for the majority, and striving for simplicity. Users don’t really care about the internal process of installing or updating themes and plugins. Listing out these technical steps for them is unnecessary at best. With Shiny Updates these actions also don’t require a page reload anymore which creates a simpler workflow and lets users achieve their goals of an enhanced WordPress experience quicker.

      • Helen Hou-Sandi 5:41 pm on April 28, 2016 Permalink | Log in to Reply

        Some thoughts:

        • For the statement of purpose, I think it’s best to stay away from descriptions of what precisely the project does on a technical/functional level.
        • “disruptive and confusing” is not very informative and doesn’t give us specific things to measure/compare against. What sorts of things are being disrupted? What is confusing about them specifically? The statement may not need that level of specificity but I think we could shape it better around that.
    • MikeNGarrett 9:49 pm on April 27, 2016 Permalink | Log in to Reply

      The developers at The Web Development Group have worked on a plugin called Jarvis for a while now, improving upon the idea of a quick search interface for finding and navigating to content and settings admin pages.

      Recently, we have started discussing what it would take to integrate a feature like this into core and whether or not it would be useful to the greater community beyond existing as a plugin. It is our opinion that a feature like this would augment the functionality of the admin and provide a better user experience for power users of the WordPress admin.

      Our testing with clients has revealed a high rate of use from content editors and developers, allowing these users to find and access the edit pages for content quickly just as the admin bar has aided this user experience on the frontend of WordPress sites.


compose new post
next post/next comment
previous post/previous comment
show/hide comments
go to top
go to login
show/hide help
shift + esc
Skip to toolbar