Publish to CD - issue with links

Sep 25, 2014

Alyssa Vass
By Alyssa Vass

I have a dilemma that I'm hoping someone will have a workaround for.

I have a 10 module series that we are wanting to put onto USBs for distribution. Each module has a number of triggers that open either a URL or a PDF

We have built a html page to host the modules on so that when the user plugs in the USB they click the HTML file and it opens in their web browser whether they are connected to the internet or not.

Our issue is that the modules, when published to CD and hosted in a html page like this, use Flash. Flash's security settings do not allow local (i.e not served from a webserver, but loaded with file://) content to open when it considers it an "External" link. Even with the PDFs built into the back end and included in the local distribution, Flash still considers these external links. It also won't open the URLs.

I've searched the Forums and seen others have had similar issues but none of the solutions listed will work for us. Here's why:

1. We want to make usability absolutely basic so nothing that requires having to navigate to Flash's security settings (especially as no warning appears that something's been blocked - when you click on the object with the trigger simply nothing happens)

2. Furthermore, most of the people we are distributing the modules to will be accessing the USB via a government computer and will not have access to administration rights to change security settings.

3. This also means that running a .exe file (such as the storyline window "launch_story.exe") won't be allowed either. Likewise with hosting the modules in a standalone web browser that's built on the USB.

4. Furthermore, .exe files will mean mac people won't be able to use the resource.

If any one has any ideas I would be VERY appreciative.

Thankyou. Alyssa.

5 Replies
onEnterFrame (James Kingsley)
over 9 years ago09/26/14 at 9:06 am (UTC)

Generally the HTML5 output does not that limitation. 

You could:

  1. Publish the course for 'Web' with the HTML5 option.
  2. Then remove the story.swf, story.html, and story_unsupported files from the published folder.
  3. Rename story_html5.html to something friendlier like Start_Course.html
  4. Copy the published files to CD. 

A few caveats:

  • The will need an HTML5 supported browser.
  • Ensure all your course's features work in HTML5. 
Alyssa Vass
over 9 years ago09/28/14 at 8:19 pm (UTC)

Thank you for your suggestions.

Unfortunately, the first suggestion to publish only in HTML 5 is that there are a number of graphics and animations we've included that don't publish properly in HTML5 so there would be a LOT of rebuilding and checking to go down that path.

For the htmlexe.com option - this would still mean Mac users couldnt access them.

Any other ideas?

(I know we may have to got down the re-build/HTML5 pathway but it is such a lot of work i'm hoping we don't have to)

Thankyou.

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