Media Weekly Update (September 9)

This post summarizes the most recent media meeting, which takes places weekly in #core-images on Slack.

Our next meeting is Friday, September 16 at 19:00 UTC and the agenda for these meetings include moving priority tasks forward, providing feedback on issues of interest, and reviewing media focused tickets on Trac.

It was brought up that the current meeting time is not great for @swissspidy or @flixos90, and they’d prefer to meet earlier, which we would start next week at Friday, September 23 at 17:00 UTC or alternatively on Thursday, September 22 at 17:00 UTC. Please sound off in the comments as to whether you’d be able to make either of the above to help decide on whether the meeting time will change.

Agenda for the next meeting

This week, we will check in on the priority projects for the 4.7 release. If you have specific tickets that you’d like to have discussed, please leave a comment on this post or reach out on Slack in the #core-images channel.

Recap of the last meeting

Our last meeting was Friday, September 9. You can read the conversation log in #core-images on Slack.

Attendees: @mikeschroder, @markoheijnen, @flixos90, @adamsilverstein, @swissspidy, @paaljoachim, and @achbed.

Media library organization improvements

  • @joemcgill and @swissspidy are working on adding the ability to search the media library by filename (#22744).
  • Following the meeting, @joemcgill posted some great notes on his thoughts regarding process for forming a roadmap for these improvements. You can read them on Slack.
  • Separately, we would like to engage members of the design team in initial conversations about what UI/UX improvements can be made to the media library to make it easier for people to organize and find their media. It’s likely that any UI changes in 4.7 would be relatively light, but we want to begin planning now and focus work during this release on getting as much infrastructure in place as we can.

Improved full size image optimizations (#37840)

Good conversation around ways to solve or work around the issue of increased CPU time/HTTP failures for image resizing.

  • Proposed closing #36534, and creating tickets from the issues found. It was great for gathering information, but has become a dropbox for all HTTP Error related tickets.
  • This is related closely to the full size image task because we want to avoid making the timeout issue worse when adding another resize.
  • In addition to running additional profiling to find what’s now taking the most time, one thing @joemcgill and @mikeschroder discussed in particular is a “try again” or “continue” button as a first jump into making it easier to recover when these failures happen. At the moment, this isn’t a thing because WP only saves meta after creating all sizes is completed successfully, and also because the code doesn’t support creating “the sizes that are left” (related: #15311).
  • @mikeschroder would also like to see investigation into making the HTTP Error more specific, but this could be part of the above project or solved without users needing to know the details, when WP can recover by itself.

Core Media Widget (#32417)

No Update. Reached out to @designsimply and @fab1en.

HTTPS fixes

No Update. Reached out to @johnbillion to see what plans are for 4.7.

PDF Thumbnails (#31050)

No time last week due to travel. @markoheijnen to send update this week.

Accents in attachment filenames should be sanitized (#22363)

@gitlost provided great feedback on the ticket (thanks!), but it looks like it’s going to need additional work before an initial commit.
@mikeschroder looking into this with @markoheijnen at WC Tokyo this week.

#4-7, #media, #weekly-update