[meta] Better media handling capabilities

Same problem with mediaelement, mediafront.

Agreed - Commons should support this.

I suggest looking in the JavaScript console in your browser and reporting any errors that might be causing Media module's scripts to fail and reporting those to this issues.

In general, this seems like it depends on #1879036: Replace Aloha with CKEditor via CKEditor project, so marking postponed.

This is a must ... It's not very social without a gallery :)

I would have to disagree here on a media gallery. I still see Commons as just that and if you start trying to tack on galleries, then it is becoming less common and more complex(Drupal Specifics). There are many fine gallery solutions out there, but which one do you go with? Media Gallery looks nice, but the latest version is still in Dev. I personally plan to use Galleria with Commons, which will probably be a nightmare to implement seeing the current JavaScript issues with Commons.

I'm not sure why Media Module is not in Drupal core, but it should be in Commons. I'm just sort of waiting for the official word on what's being used, and then I will begin testing it out.

Just to note that I did go back to the Media gallery page, and it would appear to be a shoe-in for inclusion. :) I still stand by my earlier words, but I can now definitely see the motivation to include it thanks to those very same words. I will begin looking at Media Gallery.

Looking at this it seems Media and Media Gallery will get a place in commons, right?

Greetings, Martijn

And now that http://drupal.org/node/1879036 is fixed, am I ok to set this to active again, right?
If not I apologies for this.
Greetings, Martijn

Retitling to better suit the conversation. Actually compatibility issues between modules included with Commons and media management modules such as Media are the responsibility of the individual modules themselves and are being worked on in separate issues such as #1504696: Integration with CKEditor module.

This is just a thought on media, and how it pertains to social sites such as this, given that social sign-in is already in the works well in Commons, I would like to suggest Scald Media Management It is actively developed and it's drag and drop atom capabilities has the potential to change a lot on how commons handles media. By storing all of the elements that can be added, images, galleries, video, and sound files into entity like structures, its ability to give the end user access to all of thier media regardless of where it resides, and regardless of which device they are using, as well as being a guest on a machine is by far my choice on how I would personally approach media handling. Lastly, it does a good job of removing redundant media, by creating a single entity regardless of the number of times it is added to posts.

Click for a list of Scald related projects

Scald: Customtext A minimal implementation to embed reusable text snippets into your content.
Scald: Embed.ly
Scald: Facebook
Scald: File Provider
Scald: File A minimal implementation to support Document uploads.
Scald: Flickr
Scald: Gallery
Scald: Instagram
Scald: KitDigital
Scald: PDF use PDF module (itself uses Mozilla pdf.js)
Scald: Slideshare
Scald: Soundcloud
Scald: Twitter
Scald: Viddler
Scald: Brightcove (sandbox)
Scald: Bean (sandbox)

Marked #1886804: Individual user gallery as a duplicate.

I've spent some time going through File entity + Media and determining what would need to be done in order to incorporate them into Commons.

File Entity

Description: Extends core's "minimal" File entity into a full-fledged entity (adds core module integration, page callbacks, view modes, file types, makes files fieldable).

Status: The current -unstable release is old and should be avoided. The -dev is stable and shouldn't pose any problems (especially if updates/commits are monitored).

Stable release blockers:

• #1496942: Support making any kind of meta-data available to file_load() and file_load_multiple() consumers
• #1977662: On fresh install, existing files are assigned to 'undefined' file type
• #1959260: Ensure a 'file_access' tag is used on all queries of outputted files => alpha1 breaks EntityFieldQuery not releated to files

Other issues that may affect Commons:

• #1845516: Custom file types exported through Features are missing mimetype information.

Media

Description: Integrates with WYSIWYG to allow users to embed files into textfields and provides a popup media browser to allow for file reuse in fields. Handles images out of the box and requires entensions to manage other media types.

Status: Media 1.x has been feature frozen for a long time. The current -unstable release is old and should be avoided. The -dev is stable and shouldn't pose any problems (especially if updates/commits are monitored).

Stable release blockers:

• #1903224: After upgrade I lost field and values from application file
• #1844768: Duplicate entries in file_display table cause PDO Exception on installation
• #1792738: Allow custom file view modes for WYSIWYG display
• #835516: Add ability to edit file meta data and fields when embedded in WYSIWYG
• #1314266: Replace media tag in wysiwyg only if the type equals to "media"

Other issues that may affect Commons:

• #1951964: Media Button in WYSIWYG CKEditor 4.1+ broken

CKEditor/WYSIWYG

Description: Enable adding client-side JavaScript editors to enhance the content authoring experience.

Other issues that may affect Commons:

• #1504696: Integration with CKEditor module
• #1853550: Ckeditor 4.0 - The version of CKEditor could not be detected.
• #1956778: Ckeditor 4.1 ACF

oEmbed

Description: oEmbed is a format for allowing an embedded representation of a URL on third party sites. The simple API allows a website to display embedded content (such as photos or videos) when a user posts a link to that resource, without having to parse the resource directly.

The oEmbed module (https://drupal.org/project/oembed) integrates oEmbed into Drupal which allows users to embed content from oEmbed providers into textareas (text filter), embed content using WYSIWYG by integrating with Media and even allows your site to become an oEmbed provider itself.

Current status:

• Well supported and handles all providers with a single configuration (no real issues)
• Supports many providers out of the box (YouTube, Vimeo, Soundcloud, Twitter, flickr)
• Provider list can be greatly expanded with an embed.ly subscription (Brightcove)

Marked #1342838: Add IMCE and bridge as a duplicate.

Has there been any progress on media handling in Commons? I'm currently looking for an 'inline image' solution at the moment. Are there any current best practices?

Should I add an ImageField to a Post (etc) and allow folks to insert it inline? I read an earlier Commons issue that indicated in 2.x that Commons used the Insert module.. but I don't see that module in Commons 3.x. I can certainly try that.. but I'd love for my solution to follow best practices for where Commons is now and is moving toward for the future. Thanks.

Any news for integrating photos, video gallery with Commons ?

A strong community must have a media gallery per user and group.

Thanks