To help organize your content, you can now create folders in the Content, Equivalents, Bundles, and Account Content sections of the application.
Media File Support
Now you can import MP4 videos and PDF documents, and distribute them to LMSs just as you would any standards-based content, with the same licensing and export options. Users can also upload WebVTT files to add subtitles or closed captions to their video content.
Improved LTI Exports
In addition to sharing courses as LTI 1.1, we've added support for LTI 1.3 links. We will continue to support sharing content using LTI 1.1, we’ll support a different model for LTI 1.3 that is more in line with industry best practices. Under the new model, each account is an LTI tool, and each shared course is a resource provided by that tool. In addition, we will support exporting links for LTI 1.3 resources in a Thin Common Cartridge package. These changes are intended to make it easier for LMS administrators to accept content from vendors who use Content Controller because they only need to register a single tool to make use of any amount of content.
Force Frameset for Mobile Launches
We added a new setting that can be used to specifically change the behavior of launches on mobile devices. Some mobile browsers can cause problems when the SCO Launch Type is set to "New Window", so we added the "Use Frameset SCO Launch Type For Mobile Devices" checkbox to the course configuration menu. That setting will check the browser's User-Agent, and if the User-Agent matches a configurable set of criteria, then the course will launch as though the SCO Launch Type is set to "Frameset". You can configure the criteria of what is considered a mobile device in the application settings.
Previous versions of Content Controller have included support for Scorm Driver Cross Domain (SDXD), and Content Controller 3.0 now ships with RXD 3.1. The new version of this technology includes a number of bug fixes and improvements over the previous.
Note to self-hosted customers:
Content Controller is built around its sister product, Rustici Engine. When upgrading between major versions (e.g. 2.1.xxx -> 2.2.xx or 2.2.xx -> 3.0.x), we need to also upgrade Engine's database schema. To do this, just add the argument
-e engine_upgrade=true to the command for running your playbooks. This flag tells Ansible that this particular deployment requires the Engine upgrade. You won't be required to use this flag when moving between maintenance releases (3.0.174 -> 3.0.181) unless specified in the release.