The Articulate Updater scans and updates Storyline 2, Storyline 1, and Studio '13 published content to make it compatible with iOS 9 without having to re-publish your courses.
We're working on finalizing Studio '13 Update 7 for iOS 9 support, which we'll release soon.
It should work on any elements you have already published and if you need to use the FTP method as Russ mentioned you'll want to follow the steps here at the bottom of the article.
As for the courses from SL1 - if you had upgraded them into SL2, you don't need to do any republishing from SL1 - just upgraded the SL2 version as described.
You can also see the Articulate updater will work across products as shown here:
Date
Version
Feature
Output
September 15, 2015
2.0
Added support for Apple iOS 9
Storyline 2 Studio '13 Storyline 1
Please let us know if you run into any issues using the updater and if there is anything else we can assist with.
We've had courses still in our LMS from when we only used SL1 which are not converted ever pubbed in SL2. Do we need to first repub these out of SL2 U4 or U7 and reupload them so the Articulate Updater works or can we leave them alone and scan with the Articulate Updater as is currently uploaded in our LMS?
If an LMS uses iFrames, is my interpretation of this correct? Does this mean that the Articulate Updater cannot therefore be used via updating on the LMS site because each course's pubbed set of files need the below manipulation of code manually???
"How to Launch iFrame Courses in the Articulate Mobile Player in iOS 9Some learning management systems use iFrames to display courses, and iFrame content may not launch as exptected in iOS 9. For example, nothing may happen when you tap the Launch button for a Storyline course. Here's how to fix it:
After publishing with the latest Storyline update installed or using the Articulate Updater to scan and update your published files, go to the folder that contains your published course and open the amplaunch.html file in a text editor, such as Notepad.
Find this line of text:
<a id="launch" href="#" class="button">Launch</a> And replace it with this text:
<a id="launch" href="#" class="button" target="_top">Launch</a> Save and close amplaunch.html.
Zip your published files and upload the zip file to your LMS."
Shouldn't this be already an executable code within the Articulate Updater already?
Unfortunately, iFrame content may not launch as expected in iOS 9, and if you find that to be the case with your LMS, you can use the code change above to fix it.
To be more specific, the recommended code change you've referenced is only necessary if you find that the Launch button on the Articulate Mobile Player (AMP) launch page doesn't work with a single tap (although you can still tap the Open button on the AMP banner). This code change just allows the Launch button to work.
We'll try to address this in future versions of Storyline, but for now, the sequence is:
Install the latest software update and republish (or run the updater) on your LMS content.
If the Launch button doesn't work with a single tap, then add the code change to the amplaunch.html file.
Please let us know if you need anything else, and have a great day!
I still have SL1 content on my LMS (is it required to repubb all of these said courses in SL2 first prior to running the Articulate Updater in the LMS to update said courses - we have almost 1,000 courses)
Is it normal for an HTML5 /TinCan (all player unchecked) pubbed course to only track on iOS or mobile devices? I thought the HTML5 would track on desktop and laptop platforms?
If I run the updater in my LMS, will that physically change the player to look and behave itself in ALL selected courses to the latest Update 7 player... (the concern then would be we really have no way to telling which and how many Launch buttons are impacted if an iFrame LMS).
The Articulate Updater scans and updates Storyline 2, Storyline 1, and Studio '13 published content to make it compatible with iOS 9 without having to re-publish your courses. You do not need to upgrade your Storyline 1 content to Storyline 2 in order to gain compatibility with iOS 9.
HTML5/Tin Can content should absolutely report scoring/completion data to the LMS from any supported desktop/laptop browser. If this isn't happening, please submit a Support Case so that we can take a closer look at the problem with you.
If you run the updater within your LMS, it will scan and update your published courses to add compatibility for new operating systems and web browsers, including Google Chrome 44+ and iOS 9. The updater will not change the appearance or the behavior of the player beyond adding this compatibility.
Please let us know if you have any other questions.
One last thing for now. Can you please tell me if it is the downloaded AMP that sends the course completion tracking info to our LMS or not? And if not, then what technology and what actually gets sent to our LMS as tracked/completed. The reason I ask is when I pub, my LMS says they don't need me to check both the "Use Articulate Mobile Player for iOS or Android" nor the "Allow downloading for offline viewing."
I know that SL2 U7 will always prompt to download that AMP on iOS so that covers whether or not the app is on there or not. I know that SL2 U4 on iOS 8 doesn't.
If you have published for AMP and you need to track in your LMS, you'll likely need to ensure you've published for Tin Can API. The AMP will send the information back to your LMS. This is documented a bit further here. What actually gets set will also depend on the completion settings you use.
If you don't choose to use the Mobile player, you can publish for HTML5 (just unselect the Articulate Mobile Player option) and then your users can access the course on the ipad in Mobile Safari or Chrome on Android, and again the LMS handles the tracking set up.
If a course has only been published for HTML5 and they're accessing it on an iOS device, they'll see the content directly in Mobile Safari. You also mentioned using Update 4 of Storyline 2, and we'd recommend using the latest update and iOS and/or using the Updater previously mentioned to fix previous courses that users are having difficulty accessing on the latest iOS.
I'm working on a managed workstation that runs Windows 7 and now IE11. My Storyline is a couple of updates behind (I'm on Update 4), and I'm now noticing with IE11, I can't see my content. are there fixes in any of the three updates I'm missing that would fix my problem? I'm including a screen shot of what my player window looks like. [I also tried the content on a computer that has IE8, and it worked just fine]
You can read about all of the New Features and Bug Fixes in Updates 5, 6, and 7 here. Many of these updates are really important, so we'd recommend installing the latest update as soon as you can. Thanks!
I haven't heard of anyone mention that they're using it directly in Cornerstone - have you reached out to your LMS team for any additional help or assistance? I'd defer to them for the most comprehensive information on how to do particular things within your LMS.
Thanks Ashley. I posted a request to the Cornerstone boards, too :-) I usually get a quicker response from this group, though, so figured I'd give it a shot.
I'd post your question here too-Everything we know about Cornerstone on Demand and Articulate Storyline. It's a whole discussion board of Cornerstone users. I know your question is specifically about the Updater instead of Storyline, but there may be someone there who can help you with the Updater.
Good luck! I have never used the Updater with Cornerstone, so I am curious about how this turns out!
Thanks Leslie! Sorry, I should have gave more details. I guess the main thing i'm checking was if the new iOS update caused any issues with Presenters HTML5 scorm packages? We have a student in our LMS that is having issues loading the packages on iPad with iOS 9.1. The packages worked for me yesterday, but I was on iOS 8, so I went ahead and updated to 9.1 and now they wont load. I'm going to check it out on scorm.com now... Thank you for your help!!
You may find that slide content is missing when you view Articulate Studio '13 HTML5 output on iOS 9 iPads and iPhones. We added support for iOS 9 in Update 7 for Studio '13. See this article for details on how to update your Studio '13 software and your published courses.
The link that you shared to a previous issue was for SL1 2 years ago?
Reply: Yes, it was... that's why I was asking if it ever got resolved.
What do you mean by "HTML5 published output files that would not properly synch if the audio file(s) are too long"?
Reply: The audio incorrectly synchs to the animations wherein the synch continually delays when you play the slide (please note this also happens while I'm working in SL2U7 itself). I've actually had to instead revert to creating entire slide animations in AfterEffects instead in order for the synching to work at all.
79 Replies
Russ,
Thanks for the info. Did you happen to use the Articulate Updater feature to update directly on your LMS I presume?
Do you know if you had to republish the courses first though for those done in SL1?
Do you know if it works on TinCan pubs?
Hi Gem,
It should work on any elements you have already published and if you need to use the FTP method as Russ mentioned you'll want to follow the steps here at the bottom of the article.
As for the courses from SL1 - if you had upgraded them into SL2, you don't need to do any republishing from SL1 - just upgraded the SL2 version as described.
You can also see the Articulate updater will work across products as shown here:
Studio '13
Storyline 1
Please let us know if you run into any issues using the updater and if there is anything else we can assist with.
We've had courses still in our LMS from when we only used SL1 which are not converted ever pubbed in SL2. Do we need to first repub these out of SL2 U4 or U7 and reupload them so the Articulate Updater works or can we leave them alone and scan with the Articulate Updater as is currently uploaded in our LMS?
If an LMS uses iFrames, is my interpretation of this correct? Does this mean that the Articulate Updater cannot therefore be used via updating on the LMS site because each course's pubbed set of files need the below manipulation of code manually???
"How to Launch iFrame Courses in the Articulate Mobile Player in iOS 9Some learning management systems use iFrames to display courses, and iFrame content may not launch as exptected in iOS 9. For example, nothing may happen when you tap the Launch button for a Storyline course. Here's how to fix it:
After publishing with the latest Storyline update installed or using the Articulate Updater to scan and update your published files, go to the folder that contains your published course and open the amplaunch.html file in a text editor, such as Notepad.
Find this line of text:
<a id="launch" href="#" class="button">Launch</a>
And replace it with this text:
<a id="launch" href="#" class="button" target="_top">Launch</a>
Save and close amplaunch.html.
Zip your published files and upload the zip file to your LMS."
Shouldn't this be already an executable code within the Articulate Updater already?
Greetings, Gem.
Unfortunately, iFrame content may not launch as expected in iOS 9, and if you find that to be the case with your LMS, you can use the code change above to fix it.
To be more specific, the recommended code change you've referenced is only necessary if you find that the Launch button on the Articulate Mobile Player (AMP) launch page doesn't work with a single tap (although you can still tap the Open button on the AMP banner). This code change just allows the Launch button to work.
We'll try to address this in future versions of Storyline, but for now, the sequence is:
Please let us know if you need anything else, and have a great day!
Thanks for clarifying, Justin...
Which brings me to my next few questions:
Hello again, Gem.
Please let us know if you have any other questions.
Thanks! Very clear now. Your reply helps tremendously!
One last thing for now. Can you please tell me if it is the downloaded AMP that sends the course completion tracking info to our LMS or not? And if not, then what technology and what actually gets sent to our LMS as tracked/completed. The reason I ask is when I pub, my LMS says they don't need me to check both the "Use Articulate Mobile Player for iOS or Android" nor the "Allow downloading for offline viewing."
I know that SL2 U7 will always prompt to download that AMP on iOS so that covers whether or not the app is on there or not. I know that SL2 U4 on iOS 8 doesn't.
Hi Gem,
If you have published for AMP and you need to track in your LMS, you'll likely need to ensure you've published for Tin Can API. The AMP will send the information back to your LMS. This is documented a bit further here. What actually gets set will also depend on the completion settings you use.
If you don't choose to use the Mobile player, you can publish for HTML5 (just unselect the Articulate Mobile Player option) and then your users can access the course on the ipad in Mobile Safari or Chrome on Android, and again the LMS handles the tracking set up.
If a course has only been published for HTML5 and they're accessing it on an iOS device, they'll see the content directly in Mobile Safari. You also mentioned using Update 4 of Storyline 2, and we'd recommend using the latest update and iOS and/or using the Updater previously mentioned to fix previous courses that users are having difficulty accessing on the latest iOS.
Good news, thanks for the update Articulate.
I'm working on a managed workstation that runs Windows 7 and now IE11. My Storyline is a couple of updates behind (I'm on Update 4), and I'm now noticing with IE11, I can't see my content. are there fixes in any of the three updates I'm missing that would fix my problem? I'm including a screen shot of what my player window looks like. [I also tried the content on a computer that has IE8, and it worked just fine]
Good Morning, Annie.
You can read about all of the New Features and Bug Fixes in Updates 5, 6, and 7 here. Many of these updates are really important, so we'd recommend installing the latest update as soon as you can. Thanks!
Has anyone used Updater with Cornerstone On-Demand? I'm having trouble finding our LO's via FTP. Hoping someone here might provide some tips.
Hi James,
I haven't heard of anyone mention that they're using it directly in Cornerstone - have you reached out to your LMS team for any additional help or assistance? I'd defer to them for the most comprehensive information on how to do particular things within your LMS.
Thanks Ashley. I posted a request to the Cornerstone boards, too :-) I usually get a quicker response from this group, though, so figured I'd give it a shot.
Hi, James!
I'd post your question here too-Everything we know about Cornerstone on Demand and Articulate Storyline. It's a whole discussion board of Cornerstone users. I know your question is specifically about the Updater instead of Storyline, but there may be someone there who can help you with the Updater.
Good luck! I have never used the Updater with Cornerstone, so I am curious about how this turns out!
-Rachel
Does this affect Articulate Presenter 13 also?
Hi Adrian!
Thanks Leslie! Sorry, I should have gave more details. I guess the main thing i'm checking was if the new iOS update caused any issues with Presenters HTML5 scorm packages? We have a student in our LMS that is having issues loading the packages on iPad with iOS 9.1. The packages worked for me yesterday, but I was on iOS 8, so I went ahead and updated to 9.1 and now they wont load. I'm going to check it out on scorm.com now... Thank you for your help!!
Yes Adrian.
Ok. Thank you for the info Leslie!!
Thanks for the reply. I just read on a post pertaining to a past known issue wherein HTML5 published output files that would not properly synch if the audio file(s) are too long: https://community.articulate.com/discussions/articulate-storyline/html5-specific-issues-animation-sync-and-load-times
The post referred the fix to this bug was in Update 5 but I have users reporting it is still happening.
Comparing notes... any other instances?
Hi Gem!
The link that you shared to a previous issue was for SL1 2 years ago?
What do you mean by "HTML5 published output files that would not properly synch if the audio file(s) are too long"?
The link that you shared to a previous issue was for SL1 2 years ago?
Reply: Yes, it was... that's why I was asking if it ever got resolved.
What do you mean by "HTML5 published output files that would not properly synch if the audio file(s) are too long"?
Reply: The audio incorrectly synchs to the animations wherein the synch continually delays when you play the slide (please note this also happens while I'm working in SL2U7 itself). I've actually had to instead revert to creating entire slide animations in AfterEffects instead in order for the synching to work at all.
This discussion is closed. You can start a new discussion or contact Articulate Support.