My converted Studio 09 module works well when run locally by linking to story.html. But when posted on our company intranet, the Engage files generate a Page or Document Not Found error. The company Intranet requires that all file and path names be lowercase. See the path, below, created by Storyline 2 when published for Web (HTML5 features unchecked)
\story_content\webobjects\6tksvxxuqx7\engage.html
I got the same result before changing the WebOjects folder and sub folders to lowercase.
I can double-click the engage.html file and it runs.
Do you know what causes this or a workaround, please?
Thank you for the reply. My colleagues and I have reviewed the tutorials and it seems we've followed them to the letter. In the essence of time, we will recreate the Engages directly in SL2 for now and continue to investigate later.
Hmmm. We were instructed to change all to lowercase. However, we did also test with the original file folder as mixed case with no different results. Thank for the suggestion to host the Engages and link to them. I'll present that to team to see if it's a possibility.
5 Replies
Hi Betty!
So you are importing an Engage Interaction into Storyline as explained in this tutorial?
You should be publishing and sharing the Storyline file as explained here and sharing the story.html file once uploaded.
Changing the path name to lowercase on any server that is unix based will throw an error as WebObjects and webobjects are two different folders.
It may be better to host the engage on the intranet and then link to it.
Hi Leslie,
Thank you for the reply. My colleagues and I have reviewed the tutorials and it seems we've followed them to the letter. In the essence of time, we will recreate the Engages directly in SL2 for now and continue to investigate later.
Thank you again,
Betty
Hi Phil
Hmmm. We were instructed to change all to lowercase. However, we did also test with the original file folder as mixed case with no different results. Thank for the suggestion to host the Engages and link to them. I'll present that to team to see if it's a possibility.
Betty.
Thanks for the update Betty. Just let us know if you need further assistance.
This discussion is closed. You can start a new discussion or contact Articulate Support.