Problem/Motivation
While working on adding these two asset types to the mix, we were in the belief that Widen was not capable of serving embed codes for them.
This belief of ours was also the background reason why we prioritized implementing on-site storing first, to be able to sync these media items locally if embed codes do not work for them.
However, the current tests show that things might have changed regarding this functionality:
- Audio assets are served as an HTML5 media player
- Generic assets are served as a simple anchor element, with the link pointing to a download URL.
For the sake of simplicity, beta5 was released with this exceptional embed code handling implemented. So now it's time to lift those limitations hitting these two newly added asset types and making them first citizens similar to their sisters.
Steps to reproduce
Create a media item for an asset of MP3 or TXT file by picking them from the media library modal in an entity reference field. Save the content and check the displayed results.
Proposed resolution
*Sigh* – Delete some of our nicely written code where necessary.
Remaining tasks
Update tests.
User interface changes
A unified UX both for content editors and for site visitors as well.
API changes
Tighter integration with the Widen software as all asset types will be served by their code in general, not circumvented in Drupal.
Data model changes
None.