MEE called scald_sas_to_rendered too early in the field view
process, before the content went through check_markup. This meant
that the atom markup was filtered, and you either had to allow
<object /> tags or lose the video.

The conversion now occurs /after/ check_markup is called, meaning
that site administrators can again restrict the allowed html tags.

Viktor Boykiv authored Sep 28, 2012 and DeFr committed Sep 28, 2012

Overall, even thought unchecking the "Fetch" checkboxes in the "Openly
available actions" atom edit form implements a nifty soft delete that
makes the atom disapear for every one but admins, people trying out
the module "in the wild" asked for a way to really delete unappropriate
content through the UI, so let's add it.

Previously, user could get an atom preview by clicking on an element
in the library, which opened a preview tooltip powered by an embedded
version of the BeautyTips library.

The embedded version now got removed, and replaced by a thin
compatibility layer with the qTip module and library. Users willing to
get the preview now needs to either download and enable the qTip module
or ensure by themselves that the qTip jQuery library is loaded.

This is a 'hotfix' to prevent users clicking on the "Search on Daily
Motion" link in the modal window from clobbering all the values they
previously enterred, and having to start from scratch.

The long term fix we're working on is to ajax-ify this form,
re-integrating the search form in the atom creation process.

MEE was supposed to convert SAS-representations to rendered one
only when the Drag'n'Drop setting was enabled; before this commit,
it instead erroneously tried to convert every "formatted" text field.

Add a CSS file to be used with RTE so that Atom wrapper markup could be recognized. It does nothing by default, you'll have to configure your RTE.