Can you attach .Zip files to Resources tab for download?

Hi Guys,

So I have a client who wishes for downloadable .zip files types to be accessible through the course I am building for them.
I have attached PDF's & Word documents this way in the past but not a .zip file...
I attached it anyway and seemed to be working fine but when I uploaded and tested I was presented with an error message any time I clicked on the file to download.
I have attached my .story file and also a snippet of the error I receive when I try and download...
Strange as when I "Test Launch" the course through my LMS the download seems fine?...
I had originally hosted the zip folder online and used the trigger function to download the zip using the link url but my client wants the download hosted locally as the site is not a permanent option.
Any help/advice at all would be greatly appreciated!...

3 Replies
Matthew Bibby

You should be able to manually move the .zip into the published output and link to it there from a slide using a Jump to file/URL trigger - but I don't think you can add it to the resources in this way.

For your info, when a resources is added to a Storyline course it will be copied to the story_content/external_files/ directory when the course is published.

That means that you can link to that resource from a slide by using a Jump to file/URL trigger that points to story_content/external_files/YOURFILENAME.doc

However, from memory, I don't think you can add a resource in this same way, as when you enter story_content/external_files/YOURFILENAME.doc Storyline will automatically add a http:// to the front... which will break everything. But I could be wrong about this as it's been ages since I last tried.  

So you could add a button or a link to a slide that points to story_content/external_files/ and then move the .zip file to that location after publishing.

However... if you are using an LMS, it is possible that it won't accept a SCORM package that contains a .zip file as they can be perceived as a security risk.

If you run into this issue, you may be able to get around it by adding the file name to the LMS manifest. Yell out if you need a hand doing that. Happy to help where I can.