Title: Audio / Video 2.0 &#8211; codename &#8220;Disco Fries&#8221;
Author: Scott Taylor
Published: January 13, 2014

---

 [  ](https://profiles.wordpress.org/wonderboymusic/) [Scott Taylor](https://profiles.wordpress.org/wonderboymusic/)
6:47 pm _on_ January 13, 2014     
Tags: [Audio ( 3 )](https://make.wordpress.org/core/tag/audio/),
[Backbone ( 2 )](https://make.wordpress.org/core/tag/backbone/), [jQuery ( 15 )](https://make.wordpress.org/core/tag/jquery/),
[media ( 93 )](https://make.wordpress.org/core/tag/media/), [MediaElement ( 5 )](https://make.wordpress.org/core/tag/mediaelement/),
Underscore, [video ( 6 )](https://make.wordpress.org/core/tag/video/)   

# Audio / Video 2.0 – codename “Disco Fries”

Some history:

 * [Audio / Video support in Core](https://make.wordpress.org/core/2013/04/08/audio-video-support-in-core/)
 * [WordPress 3.6 + Audio/Video](http://scotty-t.com/2013/08/01/wordpress-3-6-audiovideo/)

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.

#### First Things First: New Icons

[#26650 Replace media file type icons with Dashicons](https://core.trac.wordpress.org/ticket/26650)

There are some lingering icons in the adminadmin (and super admin) that don’t look
as pretty as their MP6ify’d brethren

#### Document the “new” Media code introduced in 3.5

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 
JSJS JavaScript, a web scripting language typically executed in the browser. Often
used for advanced user interfaces and behaviors.? 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](https://core.trac.wordpress.org/browser/trunk/src/wp-includes/js/media-editor.js),
[media-views.js](https://core.trac.wordpress.org/browser/trunk/src/wp-includes/js/media-views.js),
[media-models.js](https://core.trac.wordpress.org/browser/trunk/src/wp-includes/js/media-models.js)

#### Support subtitles for Video

[#26628 Use the content of a video shortcode when provided.](https://core.trac.wordpress.org/ticket/26628)

This ticketticket Created for both bug reports and feature development on the bug
tracker. speaks for itself, and already has a patchpatch A special text file that
describes changes to code, by identifying the files and lines which are added, removed,
and altered. It may also be referred to as a **diff**. A patch can be _applied_ 
to a codebase for testing..

#### Generate audio/video metadata on-demand

[#26825](https://core.trac.wordpress.org/ticket/26825) Add ability to generate metadata
for audio / video files on-demand

#### Add “Playlist” and “Video Playlist” shortcodes

[#26631 Add a “playlist” shortcode](https://core.trac.wordpress.org/ticket/26631)

Adding inline players for audio and video was a great first step. How do I add music
to my site? Just upload an MP3 and drop the URLURL A specific web address of a website
or web page on the Internet, such as a website’s URL www.wordpress.org on a line
by itself. Done. Or use the audio shortcodeShortcode A shortcode is a placeholder
used within a WordPress post, page, or widget to insert a form or function generated
by a plugin in a specific location on your site.. This works most of the time, but
can be a little clunky if you want to share an album of your tunes. MediaElement
doesn’t “support” playlists out of the box, but MediaElement is JavaScriptJavaScript
JavaScript or JS is an object-oriented computer programming language commonly used
to create interactive effects within web browsers. WordPress makes extensive use
of JS for a better user experience. While PHP is executed on the server, JS executes
within a user’s browser. [https://www.javascript.com](https://www.javascript.com/),
and with JavaScript and little UIUI User interface elbow grease, we can EASILY support
playlists.

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:

 * Works out of the box with any existing theme: the HTMLHTML HyperText Markup Language.
   The semantic scripting language primarily used for outputting content in web 
   browsers. should be semi-bulletproof. Many of the Player libraries make heavy
   use of DIVs instead of items that might be overridden easily with CSSCSS Cascading
   Style Sheets.: LIs and the like.
 * Gives the developer total control if they want to write their own implementation
 * Exposes enough data to the page so the themer/dev can make their own decision
   regarding display of album cover, track 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., captions, etc.

My current implementation drops data onto the page for each playlist inline. A wrapper
div “.wp-playlist” will have a script tagtag A directory in Subversion. WordPress
uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common
convention of tags in version control systems. (Not to be confused with post tags.)
in it with type=”application/jsonJSON JSON, or JavaScript Object Notation, is a 
minimal, readable format for structuring data. It is used primarily to transmit 
data between a server and web application, as an alternative to XML.”. 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.

#### Abstract Gallery logic into “Collection” logic that Galleries, Playlists, etc can use with minimal registration code

I have already done a first pass at this in the [playlist shortcode patch](https://core.trac.wordpress.org/attachment/ticket/26631/26631.4.diff).
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.

#### Other Ideas

 * In our playlist JS code, emit events that others can hook into – maybe a video
   playlist is: News clip, ad, news clip, ad, etc. When emitting events before /
   after an ad, the dev could disable next/prev buttons
 * Make a playlist embeddable on other sites via an iframeiframe iFrame is an acronym
   for an inline frame. An iFrame is used inside a webpage to load another HTML 
   document and render it. This HTML document may also contain JavaScript and/or
   CSS which is loaded at the time when iframe tag is parsed by the user’s browser.
   or embedded markup
 * Register an endpoint for audio / video that will expose the “embed code” via 
   oEmbed

#### Thoughts?

[#audio](https://make.wordpress.org/core/tag/audio/), [#backbone](https://make.wordpress.org/core/tag/backbone/),
[#jquery](https://make.wordpress.org/core/tag/jquery/), [#media](https://make.wordpress.org/core/tag/media/),
[#mediaelement](https://make.wordpress.org/core/tag/mediaelement/), [#underscore](https://make.wordpress.org/core/tag/underscore/),
[#video](https://make.wordpress.org/core/tag/video/)

### Share this:

 * [  Threads ](https://make.wordpress.org/core/2014/01/13/audio-video-2-0-codename-disco-fries/?share=threads)
 * [  Mastodon ](https://make.wordpress.org/core/2014/01/13/audio-video-2-0-codename-disco-fries/?share=mastodon)
 * [  Bluesky ](https://make.wordpress.org/core/2014/01/13/audio-video-2-0-codename-disco-fries/?share=bluesky)
 * [  X ](https://make.wordpress.org/core/2014/01/13/audio-video-2-0-codename-disco-fries/?share=x)
 * [  Facebook ](https://make.wordpress.org/core/2014/01/13/audio-video-2-0-codename-disco-fries/?share=facebook)
 * [  LinkedIn ](https://make.wordpress.org/core/2014/01/13/audio-video-2-0-codename-disco-fries/?share=linkedin)

 1.  ![](https://secure.gravatar.com/avatar/4fd344e387cd0febbb417ee2a2bef7db6b40c8f7ecf4265fb41dcef8e9fa8c4b?
     s=32&d=mm&r=g)
 2.   [Joe Dolson](https://profiles.wordpress.org/joedolson/)  7:00 pm _on_ January
     13, 2014
 3.  Definite thumbs up from the AccessibilityAccessibility Accessibility (commonly
     shortened to a11y) refers to the design of products, devices, services, or environments
     for people with disabilities. The concept of accessible design ensures both “direct
     access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s
     assistive technology (for example, computer screen readers). (https://en.wikipedia.
     org/wiki/Accessibility) team for adding captions support. In addition to that,
     I’d like to suggest making it possible to enable keyboard accessibility more easily
     than it is right now. MediaElement.js includes settings which enable this — one
     is enabled by default, which enables keyboard access to the controls, but without‘
     alwaysShowControls’ enabled, it’s not possible for a keyboard dependent user to
     move focus onto the player, so they can’t take advantage of any of those controls.
 4.  I’d like to see a localization variable so that the MediaElement settings can 
     be adjusted via wp_localize_script, but for keyboard accessibility it may be valuable
     to make this an option, either via shortcodeShortcode A shortcode is a placeholder
     used within a WordPress post, page, or widget to insert a form or function generated
     by a plugin in a specific location on your site. or settings, so it’s possible
     for non-programmers to enable keyboard accessibility.
 5.  I’ve got a plug-in, [Accessible Video Library](https://wordpress.org/plugins/accessible-video-library/)
     that hacks in support for alwaysShowControls by deregistering the default wp-mediaelement
     script, but that’s not an ideal solution.
 6.  It would also be nice if the caption selector within MediaElementjs could be made
     keyboard accessible; though that’s probably something that should be handled as
     a patchpatch A special text file that describes changes to code, by identifying
     the files and lines which are added, removed, and altered. It may also be referred
     to as a **diff**. A patch can be _applied_ to a codebase for testing. to MediaElementjs
     itself.
 7.  The Add Media Panel, in addition to new documentation, is in desperate need of
     accessibility work. See [#23560](https://core.trac.wordpress.org/ticket/23560).
     And several other tickets; there are quite a few accessibility tickets on the 
     Add Media Panel.
 8.  ![](https://secure.gravatar.com/avatar/323cf209e19dd825678e9ccc51bc3f745f96571f1c68af26ae7955c1fa9ad1f2?
     s=32&d=mm&r=g)
 9.   [Aaron Jorbin](https://profiles.wordpress.org/jorbin/)  7:03 pm _on_ January 
     13, 2014
 10. RE: JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming
     language commonly used to create interactive effects within web browsers. WordPress
     makes extensive use of JS for a better user experience. While PHP is executed 
     on the server, JS executes within a user’s browser.
      [https://www.javascript.com](https://www.javascript.com/)
     Docs.
 11. the JSDoc standard is pretty close to the phpdocPHPDoc (**docblock**, **inline
     docs**) standard that we use for PHPPHP The web scripting language in which WordPress
     is primarily architected. WordPress requires PHP 7.4 or higher and thus it makes
     the most sense in my eyes. There was a passing IRCIRC Internet Relay Chat, a network
     where users can have conversations online. IRC channels are used widely by open
     source projects, and by WordPress. The primary WordPress channels are **[#wordpress](https://make.wordpress.org/core/tag/wordpress/)**
     and **[#wordpress-dev](https://make.wordpress.org/core/tag/wordpress-dev/)**, 
     on irc.freenode.net. conversation between members of the team that did the jshint
     work and the inline documentation that a future project could focus on improving
     the documentation of our JSJS JavaScript, a web scripting language typically executed
     in the browser. Often used for advanced user interfaces and behaviors.. The media
     files seem like a great place to prototype this.
 12. [http://usejsdoc.org/](http://usejsdoc.org/) is the standard.
 13.  * ![](https://secure.gravatar.com/avatar/92c9b71af01db9777d29870c622c80ef94d1344158eb2f5965f4bbe8efed251a?
        s=32&d=mm&r=g)
      *  [Eric Andrew Lewis](https://profiles.wordpress.org/ericlewis/)  8:02 pm _on_
        January 13, 2014
      * Yes to inline docsinline docs (phpdoc, docblock, xref). However, I think we’re
        going to need an alternate form of documentation completely separate from inline
        to give an easily understandable overview of how media works.
         - ![](https://secure.gravatar.com/avatar/479f05d4acc73915a43b24a1ee3f30477d4ee19bbec6a5a79906d396f2b2d2ad?
           s=32&d=mm&r=g)
         -  [Sam Sidler](https://profiles.wordpress.org/samuelsidler/)  8:37 pm _on_
           January 13, 2014
         - What did you have in mind?
         - The inline docsinline docs (phpdoc, docblock, xref) will soon (ish) be present
           on developer.wordpress.orgWordPress.org The community site where WordPress
           code is created and shared by the users. This is where you can download 
           the source code for WordPress core, plugins and themes as well as the central
           location for community conversations and organization. [https://wordpress.org/](https://wordpress.org/),
           which will help the visibility of them. Do you mean something more like 
           a walkthrough on exactly how it works? I’m trying to think of where the 
           best place for that would be. Definitely on the developer hub, but probably
           not part of the theme/pluginPlugin A plugin is a piece of software containing
           a group of functions that can be added to a WordPress website. They can 
           extend functionality or add new features to your WordPress websites. WordPress
           plugins are written in the PHP programming language and integrate seamlessly
           with WordPress. These can be free in the WordPress.org Plugin Directory 
           [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can 
           be cost-based plugin from a third-party. handbooks.
            * ![](https://secure.gravatar.com/avatar/92c9b71af01db9777d29870c622c80ef94d1344158eb2f5965f4bbe8efed251a?
              s=32&d=mm&r=g)
            *  [Eric Andrew Lewis](https://profiles.wordpress.org/ericlewis/)  10:24
              pm _on_ January 13, 2014
            * Not sure to be honest. I think there are limits to inline documentation.
              Inline is always so contextual to the code it surrounds; separate documentation
              can speak of overarching design principles and secondary information 
              that doesn’t pertain to any code blockBlock Block is the abstract term
              used to describe units of markup that, composed together, form the content
              or layout of a webpage using the WordPress editor. The idea combines 
              concepts of what in the past may have achieved with shortcodes, custom
              HTML, and embed discovery into a single consistent API and user experience.
              in particular.
            * [WP-API’s documentation](https://github.com/WP-API/WP-API/tree/master/docs)
              for example is quite verbose, and covers a range of topics including 
              the APIAPI An API or Application Programming Interface is a software 
              intermediary that allows programs to interact with each other and share
              data in limited, clearly defined ways.’s philosophy, tutorials, schema
              details, etc. None of this could fit easily into inline documentation.
            * Full disclosure: I’ve only used the media library cursorily, and am not
              even sure what secondary documentation for it might look like, so I may
              be off-base here.
               - ![](https://secure.gravatar.com/avatar/c21ff90e030a07e3a20f48a0496530828cf86ef69a464d326351423eb2570ef0?
                 s=32&d=mm&r=g)
               -  [Ryan McCue](https://profiles.wordpress.org/rmccue/)  1:11 pm _on_
                 January 16, 2014
               - This is one of the benefits of the new developer site being WP-based:
                 we can mix in inline docsinline docs (phpdoc, docblock, xref) with
                 full pages. (It’s also one of the reasons WP-Parser is architectured
                 that way.)
            * ![](https://secure.gravatar.com/avatar/c47c86a6e780f2309c491d27ecd3feea89446df2c1d584ce329832d7c8158991?
              s=32&d=mm&r=g)
            *  [Gregory Cornelius](https://profiles.wordpress.org/gcorne/)  6:01 pm
              _on_ January 15, 2014
            * Documenting the parts of the WordPress Backbone code that form more of
              a “public” APIAPI An API or Application Programming Interface is a software
              intermediary that allows programs to interact with each other and share
              data in limited, clearly defined ways. that is intended to be re-used
              in plugins with a few examples makes sense.
         - ![](https://secure.gravatar.com/avatar/323cf209e19dd825678e9ccc51bc3f745f96571f1c68af26ae7955c1fa9ad1f2?
           s=32&d=mm&r=g)
         -  [Aaron Jorbin](https://profiles.wordpress.org/jorbin/)  8:45 pm _on_ January
           13, 2014
         - I agree that some good tutorials and foundation docs are important, but 
           I think that inline docsinline docs (phpdoc, docblock, xref) can help move
           us forward.
            * ![](https://secure.gravatar.com/avatar/92c9b71af01db9777d29870c622c80ef94d1344158eb2f5965f4bbe8efed251a?
              s=32&d=mm&r=g)
            *  [Eric Andrew Lewis](https://profiles.wordpress.org/ericlewis/)  10:29
              pm _on_ January 13, 2014
            * Definitely. I’m in for an inline doc-athon anytime after this week.
 14. ![](https://secure.gravatar.com/avatar/fb06ff3c303b2a6cc7ad89c7304e17b823782b919951eb9c6eb9eeb0012e8ac4?
     s=32&d=mm&r=g)
 15.  [two7s_clash](https://profiles.wordpress.org/two7s_clash/)  7:17 pm _on_ January
     13, 2014
 16. I wanted to point out that for a few years the flash player did support playlists:
     [https://plugins.trac.wordpress.org/ticket/1869/](https://plugins.trac.wordpress.org/ticket/1869/)
     See also: [http://jamesfishwick.com/3-6-audio-so-what-happens-to-blogs-using-the-old-jetpack-shortcode-for-generating-playlists/](http://jamesfishwick.com/3-6-audio-so-what-happens-to-blogs-using-the-old-jetpack-shortcode-for-generating-playlists/)
     Furthermore, I had a popular plug-in that did many of these things you list here
     called Jetpack Easy Playlists: [http://jamesfishwick.com/software/jetpack-easy-playlists/](http://jamesfishwick.com/software/jetpack-easy-playlists/)
     It worked on your “gallery” paradigm. The playlist still works if you hack Jetpack’s
     shortcodeShortcode A shortcode is a placeholder used within a WordPress post, 
     page, or widget to insert a form or function generated by a plugin in a specific
     location on your site. module and disable its check. If you want this to work 
     with 3.6 and up, edit this file: /wp-content/plugins/jetpack/modules/shortcodes.
     php
 17. Change line 51 to: “if ( version_compare( $wp_version, ’3.9-z′, ‘>=’ ) && stristr(
     $include, ‘audio.php’ ) )”
 18. ![](https://secure.gravatar.com/avatar/688e591b5d1baee94cff30ae8308c1ff5b54e336deabc134eb625d0de86020d3?
     s=32&d=mm&r=g)
 19.  [@ubernaut](https://profiles.wordpress.org/ubernaut/)  7:58 pm _on_ January 13,
     2014
 20. i think this all sounds awesome.
 21. ![](https://secure.gravatar.com/avatar/ed7f45a8ed2f6611258d19c3533c72d240f0058aab390f8533c0d4ed949cf4eb?
     s=32&d=mm&r=g)
 22.  [s3w47m88](https://profiles.wordpress.org/s3w47m88/)  8:02 pm _on_ January 13,
     2014
 23. We provide custom Theme WordPress websites to our customers and the primary challenge
     we face, regarding media, is that customers frequently are embedding video from
     sources beside the big guys (YouTube, Vimeo, etc…) so they have HTMLHTML HyperText
     Markup Language. The semantic scripting language primarily used for outputting
     content in web browsers. or something. But that requires them to have access to
     the HTML (insert blood curdling scream here). What would be a potential solution
     is a simple 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. on the right of Pages/Posts that allows them to paste whatever code
     they have, then see a rendered version without reloading the page, then the ability
     to drag that rendered video sample into the Visual Editor.
 24. As much as I like shortcodeShortcode A shortcode is a placeholder used within 
     a WordPress post, page, or widget to insert a form or function generated by a 
     plugin in a specific location on your site., customers still don’t get it for 
     some reason. Anything they hear the word “code” they freak.
 25.  * ![](https://secure.gravatar.com/avatar/479f05d4acc73915a43b24a1ee3f30477d4ee19bbec6a5a79906d396f2b2d2ad?
        s=32&d=mm&r=g)
      *  [Sam Sidler](https://profiles.wordpress.org/samuelsidler/)  9:16 pm _on_ January
        13, 2014
      * What you’re talking about sounds a lot like [the CEUX project](https://make.wordpress.org/ui/tag/ceux/)(
        currently on hiatus).
      * ![](https://secure.gravatar.com/avatar/27e1ec1c5ddd320f2cca5aa10cdf696b132db9230fa77ed87df5ca3c3ba6cbd9?
        s=32&d=mm&r=g)
      *  [Scott Taylor](https://profiles.wordpress.org/wonderboymusic/)  9:18 pm _on_
        January 13, 2014
      * the shortcodes get inserted automatically from the Media Library, don’t have
        to be written by hand – they are just the easiest way to save the most minimal
        data necessary in the post content without hardcoding markup or URLs
 26. ![](https://secure.gravatar.com/avatar/787450384271401e3d98d9f7a17953c64728c01b533e9aef46ec01abe7162170?
     s=32&d=mm&r=g)
 27.  [Tom Auger](https://profiles.wordpress.org/tomauger/)  9:31 pm _on_ January 13,
     2014
 28. Sounds like a pretty wide scope of things. I’m primarily interested in extending
     the Media Editor, and have prepared a feature-as-pluginPlugin A plugin is a piece
     of software containing a group of functions that can be added to a WordPress website.
     They can extend functionality or add new features to your WordPress websites. 
     WordPress plugins are written in the PHP programming language and integrate seamlessly
     with WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
     or can be cost-based plugin from a third-party. to this effect as a proof-of-concept.
     As I missed the deadline for 3.9, I was planning on waiting until the next round
     to bring this forward, but if work is being done in media-editor.js and friends,
     perhaps this is a good time to look at the challenges that the current architecture
     of the Media Editor presents, and my proposed solutions to it.
 29.  * ![](https://secure.gravatar.com/avatar/35e97a8a6a16cf83a8c3fe86cfb13429c092546ee7c1af870c707f55aaf62df4?
        s=32&d=mm&r=g)
      *  [Manny Fleurmond](https://profiles.wordpress.org/funkatronic/)  4:35 am _on_
        January 14, 2014
      * I was planning on tackling the media editor as well, specifically making it
        more modular and using Backbone. Would love to see what you have so far
         - ![](https://secure.gravatar.com/avatar/787450384271401e3d98d9f7a17953c64728c01b533e9aef46ec01abe7162170?
           s=32&d=mm&r=g)
         -  [Tom Auger](https://profiles.wordpress.org/tomauger/)  3:18 pm _on_ January
           14, 2014
         - Okay, well, when I get a few hours, I’ll throw up a post and share the code.
           I’ve completely modularized the “editor groups” – which are basically the
           Media Editor’s version of 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. Boxes. It is currently **
           possible** to extend the media editor without coreCore Core is the set of
           software required to run WordPress. The Core Development Team builds WordPress.
           modifications, but it’s really ugly and involves duplicating some core files.
           This is one of those cases where it would really benefit from some well-
           placed hooksHooks In WordPress theme and development, hooks are functions
           that can be applied to an action or a Filter in WordPress. Actions are functions
           performed when a certain event occurs in WordPress. Filters allow you to
           modify certain functions. Arguments used to hook both filters and actions
           look the same..
 30. ![](https://secure.gravatar.com/avatar/1fc50ce475e030ebe26a873bc0ea6152396262d2ec31566c9c0f84e9c7fa8fe0?
     s=32&d=mm&r=g)
 31.  [mttktz](https://profiles.wordpress.org/mttktz/)  2:44 am _on_ January 14, 2014
 32. Half of what’s important in WP is making sure that it is easy to create great 
     stuff and publish it on the web.
 33. The other half is people finding that great stuff. Right now other platforms do
     a better job of sharing and redistributing great stuff. Better or more sophisticated
     oembed would probably mean more WP posts that look “right” when someone shares
     them on another site or tries to link to them.
 34. That sounds really interesting to me – but I’m not sure what you are thinking 
     about there.
 35. ![](https://secure.gravatar.com/avatar/299ab71850a3d6fb44062f52ef927c600dd5570c3d4ce1286dff97342be6a31e?
     s=32&d=mm&r=g)
 36.  [David Lingren](https://profiles.wordpress.org/dglingren/)  3:48 am _on_ January
     15, 2014
 37. I was very excited to read this post!
 38. As the author of Media Library Assistant ([https://wordpress.org/plugins/media-library-assistant/](https://wordpress.org/plugins/media-library-assistant/)),
     I have devoted quite a bit of time and effort to enhance the Media experience 
     in WordPress. One of the frequent comments I get in my support forumSupport Forum
     WordPress Support Forums is a place to go for help and conversations around using
     WordPress. Also the place to go to report issues that are caused by errors with
     the WordPress code and implementations. is “this should be in coreCore Core is
     the set of software required to run WordPress. The Core Development Team builds
     WordPress.”, and I would be delighted to see any relevant parts of my work get
     to a wider audience.
 39. Two of your proposals are of particular interest. First, “Document the “new” Media
     code introduced in 3.5″. I have had several requests to enhance the Media Manager
     Modal Window, and I have devoted a frustrating amount of time to understanding
     the code behind it. One of the best aspects of WordPress is its provision for 
     actions, filters and other extension mechanisms; these are nowhere to be found
     in the Media Manager code. Consider these support requests I’ve received and responded
     to:
 40. Media sorting ([https://wordpress.org/support/topic/media-sorting](https://wordpress.org/support/topic/media-sorting))
 41. MLA and ACF image upload conflictconflict A conflict occurs when a patch changes
     code that was modified after the patch was created. These patches are considered
     _stale_, and will require a _refresh_ of the changes before it can be applied,
     or the conflicts will need to be _resolved_. ([https://wordpress.org/support/topic/mla-and-acf-image-upload-conflict](https://wordpress.org/support/topic/mla-and-acf-image-upload-conflict))
 42. categoryCategory The 'category' taxonomy lets you group posts / content together
     that share a common bond. Categories are pre-defined and broad ranging. selection
     when uploading media ([https://wordpress.org/support/topic/category-selection-when-uploading-media](https://wordpress.org/support/topic/category-selection-when-uploading-media))
 43. Hide edit cat and tags in media manager ([https://wordpress.org/support/topic/hide-edit-cat-and-tags-in-media-manager](https://wordpress.org/support/topic/hide-edit-cat-and-tags-in-media-manager))
 44. Different form field for category selection? ([https://wordpress.org/support/topic/different-form-field-for-category-selection](https://wordpress.org/support/topic/different-form-field-for-category-selection))
 45. Problem with Simplefields ([https://wordpress.org/support/topic/problem-with-simplefields](https://wordpress.org/support/topic/problem-with-simplefields))
 46. filterFilter Filters are one of the two types of Hooks [https://codex.wordpress.org/Plugin_API/Hooks](https://codex.wordpress.org/Plugin_API/Hooks).
     They provide a way for functions to modify data of other functions. They are the
     counterpart to Actions. Unlike Actions, filters are meant to work in an isolated
     manner, and should never have side effects such as affecting global variables 
     and output. not showing in modal popup window for image (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. [https://wordpress.org/support/topic/filter-not-showing-in-modal-popup-window-for-image-widget](https://wordpress.org/support/topic/filter-not-showing-in-modal-popup-window-for-image-widget))
 47. I would welcome an opportunity not just to understand, but to improve the Media
     Manager code.
 48. Second, you propose to “Abstract Gallery logic into “Collection” logic that Galleries,
     Playlists, etc. can use with minimal registration code”. This is a great idea,
     and should be extended to all of the items that can be stored in the “Media” Library,
     not just image, audio and video items. There are many sites using WordPress to
     manage large collections of other assets such as PDF documents. Let’s give them
     some attention as well.
 49. I look forward to following your progress and finding a way to contribute something
     to it. Thank you!
 50. ![](https://secure.gravatar.com/avatar/803828b32ae6d62391e6c26ff32e1a6e82064f8e4a29472876bac75731bca23c?
     s=32&d=mm&r=g)
 51.  [spacedmonkey](https://profiles.wordpress.org/spacedmonkey/)  4:31 pm _on_ January
     19, 2014
 52. With this move away from galleries to collections, (an idea which I really like
     btw), the gallery code should be rewritten to use walkers. This would make it 
     much much easier to override the markup that galleries output.
 53. ![](https://secure.gravatar.com/avatar/e4ffab6e721cd0f026a47028900c31121a7257662b07c3788329418b6d1e58d4?
     s=32&d=mm&r=g)
 54.  [Gregory Karpinsky](https://profiles.wordpress.org/tivnet/)  9:16 pm _on_ January
     22, 2014
 55. Mechanism of inserting video from a YouTube channel: show a list of available 
     videos, and let choose one?
 56. Can be based on formatting the output of a JSONJSON JSON, or JavaScript Object
     Notation, is a minimal, readable format for structuring data. It is used primarily
     to transmit data between a server and web application, as an alternative to XML.
     like this one:
      [https://gdata.youtube.com/feeds/api/users/musicinsummer/uploads?max-results=25&alt=json&orderby=published&format=5](https://gdata.youtube.com/feeds/api/users/musicinsummer/uploads?max-results=25&alt=json&orderby=published&format=5)
 57. Same can be used to show all recent uploads to a channel.

Comments are closed.

# Post navigation

[← Brainstorming ticket reports](https://make.wordpress.org/core/2014/01/10/brainstorming-ticket-reports/)

[Metadata changes weekly meeting to office hours →](https://make.wordpress.org/core/2014/01/15/metadata-changes-weekly-meeting-to-office-hours/)