Welcome to the official blog of the core development team for the WordPress open source project.
Here, we make WordPress core. Follow our progress with general updates, status reports, and the occasional code debate.
We’d love for you to help out.
It’s easy to create a ticket on our bug tracker.
Get started quickly. We have some tickets marked as good first bugs for new contributors. There’s more on our reports page, like patches needing testing.
We also have a detailed handbook for contributors, complete with tutorials.
We use Slack for real-time communication. As contributors live all over the world, there are discussions happening at all hours of the day.
We have a project meeting every Wednesday at 21:00 UTC in the #core channel on Slack. (Find out more about Slack.)
You can find meeting agendas on this blog. You’re welcome to join us or listen in.
Hello everyone, let’s have a look at what’s going on in WordPress core! This edition covers February 19th, 2015 [31479] through February 25th, 2015 [31544].
If you want to write the next WordPress Core Weekly summary, check out the table over at make/docs and get in touch in the #core-weekly-update Slack channel.
WP_Customize_Manager::theme() never returns null. [31536] #31445orderby=description support to get_terms(). This appears as a sortable column header. [31532] #31364edit_term_taxonomy and edited_term_taxonomy actions. [31525] #30999version and locale POST vars through the Core Update FTP credentials form. [31527] [31528] #30245 #31378.description-thin fields. [31524] #31426comment-author-is-site-member class to comment output for site members. [31518] #24054focusin and focusout events for row actions to make sure the actions are always revealed on focus. [31509] #29765wp_die() when a user is successfully added to an individual site after using the /newbloguser/ URL from an invite email. This is a user facing success message. [31514] #31224<tfoot> after <tbody>. [31513] #30914is_multisite() before activating a plugin that has been installed via AJAX. Without this check, the plugin would be automatically activated on the main site of the network. [31511] #31327twentyfourteen_post_thumbnail() pluggable. [31481] [31482] #31374Thanks to @afercia, @ AramZS @atimmer, @azaozz, @boonebgorges, @celloexpressions, @cfoellmann, @danielbachhuber, @dd32, @designsimpl, @dipesh.kakadiya, @DrewAPicture, @folletto, @ianmjones, @ipm-frommen, @iseulde, @janhenckens, @jeremyfelt, @jlevandowski, @joedolson, @joostdevalk, @kraftbj, @lancewillett, @mako09, @marcelomazza, @markjaquith,@michael-arestad @MikeHansenMe, @neil_pie, @NikV, @obenland, @ocean90, @PeteMall, @ravindra-pal-singh, @rachelbaker, @rianrietveld, @SergeyBiryukov, @stephdau, @stevegrunwell, @swissspidy @tyxla, @Viper007Bond, @westonruter, and @wonderboymusic for their contributions!
Here’s the agenda for Wednesday’s Emoji Chat in the #core channel on Slack.
Time/Date: Immediately after the Dev Chat.
Here’s the agenda for Wednesday’s Dev Chat in the #core channel on Slack.
Time/Date: February 25 2015 21:00 UTC:
Mobile ticket status.
https://make.wordpress.org/core/2015/02/18/mobile-flow-update/#comment-25331
Multisite office hours are held every Tuesday at 21:00UTC in #core-multisite and are followed by a casual bug scrub / ticket conversation at 22:00 UTC.
We had a great conversation in office hours today around network types as a follow-up to some of the discussion generated by the network types thread from last week.
I think the chat log is the best place to get a full picture of this one as we covered a lot of material and several possible approaches.
In short:
wp_is_trusted_network() to something along the lines of “Introduce better default settings during network creation” (credit @ipstenu).I think that grasps the overall intent of today’s conversation. The entire log is a good read. Please leave feedback here and in the network types thread as you have it! 
Great discussion! Sorry I missed it. But it is encouraging to see the progress being made on multisite!
This is the jump-start post for the sixth week of the WordPress 4.2 release cycle.
The feature plugin merge window is scheduled to close this week on Wednesday, February 25th. Beta 1 starts in 2 1/2 weeks, on Wednesday, March 11th.
Accessibility
Mobile:
Hi Drew. Is there a recap of what we wanted on the Welcome screen so I can make a mockup for tomorrow’s meeting? Thank you!
Left a message in #core-flow.
Re: Enhancements prior to March 10 deadline…”If you have a patch that needs developer feedback, add the dev-feedback keyword to the ticket and leave a comment. I would also encourage you to mention the ticket in the comments of the Monday jump-start”
https://core.trac.wordpress.org/ticket/18132 has dev-feedback keyword and has gotten some prior feedback from @jeremyfelt. It feels commit ready in current state, or small tweaks I’m happy to finish off with feedback from others certainly for 4.2 deadline.
I think we’ll be able to get #18132 in this week, we’re definitely close.
Left some patch feedback.
In a typical release cycle, the beta stages are known as the period where we ramp down and shift focus to testing and fixing bugs only. The testing stages in the 4.2 release cycle will not differ on this point. However, unlike in some previous releases, the shift to working on bugs and testing will be more pronounced in 4.2.
According to the release schedule, Beta 1 is set to begin on March 11th — just about 2 1/2 weeks from now. This means that on March 10th, any enhancement ticket that has one or more commits against it, and/or is owned by a core committer will be converted to a blessed task.
Without exception, all enhancement tickets not converted to tasks on March 10th will be punted to a future release or closed.
So, if you’ve got a pet ticket you’d still like work on for 4.2, now is the time to start if you haven’t already.
If you’re looking for an enhancement to work on, there’s a whole report to choose from!
Developer Feedback
If you have a patch that needs developer feedback, add the dev-feedback keyword to the ticket and leave a comment. I would also encourage you to mention the ticket in the comments of the Monday jump-start or Wednesday dev chat agenda posts on make/core. You could also mention the ticket number during the “Open Floor” time at the end of the weekly core dev chat on Wednesdays.
Accessibility/Mobile/UI Feedback
If your ticket has anything to do with administration or UI, jump into the #accessibility, #core-flow, or #design channels on Slack to get accessibility, mobile, or design feedback.
Not Ready
If you feel like you just aren’t going to have time to work on your enhancement ticket between now and the March 10th deadline, no problem. Just leave a comment to that effect on the ticket and somebody will come along and mark it for Future Release.
Hello everyone, and welcome to this installment of the WP Weekly Roundup! This edition covers February 11th, 2015 [31411] through February 18h, 2015 [31478].
Right at the top of the list: the release of 4.1.1 rolled out Wednesday. You can read the changelog for full details, but here’s the overview.
$tinymce_version in the 4.1 branch. [31477]eol-style = native where missing. [31471]wp_read_image_metadata(), as it’s not a part of the Exif standard. [31462] #31043html4 Plupload handler. [31429] [31430] #31037nodeChanged when an embedded iframe is resized so we can adjust the editor height and other UI components. Props iseulde, [31466] #30646.screen-reader-text to be consistent with current accessibility guidelines. [31464] #31279array_shift() with current() for performance. [31453] #31260WP_Comment_Query. [31467] #31045, #30478, #31265comment-page with the comment pagination base. [31459] #18084add_option() and update_option(). [31473] #31047$expiration as a parameter to the pre_set_transient_{$transient}filter. [31414] #30576WP_Error if an empty name is provided when registering a post type. [31450] #31134paginate_links(), don’t override custom format arguments when setting up default ‘add_args’. [31433] #30831add_args is passed as false to paginate_links(). [31432] #30831add_query_arg(). [31427] #30952WP_Query is_*() methods. [31458] #24674WP_Query‘s sticky post logic. [31439] #27282require_once() to prevent a fatal error if _wp_admin_bar_init() is called twice. [31411] #31287wp_get_archives() when type=postbypost. [31452] #30480WP_Error if an empty name is provided when registering a taxonomy. [31449] #31135term_id with another term, we generate a new row in wp_terms and associate the updated term_taxonomy_id with the new term. This separates the terms, such that updating the name of one term does not change the name of any others. #5809get_admin_url() to get the correct My Sites URL without calling switch_to_blog() directly. [31448] #31314iframe_header(). [31443] #31309_list_meta_row() should always return a string. [31442] #31310.notice admin notices below the first H2, same as the .updated and .error notices. Merges [31023] to the 4.1 branch. [31434] #30885logout_redirect filter so the redirect destination can be changed when a user logs out. [31417] #27617DOMDocumentwhen protecting <pre> tags in WP_oEmbed::_strip_newlines(). It is incredibly difficult to maintain character encoding and whitespace when parsing viaDOMDocument. [31423] #31214str_replace() only occurs once for each matched tag to avoid overwriting until <pre>s. [31416] #31214<pre> tags when parsing oEmbed responses in WP_oEmbed::_strip_newlines() in DOMDocument is available. [31415] #31214The merge period for Feature Plugins has opened. The two candidates, Customizer Theme Switcher and the revamped Press This were both approved and will be “shepherded” in over the next week.
Also discussed were the possible switch in build tools from CSSJanus to RTLCSS (#31332), using the button element for buttons (instead of <a href="#">) and recruiting release leads for 4.3 and 4.4, with a reminder that this isn’t necessarily a developer position.
Yeah, so, the leads are already thinking about who might lead 4.3 and 4.4. The goal was always to announce these ahead of time, and hopefully see overlap with releases, but if nothing else, the release lead for next major +n can be looking at feature plugins, tracking them, pushing them, etc.
With 4.3 starting development in less than 3 months, now would be the time to throw your hat into the ring. I think, ideally, there is an announcement before 4.2 hits beta. This wouldn’t be about doing nothing for the next 3 months, but already getting started in terms of laying the groundwork.
If you are interested in leading a release in 2015, now would be the time to say something. Same if you are interested in helping to lead a release in 2015.
These tickets were specifically mentioned by developers looking for assistance or an extra set of eyes:
Thanks to @adamsilverstein, @afercia, @azaozz, @barrykooij, @boonebgorges, @boonebgorges, @clifgriffin, @cweiske, @danielbachhuber, @dd32, @dlh, @DrewAPicture, @GregLone, @helen, @herbmillerjr, @hugobaeta, @Idealien, @ipm-frommen, @iseulde, @jdgrimes, @jeremyfelt, @johnbillio, @johnbillion, @johnjamesjacoby, @jorbin, @lancewillett, @mattheweppelsheimer, @mboynes, @melchoyce, @mgibbs18, @MikeHansenM, @morganestes, @nacin, @netweb, @norcross, @nunomorgadinho, @obenland, @ocean90, @r-a-y, @SergeyBiryukov, @simonwheatley, @sippis, @stevehickeydesign, @tywayne, @tyxla, @webord, @westonruter, and @wonderboymusic for their contributions!
Here’s the agenda for Wednesday’s Dev Chat in the #core channel on Slack.
Time/Date: February 18 2015 21:00 UTC:
Bring me your tired, your slack, your feedback, bring me your EXIF/IPTC captions to the caption/post_excerpt.
We need some feedback on:
Hide Media Buttons on small screens – https://core.trac.wordpress.org/ticket/29989
As usual, I’d appreciate feedback on #17817.
I’d appreciate some feedback on #27282, also. Seems like a very old bug that I have a good (?) fix for.
Press This is a redesign of an existing feature with a focus on automation, speed, and mobile usability.
Download the plugin and check it out for yourself!
One of the requirements of core is at least feature parity with the old version of Press This. Here’s a comparison chart of where the new Press This is.
| Feature | Old | New |
| Drag & drop install on desktop | Yes | Yes |
| Editor, including: title, image/gallery addition | Yes | Yes |
| TinyMCE buttons (minus kitchen sink) | Yes | Mostly [1] |
| Ability to publish or save as draft | Yes | Yes |
| Post formats | Yes | Yes |
| Categories | Yes | IYes |
| Tags | Yes | Yes |
| Content Scraping | Yes | Improved [2] |
| Media Discovery | Yes | Improved [3] |
| Alert before closing/navigating away | Yes | Yes |
| Can add to bookmarks | Yes | Yes |
| Responsive, clean design, updated icons | No | Yes |
| Fast loading (speedy!) | No | Yes |
| Mobile installation | No | Yes |
[1] A number of TinyMCE buttons are removed intentionally. Only necessary WYSIWYG buttons are shown now.
[2] Not only is it included, but it’s quite a bit smarter than the previous one.
[3] Now is actually quite exposed in the UI.
When we were initially exploring designs and ideas, a few people suggested just improving Post New. The main reason we opted not to was speed. Post New comes with all of wp-admin and its files. It’s a bit of a beast. We wanted an extremely light, extremely fast (both in performance and in usability) way to post and keeping Press This was a good way to go. We can also pull the ideas and techniques we like back into Post New if successful and useful.
We experimented with SVG icons (one less http request, but ultimately removed as Dashicons are required for the editor). We planned to use the upcoming API. We have trimmed down stylesheets and JS (only the styles necessary for a PT view). There is no extra UI that could get in the way of going from 0 to published post. Press This also has the luxury of being able to fall back to the full editor (via Save Draft) for those that have plugins and other features the need to set before posting.
We did a couple rounds of usability tests. One for a11y and another with some new users.
Both had tremendous difficulty in even adding the bookmarklet. @marcelomazza did a pretty solid job fixing up the add bookmarklet screen.
We ran into a number of a11y issues and addressed as many as we could. Could still use another round of a11y testing.
Once the new users figured out how to install it, they didn’t have many issues creating a post. I’d like to do more with ultra Space Jam pro users like yourselves.
@stephdau @azaozz @marcelomazza @ryan @kraftbj @afercia @iseulde @melchoyce @folletto @georgestephanis @helen @drewapicture @danielbachhuber @dd32 (for epic Github > SVN sync)
And thanks to all the testers so far!
This has really turned out excellent. There’s been a ton of progress over the last couple weeks and as an “every once and a while, but hoping to use it more” user of Press This, the new UI is looking great.
“Trimmed down UI for extra-speedy reposting of your favorite left shark gif”
Nice reference. I actually spit coffee in a pop of laughter you awesome jerk.
“Jerk” not meant seriously.
Sorry about your coffee.
Will test and see if it can actually work as a bookmarking service, something like Pocket (or its Open Source version Wallabag), or for content curation, similar to what Scoop.it does.
I’ve actually been testing it as a bookmarking service, but it’s a little tricky the way I was using it. (actual bookmarks).
How about a Chrome extension. “bookmarklet” to me sounds like a quick hack, although it really works, pulling the image and highlighted text.
I would also take it further, to content curation, the hot 2015 trend for SEO.
Congratulations for bringing this feature back to life!
We’re planning on an extension.
Do you guys (mis)use Amphetamines ?
I have never seen so much activity in any CSM community. You really deserve No. 1 place in the world of CMSs.
A suggestion…. if Press This detects a Copyright meta tag, that it doesn’t allow any content from that source to be scraped.
Reply
You must be logged in to post a comment.