Has anyone else had an issue with uploading Storyline 3 scorm packages into SumTotal Learn? I am interested in testing the new mobile capabilities in Storyline 3, but when I uploaded it to our LMS, I got an error message stating (see attachment)that gz, woff, and json files contained within the zip are unsupported.
our team is reviewing JSON files and how they are affecting the published output in certain LMS environments.
Here are some next steps that you can take.
If you determine that you don't want to use the Articulate Mobile Player (many people don't, given the new HTML5), you can uncheck that option during publishing.
Next, reach out to SumTotal support and ask if they have plans to allow these file types in SCORM content.
Any updates on this? Our client is also having failed uploads due to json file existing in storyline 3 builds. they had no problem uploading storyline 2 builds.
Well, this is an old post but I've come across similar issue for gz file type, and I simply included this new file type in the File Upload Security section of SumTotal.
You need to log in to SumTotal Learn as System Admin and then add the file type to the list of allowable file types under the Global Settings > File Upload Security Section (the path of this depends on the SumTotal version you use).
8 Replies
Hi there, Aaron! Thanks for giving Storyline 3 a spin! :)
Regarding those 3 file types:
and
Here are some next steps that you can take.
If you determine that you don't want to use the Articulate Mobile Player (many people don't, given the new HTML5), you can uncheck that option during publishing.
Next, reach out to SumTotal support and ask if they have plans to allow these file types in SCORM content.
Any updates on this? Our client is also having failed uploads due to json file existing in storyline 3 builds. they had no problem uploading storyline 2 builds.
Hi there Calvin,
What LMS does your client use? Have you had a chance to compare the behavior in another learning management system, like SCORM Cloud?
it's working on our own lms because we don't have any json restriction. but our client does.
Thanks for confirming that, Calvin.
I have heard of community members deleting JSON files in the published output, but that workaround hasn't been successful for all.
I'll leave the "what ifs" for removing those files to the community. Have you given it a try to see how it works for you?
i did remove the json file but not the reference in manifest, it's still working in our LMS. we'll have the customer try that.
Hi all,
Well, this is an old post but I've come across similar issue for gz file type, and I simply included this new file type in the File Upload Security section of SumTotal.
You need to log in to SumTotal Learn as System Admin and then add the file type to the list of allowable file types under the Global Settings > File Upload Security Section (the path of this depends on the SumTotal version you use).
Thanks for popping in to share Deepak :)
This discussion is closed. You can start a new discussion or contact Articulate Support.