Sitecore Media Framework Ooyala Edition module - using HTML5 player instead of Flash player

Another nugget of knowledge concerning the Sitecore Media Framework Ooyala Edition module (2.1 rev. 150323). When embedding a video using the Rich Text Editor, the default behaviour seems to be to output the video and its controls using Flash, with a fallback to an HTML5 player when Flash is not configured for the user's browser. If you want to change this to always use the HTML5 version of the player, simply amend the <scriptUrl> elements in App_Config\Include\Sitecore.MediaFramework.Services.Ooyala.config as follows (or use a patch file ;) ...) - credit to Sitecore Support for this:

    <playerMarkupGenerators>
        <add name="ooyala_video" templateId="{C3B8C43D-AD6B-49E2-9C6E-2FB4B53A966A}" type="Sitecore.MediaFramework.Ooyala.Players.OoyalaPlayerMarkupGenerator,Sitecore.MediaFramework.Ooyala">
            <analyticsScriptUrl>/sitecore modules/Web/MediaFramework/js/Analytics/ooyala.js</analyticsScriptUrl>
            <scriptUrl>//player.ooyala.com/v3/{0}?platform=html5%26namespace={1}</scriptUrl>
        </add>
        <add name="ooyala_channel" templateId="{49731DEB-A021-448F-ABC2-B9238D5A7E05}" type="Sitecore.MediaFramework.Ooyala.Players.OoyalaPlayerMarkupGenerator,Sitecore.MediaFramework.Ooyala">
            <analyticsScriptUrl>/sitecore modules/Web/MediaFramework/js/Analytics/ooyala.js</analyticsScriptUrl>
            <scriptUrl>//player.ooyala.com/v3/{0}?platform=html5%26namespace={1}</scriptUrl>
        </add>
    </playerMarkupGenerators>
    

Note that I've also changed the URLs to be protocol relative, as we were having browser issues loading non-secure scripts when the page was accessed via an https QA environment.

 


By James at 18 Aug 2015, 21:33 PM


Comments

Post a comment