Loading story_content from another location

Oct 08, 2014

Hi There!

We have developed a number of courses using Storyline but have a requirement to load the assets (videos) from another server. This is because our users have local content servers at their locations.

While we are able to link to a video file from another location in storyline, you do not get the same control and functions that you get when you embed a video.

We were able to get it that the LMS calls the entire course from the content server, but then we have a cross-domain issue when it comes to updating the LMS.

Is there a way to have the 'story_content' folder exist on another server/location, and if so, how do we implement this.

The other challenge is that each content server has a different address, we are able to pass a url parameter to the content on launch, and would like to use this parameter to call the story_content folder assets from.

3 Replies
Leslie McKerchie

Hi Xenothan and welcome to E-Learning Heroes!

Perhaps someone in the community will be able to assist you with this, but for you and anyone else that may run across this thread, I wanted to share our recommendation.

If you view published Storyline content on your local hard drive or send it to someone else to view on their local hard drive, you'll encounter security restrictions from the computer, web browser, Flash Player, and network that'll cause various features of your content to fail.
To properly test your published content and share it with others, upload it to the environment for which it was published. Please review this article for details.
Tony Fung

Hi Xenothan,

I want to ask have you found a way to achieve your previous goals?  It is because I am facing a very similar situation that we want to fasten the download speed of assets (mainly video and audio) in the published SCORM.  We want to store the assets to the users' local disks and at the same time the SCORM is hosted in our LMS.

It is much appreciated if you or anyone could share experiences about this. 

This discussion is closed. You can start a new discussion or contact Articulate Support.