I've imported engage to Storyline 2 both through the pptx and as a separate file and the Engage slides are showing up blank on both a customer's lms and SCORM Cloud using an ipad with ios9. Is there a tool or tip to use for success? It works on a computer but not an ipad.
Engage 09 didn't include HTML5 support - so you won't be able to view it within the iPad in mobile safari or the mobile player app. If you have Engage '13 (or even want to use the trial) you could update the interaction and insert that into Storyline. Please note that you can't have Engage '13 and '09 installed on the same system - so it will remove Engage '09 but you can always reinstall after the fact.
Sorry Steve - I totally misread that! For Engage '13 content you'll want to review the information here in regards to setting it up for HTML5 deployment. Since you import in the Engage file into Storyline normally it loses the file's ability to determine to show the HTML5 so that article will walk you through the steps around it.
Also, double check that you're using the latest update of Storyline and Engage - as they both included fixes dealing with iOS9.
I've taken the steps in the notes on importing - do you have anything more specific to issues with Engage specifically showing up blank on ipads with ios9?
First, I wanted to let you know that responding via email includes your signature here - so you may want to edit the post to remove that information.
Were you able to open the article that I attached above? Here's the relevant snippet:
When you use this automatic import method, Engage interactions are embedded as Flash objects. As a result, they aren't supported in HTML5 output or the Articulate Mobile Player app. See also:
So that would prevent you from seeing them in iOS9 or earlier regardless. If you need to embed them in your Storyline course, you'll want to publish first in Engage (using the latest update 7) and then host that published content on a web server that you can link to in your Storyline 2 course as a web object. Also make sure you're using the latest update of Storyline 2 (also update 7) to publish as it offers support for iOS9. Directions on how to set this up are include in the previously linked article.
Hope that helps clarify and please let us know if you need anything else!
Thanks - You've put me on the right track now. I have Storyline 2 (just purchased Oct 22) so I have the latest one and a new user. I've read the links above but most reference importing & editing. I need the specific steps in linking to the Engage as a web object. I changed the Engage player browser settings to 'launch player in new window' and published but need steps from Storyline slide to link to it. Am I getting there? Thanks.
It looks like you meant to include an image here? But they're not included when you respond via email. If you'd like to visit the thread you'll be able to upload an image using the "add attachment" button at the bottom of the insert image icon at the top of the reply window.
The "launch player in new window" is generally specific to an LMS setting or for when the user clicks on the link in the window and it needs to launch in a new window. If you want it to appear within the Storyline interface, I may not select that option and then just embed directly into the Storyline slide. I would definitely display it with no browser controls though - that way it'll appear more seamless with your Storyline slide.
I really feel close - tried the index.html and got a blank screen so I uploaded the published Engage and linked to it and received the attached message. Could you & I call and do a 10 minute WebEx - I've done this about 10 times unsuccessfully - how about tomorrow at 9AM?
The published Engage output will have a file with interaction.html and that is the file that needs to be renamed to index.html. Once you've done that, you'll use that file to link it within your Storyline course, prior to publishing, as a web object. You'll also want to make sure that once you've published the Storyline file, you're uploading the entire published output folder to your web server or LMS - testing it locally may not allow the web object to play. If you're not ready to place it on a live site you could look at using one of the options mentioned in this article.
16 Replies
Hi Steve,
Engage 09 didn't include HTML5 support - so you won't be able to view it within the iPad in mobile safari or the mobile player app. If you have Engage '13 (or even want to use the trial) you could update the interaction and insert that into Storyline. Please note that you can't have Engage '13 and '09 installed on the same system - so it will remove Engage '09 but you can always reinstall after the fact.
Ashley Terwilliger,
I have Engage 13.
Steve
Engage 13 not working on ipads with ios9.
Sorry Steve - I totally misread that! For Engage '13 content you'll want to review the information here in regards to setting it up for HTML5 deployment. Since you import in the Engage file into Storyline normally it loses the file's ability to determine to show the HTML5 so that article will walk you through the steps around it.
Also, double check that you're using the latest update of Storyline and Engage - as they both included fixes dealing with iOS9.
Ashley,
I've taken the steps in the notes on importing - do you have anything more
specific to issues with Engage specifically showing up blank on ipads with
ios9?
Steve O'Connor
Hi Steve,
First, I wanted to let you know that responding via email includes your signature here - so you may want to edit the post to remove that information.
Were you able to open the article that I attached above? Here's the relevant snippet:
When you use this automatic import method, Engage interactions are embedded as Flash objects. As a result, they aren't supported in HTML5 output or the Articulate Mobile Player app. See also:
So that would prevent you from seeing them in iOS9 or earlier regardless. If you need to embed them in your Storyline course, you'll want to publish first in Engage (using the latest update 7) and then host that published content on a web server that you can link to in your Storyline 2 course as a web object. Also make sure you're using the latest update of Storyline 2 (also update 7) to publish as it offers support for iOS9. Directions on how to set this up are include in the previously linked article.
Hope that helps clarify and please let us know if you need anything else!
Ashley,
Thanks - You've put me on the right track now. I have Storyline 2 (just purchased Oct 22) so I have the latest one and a new user. I've read the links above but most reference importing & editing. I need the specific steps in linking to the Engage as a web object. I changed the Engage player browser settings to 'launch player in new window' and published but need steps from Storyline slide to link to it. Am I getting there? Thanks.
Hi Steve,
Sure the directions on linking to the Engage as a web object are below:
You could also place the Engage interaction on a web server and use the URL to link to a web object following these directions linked here.
Ashley,
Is this the proper Engage Player setting:
Steve
Hi Steve,
It looks like you meant to include an image here? But they're not included when you respond via email. If you'd like to visit the thread you'll be able to upload an image using the "add attachment" button at the bottom of the insert image icon at the top of the reply window.
Is this the right Engage Player setting?
Hi Steve,
I guess it depends on "right" for what...? :-)
The "launch player in new window" is generally specific to an LMS setting or for when the user clicks on the link in the window and it needs to launch in a new window. If you want it to appear within the Storyline interface, I may not select that option and then just embed directly into the Storyline slide. I would definitely display it with no browser controls though - that way it'll appear more seamless with your Storyline slide.
I really feel close - tried the index.html and got a blank screen so I uploaded the published Engage and linked to it and received the attached message. Could you & I call and do a 10 minute WebEx - I've done this about 10 times unsuccessfully - how about tomorrow at 9AM?
Hi Steve,
I don't have the ability to do a call or a webex - you can purchase a web conference, but it may be too much for what you need.
Ashley - Which file gets the index.html?
Steve
Hi Steve,
The published Engage output will have a file with interaction.html and that is the file that needs to be renamed to index.html. Once you've done that, you'll use that file to link it within your Storyline course, prior to publishing, as a web object. You'll also want to make sure that once you've published the Storyline file, you're uploading the entire published output folder to your web server or LMS - testing it locally may not allow the web object to play. If you're not ready to place it on a live site you could look at using one of the options mentioned in this article.
This discussion is closed. You can start a new discussion or contact Articulate Support.