Media Weekly Update (September 9)

This post summarizes the most recent media meeting, which takes places weekly in #core-images on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..

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 TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress..

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 makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). 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 releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software.. 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 UIUI User interface/UXUX User experience 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/HTTPHTTP HTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands. 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 metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. 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.

CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Media WidgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. (#32417)

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

HTTPSHTTPS HTTPS is an acronym for Hyper Text Transfer Protocol Secure. HTTPS is the secure version of HTTP, the protocol over which data is sent between your browser and the website that you are connected to. The 'S' at the end of HTTPS stands for 'Secure'. It means all communications between your browser and the website are encrypted. This is especially helpful for protecting sensitive data like banking information. 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 ticketticket Created for both bug reports and feature development on the bug tracker. (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