Importing an Existing Project into Storyline - Engage Interactions

Hi Jamie and welcome to Heroes! 

It sounds like you created a project in Presenter that you've imported into Storyline? You may need to import the Engage elements separately.

Let us know if you're still having difficulty importing the Engage objects themselves. 

Hi,

I am still having problems with the Engage files.

Here is what is happening:

I imported the original Engage files into Storyline. Once I did this, they worked fine for me. So, I published the project and viewed it again and it worked fine. Once I copied the files to an FTP drive for another person to view, they were unable to view the Engage slides (4 of them) in the presentation and the exit button would not work.

Can you please tell me what I need to do to get this person to be able to view this project properly on an FTP site.

Thanks,

Jamie

Hi Jamie,

So the other person is viewing the published output files and not the .story file? You should be able to FTP the files as described here but I'm curious if this is a FTP drive that is more of a network drive or an FTP server/website? If it's a network drive, I'd suggest placing the content within an actual web server so that they can test the output online as Engage files are inserted as Web objects. 

Hi,

I am still having issues view the 4 engage interaction slides that I imported into my presentation. When I publish this to a CD, then I can see the 4 engage slides and the exit button work. However, I need to publish for Web and I also need it to launch in a new window.

When I publish to web, the engage slides stop working, the exit button doesn't work and I can't launch the launcher.html file.

Please help. I spent most of the day yesterday trying to get this to work and I cannot get it to work. I have two other presentations that need to be published the same way, so I must get this to work.

Thanks,

Jamie

Hi Jamie,

I'm sorry that you're still having issues, but I'm still not clear about the process you're going through to test this published output. For the Engage slides and exit button to all function as expected when published for Web or LMS you'll need to load it into one of those environments. Testing the published version off a local drive, network or shared drive, or USB could cause odd behavior and elements of your content to fail. If you aren't yet ready to place the content on a web server or in your LMS you could use one of the web server options below to test the content or for an LMS upload it to SCORM Cloud which is a free, industry standard testing method for SCORM content:

• Tempshare: This is a free service provided by Articulate for testing Storyline content. Note: Uploaded files will be deleted after 10 days.
• Amazon S3: Amazon S3 offers free hosting with generous usage limits. If you go over your limit, you'll be charged a graduated fee.
• Dropbox: Place your published output in the Public folder in your Dropbox account to share it with others.
• Google Drive: Change the story.html file to index.html, and set the sharing permissions to Public. Here's how.

If you are testing it within those intended environments and still experiencing some odd behavior there are some known reasons documented here on why the Engage interaction may not work and the exit tab is described here. 

Also, if you'd like me to take a look at the file as well I'm happy to - you'll want to share the .story file here with us and if you'd prefer to share privately I can send you directions on how to send to me directly. 

Hi Ashley,

Thank you so much for your help.

I will read the links that you sent and try to get it to work. I may ask for you to look at my file if I cannot get it to work.

Thanks again,

Jamie

Happy to take a look Jamie - just let me know!