Drupal Association members fund grants that make connections all over the world.
We had and have quite some trouble with the WYSIWYG integration provided by media.
I think one of the reasons is that people that should / would solely focus on the media handling are bothered with WYSIWYG stuff - which's quite another problem space.
There's enough work in the Media / File Entity world already, and interruptions by WYSIWYG stuff doesn't help getting the work there done.
One general module that provides the basic handling including a JS API for WYSIWYG integrations similar to / the same as the one provided by Media.
With integrations for each WYSIWYG integration module e.g. WYSIWYG, CKEditor incorporated.
- Provides by default an enabled wysiwyg file display mode (Ensures only a single html tag (
<img />) is used as placedholder).
The default behaviour could be overwritten by more complex WYSIWYG integrations..
- The WYSIWYG JS API as currently provided by media - to be extended.
- The integration into the WYSIWYG module as currently provided by media
- The integration into the CKEditor module as provided by (second priority).
Ok, so inline embedding of media via the plugin supplied by the media module. It almost works!
What I'd like to do Is help in a push to get the work finished. Here's my findings and my current set up.
Ok so using media v1 (not the unstable v2) both dev and beta 5, latest stabl and dev of wysiwyg and Drupal 7.8.
Ok, long story short, the problem with the current dev as I see it is that when editing via wysiwyg (CKEditor) the current media-wysiwyg plugin tries to render the complete player (passes rendering to the media module, in turn to the file display formatter). It should be using a placeholder and only applying the formatter on node display, when relivent JS/CSS libs can be added ect)
in more detail...
From what I can tell, as far as adding the inline media elements goes, all works well, if you stick to the file display mode (under media) as generic file there is no problme at all.
The problem is that if you set the display formatter (via media) to anything other than generic file the wysiwyg removes the markup on attach as it fails to render properly, also if anything other than generic file is selected the media embed popup breaks and won't submit on the output settings form.
It's soo close though, adding a file (formatting set to generic for all types) works, as does displaying the file (icon displayed), and clicking edit shows the file icon as expected too!
However once the output formatter gets changed the editor strips the media embed on attach, and trying to add media inline does not work as the submit button fails on the output mode screen.
As a test I tried adding the media via wysiwyg with the output formatters all set to generic file. No problem there, once I'd edited the node I went and changed the output formatter to a video renderer (mediaelement is being used for testing) and the inlien media is rendered correctly and formatted in the chosen formatter! Only problem is this formatter breaks the wysiwyg on re-editing.
My opinion is that when in the editor a placeholder image should be used regardless of output styling (currently it seems to want to try to style the output within the editor, which breaks it). and that the output styling should be applied on the input format level (replace the image with forced attributes with the relevant formatter), the last piece to the puzzle is parsing the media inline code (the [mediaxxx] coding) when the edit button is clicked back into the placeholder with attributes.
It seems that this is not too far from the direction dev is taking. Anyone out there that I can talk to to get involved finishing off this (currently broken) solution??