20 open tickets. Last 7 days: -1 ticket
|20 open tickets||defect (bug)||enhancement||feature request|
Howdy! This is Last Week in WordPress Core for the week of February 24—March 2! Lots of activity for the past week, which is great as we head into our last few days of alpha. Please join us for daily triage at 1900 UTC to help work through the remaining enhancements scheduled for 3.9.
As a quick note, if you work with our tools in ‘develop’, and are receiving a
SELF_SIGNED_CERT_IN_CHAIN error, you can resolve it by running
npm config set ca="". For details, check out this npm blog post.
If you want to skim, each section is roughly ordered by an important and/or interesting factor.
add_theme_support( 'html5', 'gallery' ),
figcaptionwill be used instead of definition list markup.  #26697
comment-reply.jsto the footer. While it can function before the page is loaded, it works by moving the comment form, which is usually toward the bottom of the page. Please report any contraindications on the ticket.  #12641
get_adjacent_post()wrap a new
WP_Adjacent_Postobject that uses
WP_Query.   #26937
wp_list_authors().  #9902
get_site_by_path()and further rewrite the site detection process for multisite. This makes it so that a sunrise plugin could do much of its work by adding filters, if those are even needed.  #27003
doing_action()to identify hooks in progress. You can also use this with to identify a hook that has completed. For more, see  #14994.
trailingslashit()will now remove any forward or backslashes from the end of a string before appending a forward slash.  #22267
current_time()to accept a date format string, adding to
mysql.  #21653
microtime()returns greater precision than
microtime(true).  #27000, #23448, #26903, #14485
WP_Query::get(). Helpful when working with endpoints.  #16471
user_idto be an array of IDs in
WP_Comment_Query.  #27064
get_dashboard_url()optional, defaulting to the current user.   #16686
masonry. The old
jquery-masonryhandle is the official shiv that sits on top of the v3 library to be backwards compatible with v2 usage. While v3 no longer depends on jQuery, a theme or plugin may have been implicitly loading jQuery though Masonry, rather than additionally declaring it as a dependency for themselves.
masonryand declare jQuery as a dependency on their own if they need it.
WP_HTTPfrom the latest Mozilla release NSS.  #27017
grunt-patch-wordpressfor applying patches directly from Trac. Mapped to
grunt patch, which declares usage. Requires
npm installto install.  #27023
Thanks to @adamsilverstein, @andy, @avryl, @bassgang, @bootsz, @chrisscott, @danielbachhuber, @DrewAPicture, @enej, @ericlewis, @ericmann, @ethitter, @evarlese, @garyc40, @GaryJ, @gcorne, @georgestephanis, @GregLone, @helen, @iamfriendly, @Ipstenu, @jackreichert, @jeremyfelt, @johnjamesjacoby, @jorbin, @knutsp, @kovshenin, @kpdesign, @leewillis77, @markjaquith, @mattheu, @mboynes, @mitchoyoshitaka, @mjbanks, @mordauk, @morganestes, @nacin, @nicolealleyinteractivecom, @obenland, @ocean90, @patricknami, @pento, @pross, @rickalee, @salcode, @scribu, @SergeyBiryukov, @shelob9, @siobhyb, @solarissmoke, @xsonic, @stephcook22, @theorboman, @tivnet, @TobiasBg, @willmot, @wonderboymusic, @xknown, and @yoavf for their help this week!
Here’s a quick summary of yesterday’s meeting (IRC log), as a status report on WordPress 3.9:
Beta 1 will now be the week of March 3, a week later. The rest of the schedule is unchanged. I felt the extra week of alpha would be helpful given all of forward momentum right now, and others seemed to agree.
It was decided to green-light the widget customizer plugin for merge. If all goes well, it’ll be in 3.9 final. There’s still a lot to do: some UI polishing, deeper code review, etc. — and surely it will get a lot of testing.
Quick hits raised in the meeting:
We have a few more weeks of alpha, so it’s a great time to help with writing or testing a patch for WordPress 3.9. We’ll be keeping the tempo quick. Expect lots of changes.
Welcome back to Last Week In WordPress Core, for the week of January 27-February 2. Big list this time! First, a summary of the major changes; then a roundup from the various 3.9 teams:
Enhancements and hooks
resetpass_form, in wp-login.php #21044
wp_upgradehooks to the respective functions. #25762
TRADITIONAL. Introduces filterable
incompatible_sql_modesfilter for plugins. #26847
wpdb::db_connect(), allow the loading of a translatable custom database error template. #25703
Miscellaneous, including library updates
$forceargument removed from
WP_Object_Cache::delete(), which was internal-only. #22478
npm installto receive updates for
node_modulesin the project root. #26073
Here are roughly where each of the 3.9 teams/tasks stood as of last week’s meeting:
Other UI work:
Fun with internals:
Housekeeping items last week included a call for GSoC participation from @jenmylo, and trac component reorganization proposal from @nacin. The reorganization was approved during the chat on Wednesday and is well under way. Additionally, there’s now a new Trac reports overlay and Trac’s navigation got overhauled.
For the complete changelog commits to trunk, check out the log on Trac.
More than three dozen contributors had a hand in last week’s efforts. Want to help out this week? Write or test a patch for 3.9.
Thanks for contributions this week from atimmer, aubreypwd, azaozz, c3mdigital, cmmarslender, coffee2code, Denis-de-Bernardy, DrewAPicture, empireoflight, gcorne, helen, ippetkov, jeremyfelt, joehoyle, johnjamesjacoby, JoshuaAbenazer, kovshenin, kpdesign, kraftbj, mark8barnes, markjaquith, MattyRob, mdbitz, melchoyce, nacin, neoxx, nofearinc, ocean90, olivM, oso96_2000, ounziw, pento, romaimperator, sbruner, SergeyBiryukov, soulseekah, TobiasBg, toszcze, wonderboymusic, and yoavf!
WordPress uses open source software called Trac to manage bug reports and tasks. If you are looking to report a bug, please head on over.
There are many ways to contribute. We have a detailed contributor handbook to help get you started. If you want to get started quickly, try one of the Getting Started reports blow — test a patch, or grab a bug and see if you can reproduce the problem it describes.
If you have encountered a security issue in WordPress, please contact security at wordpress.org. For more, see our Security FAQ.
Warning, this long. tl;dr: I propose a reorganization of our Trac components. 34 top-level components with two dozen subcomponents. New tree at the bottom. First, an overview of some of our problems.
We were supposed to discuss WordPress 3.9 during the weekly meeting last week, but in the absence of a decision on a release lead, and with a lot of 3.8.1 things to get through, it got pushed to today. 2100 UTC, #wordpress-dev (so, in an hour).
I’ll be the release lead for WordPress 3.9. Expect some familiar faces helping me out, including Andrew Ozz, who will be overseeing all of the TinyMCE work already underway this cycle; Helen Hou-Sandí, who will be spending most of her time working on and advising ongoing feature plugins efforts; Sam Sidler, who will be helping with project management; and Mike Schroder, who will be backing me up for this release.
Today we’ll be:
Hope to see you today. Have any idea, thought, or suggestion about 3.9 or for today’s meeting in particular? Please leave a comment so I can prepare for it. Talk soon.
I wanted to do a Make post on my wants for Audio / Video in 3.9 to solicit feedback and spark some discussion about what the community wants / needs / doesn’t want / doesn’t need. Adding audio / video in 3.6 was a great first step, but there are some things we can do to continue to modernize Media and give our huge user base even more ways to display and manage their content. We can also make some changes that help developers navigate the new world of MediaElement.js, Backbone, and Underscore.
#26650 Replace media file type icons with Dashicons
There are some lingering icons in the admin that don’t look as pretty as their MP6ify’d brethren
In 3.5, we overhauled Media. @Koop produced some beautiful code, and a LOT of it. Raise your hand if you’ve ever dived in and tried to program against it? Raise you hand if you understand how all of it works? Me neither. As a community, we need to help each other learn what it is and what it does. Documentation will go a long way in getting us all on the same page. Do we have a documentation standard for JS? We need one. While this isn’t the easiest place to start, it is a necessary one. I would be happy to spend time on this, as I have spent many hours recently reading the code and learning how it works. The main files: media-editor.js, media-views.js, media-models.js
#26628 Use the content of a video shortcode when provided.
This ticket speaks for itself, and already has a patch.
#26825 Add ability to generate metadata for audio / video files on-demand
#26631 Add a “playlist” shortcode
My ticket already contains a patch, but is still considered a work in progress. I think the playlist shortcode should produce markup that does the following:
My current implementation drops data onto the page for each playlist inline. A wrapper div “.wp-playlist” will have a script tag in it with type=”application/json”. I do this so that if ‘wp-playlist.js’ is unenqueue’d, the developer still has the data necessary to write their own implementation. The data is reachable in JS like so:
var data = $.parseJSON( el.find('script').html() );
My current UI for playlist is a basic one, and uses Backbone Views to render the tracklist on load and update the “current” playing track view. There are 2 camps of people when it comes to “JS on the frontend” – one who doesn’t like it (others) and one who says “who cares” (me). One of the reasons I am posting this at the beginning is so we can flesh out issues like this.
I have already done a first pass at this in the playlist shortcode patch. It goes like this: a “gallery” is really a “collection” of attachments of type “image.” A “playlist” is really a “collection” of attachments of type “audio.” So they should extend or be instances of a “collection”-type class. Currently, the Gallery code has to be dupe’d. By abstracting this code, Gallery, Playlist, Video Playlist, + any other “collection” of media type can be registered minimally.
The Widgets team has been busy. Outside of the Widget Customizer plugin (posted about previously), we’re also working on some updates to the main wp-admin widgets screen through the Better Widgets plugin. This plugin does a bunch of things:
The plugin is still very young, but we’re looking to the community to get some interested from designers, developers, and testers. Please, install the plugin and play around. If you’d like to help us improve widgets, please join us every Monday at 20:00 UTC in #wordpress-ui — you can also drop your Skype nick below and we’ll add you to our ongoing chat.
Some things to keep in mind when testing the Better Widgets plugin:
Three of the features in the upcoming WordPress 3.8 release were developed first as feature plugins:
Feature plugins are regular plugins whose ultimate aim is to be put forward as new features for future versions of WordPress. This model allows for efficient, collaborative development over longer periods of time, and a certain amount of visibility among people who help develop for core. The status of existing feature plugins can be seen here.
This post is a call for people who are planning on working on feature plugins in the near future to make themselves known in the comments. People who would like to pro-actively help out should then comment on individual comment threads.
If you are a developer, designer, or curator who’d like to act as a project lead for (or at least take a primary role in) the development of a feature plugin, please leave a top-level comment on this thread with the following information:
Please note that this thread is not for putting forward ideas for things unless you are planning on taking an active and primary role in its development. This is an organisation thread, not an ideas thread.
Anyone who’d like to collaborate on any of the plugins listed in the comments should leave a reply to the corresponding comment indicating your interest and what you can help out with.
Bear in mind this is not a list of potential features for WordPress 3.9, or indeed any other particular future release. Feature plugins are not tied to any specific release and will only be considered for potential inclusion in core once they reach a certain level of completeness.
We’ll see how this list pans out over the next few days and go from there! It’s expected that we’ll organise some IRC meetings in due course.