I created a project yesterday in SL3 and it wouldn't fully open in chrome; it just hangs at the opening spinning wheel. The same published content opens fine in MS Edge. I'm publishing to HTML5 with flash back up and also tried publishing to just HTML5.
When I open the file through SL360 and publish, everything plays fine in both Chrome and Edge. I also recreated the file in SL2 and it opens and plays fine in both Chrome and Edge. The issue only occurs with my SL3 file and only in Chrome.
When you're viewing the Storyline 3 content in Chrome, are you viewing it locally? This is an issue with the latest Chrome update and our team is working on a fix in Storyline 3 (we already rolled one out to Storyline 360) so I'll let you know here as soon as that's ready!
Yes, I am viewing it locally. Being able to do so is pretty critical as it is the closest thing to "Preview" for any coursework involving JavaScript. Looking forward to the update!
Totally understand Owen, and I'll keep you posted. In the meantime, have you looked at uploading your published content to Tempshare? That would allow for an easy testing environment where those courses will also disappear after 10 days.
This is a huge concern for us. I've never had any problems with this before today. This is something very new. I cannot view (locally) a published file in Chrome. I can in IE, but not Chrome. If I click on the Story_flash file (in the published files)- it plays. I've disabled pop up blockers and that hasn't helped. PS running SL 360 and the most recent version of Chrome -Version 64.0.3282.140 (Official Build) (64-bit). Suggestions anyone?
When you Publish are you publishing for Flash/HTML5?
If you want to open in a web browser I suggest Publishing for just HTML5 in your settings. Flash is more or less dying and not being supported by a lot of browsers.
I'm currently in a similar situation in SL3 but with the recent Chrome update it will not let me load the story_html5.html file in Chrome. I'm under the impression however, that a fix was made for SL360.
The latest version of Chrome blocks the loading of local files. A good workaround for this is to enable IIS on your machine and place your Storyline web output files in a test folder that you create in C:/inetpub/wwwroot/test for testing at http://localhost/test/story.html
I've created some tutorial videos to outline this process. You may need to navigate to Programs and Features slightly differently on newer versions of Windows 10 -- the Start menu now has an option called Apps and Features where you can launch the classic Programs and Features window as a related setting.
Hi David, Thanks for the quick response. We publish as HTML5/Flash (with the fallback) never had an issue. I was publishing today as a "test" to the WEB but also tried to the LMS when I noticed the issue. Thanks.
Ok. Well I'll try to give my input from my experience in what we're Publishing for. We're offering teachers 3 methods for viewing our Courses.
Online/Web -- We publish as HTML5 Only because our server does not support Flash (Link opens the "story_html5.html" file.
Locally to run on their own computer/SmartBoards -- We Publish for CD. Direct teachers to launch the "story_html5.html" file in Chrome.
Mobile -- We publish to HTML5/Flash and turn on AMP settings. Believe the file to launch is called "amplaunch.html"
Now this is my experience in SL3. I just installed 360 and publishing to all three formats and now opening the "story_html5.html" file in Chrome loads my courses like it should.
My recommendation is if you're publishing for Web and plan to use Chrome anyway I'd publish as HTML5 only and avoid trying to include flash or ever opening the story_flash file. I think Chrome will naturally put up a blocker telling you to activate the flash plug in if you want to open the file.
I thought this issue only occurred when viewing content from the local hard drive. Are you having the same loading problem when viewing the courses from your LMS? What is the exact problem you are having?
Only on Windows 10? Have you checked Chrome's developer console to see what errors are logged there while trying to load the course? Do you have a sample course file you can post here or a link to the course on your LMS?
Now I’m even more concerned. It’s not even working on the LMS? I was going to test tomorrow. I was having an issue on my local drive. I agree, this is a browser issue and for me, just started on Friday. We publish as Tincan HTML5/Flash fallback. We need a solution- and fast.
Sorry, Gillian. For my team, Publishing our course in SL3 and uploading to our LMS and viewing in Chrome has worked for us. Only if we Publish as HTML5 only because Flash is blocked on our firewall.
I have not tested on a Windows 10 machine yet however. So I apologize if the above didn't help. I did mention I downloaded the Trial Run of SL360 that seemed to fix my Chrome Local Playback issue although it created an enormous amount of other bugs in my course. So I don't think that is currently a solution I can run with.
So I am also still looking for a solution to this.
I'm sorry for the issues you ran into this weekend. Our team has seen with the recent Chrome updates that local playback of content does not work. This would only be for Storyline 3 or 360 content that you had published for Web or LMS and were playing back while housed locally such as on your C drive.
If you've uploaded your courses to the web server or LMS, the playback there should not be effected. If you are seeing issues once you upload to the intended environment as we recommend I'd look at testing outside your environment to narrow down where the issue is. For example:
For web published content you could use Amazon S3 or upload to Tempshare
For LMS published content, take a look at testing in SCORM Cloud.
If you're still running into issues after testing in any of those other environments, please let us know. Our Support team is around 24/7 here (a smaller group on weekends!) but they are happy to help and will keep an eye on if this is specific to one course/LMS or a larger issue across all users that needs to alert our broader team.
Update: During testing, my coworker published to the (Web) using our usual settings, HTML5/Flash (fallback) and was able to open and view on her desktop- in Chrome and IE- with no issues. This makes me think that possibly something changed with my security settings.
Additionally, I had an update – or two waiting and once I updated 360 (v3.12.14647.0), it worked as it always did. We are still testing on the LMS (Absorb). Thanks to all for your suggestions/ feedback.
47 Replies
Hi Owen,
When you're viewing the Storyline 3 content in Chrome, are you viewing it locally? This is an issue with the latest Chrome update and our team is working on a fix in Storyline 3 (we already rolled one out to Storyline 360) so I'll let you know here as soon as that's ready!
Yes, I am viewing it locally. Being able to do so is pretty critical as it is the closest thing to "Preview" for any coursework involving JavaScript. Looking forward to the update!
Totally understand Owen, and I'll keep you posted. In the meantime, have you looked at uploading your published content to Tempshare? That would allow for an easy testing environment where those courses will also disappear after 10 days.
This post was removed by the author
This is an urgent issue for us as well.
This is a huge concern for us. I've never had any problems with this before today. This is something very new. I cannot view (locally) a published file in Chrome. I can in IE, but not Chrome. If I click on the Story_flash file (in the published files)- it plays. I've disabled pop up blockers and that hasn't helped. PS running SL 360 and the most recent version of Chrome -Version 64.0.3282.140 (Official Build) (64-bit). Suggestions anyone?
Hi Karyn,
When you Publish are you publishing for Flash/HTML5?
If you want to open in a web browser I suggest Publishing for just HTML5 in your settings. Flash is more or less dying and not being supported by a lot of browsers.
I'm currently in a similar situation in SL3 but with the recent Chrome update it will not let me load the story_html5.html file in Chrome. I'm under the impression however, that a fix was made for SL360.
Are you Publishing for CD or Publishing for Web?
The latest version of Chrome blocks the loading of local files. A good workaround for this is to enable IIS on your machine and place your Storyline web output files in a test folder that you create in C:/inetpub/wwwroot/test for testing at http://localhost/test/story.html
I've created some tutorial videos to outline this process. You may need to navigate to Programs and Features slightly differently on newer versions of Windows 10 -- the Start menu now has an option called Apps and Features where you can launch the classic Programs and Features window as a related setting.
Here's a screenshot of the Apps and Features window. You can launch Programs and Features from the right-hand side under the Related settings header.
Hi again Karyn,
I downloaded the trial Version of 360 and published my files again the the Chrome bug is fixed as far as I can tell.
If you need a hand let me know and I can try to help sort out your issue.
Hi David, Thanks for the quick response. We publish as HTML5/Flash (with the fallback) never had an issue. I was publishing today as a "test" to the WEB but also tried to the LMS when I noticed the issue. Thanks.
Ok. Well I'll try to give my input from my experience in what we're Publishing for. We're offering teachers 3 methods for viewing our Courses.
Online/Web -- We publish as HTML5 Only because our server does not support Flash (Link opens the "story_html5.html" file.
Locally to run on their own computer/SmartBoards -- We Publish for CD. Direct teachers to launch the "story_html5.html" file in Chrome.
Mobile -- We publish to HTML5/Flash and turn on AMP settings. Believe the file to launch is called "amplaunch.html"
Now this is my experience in SL3. I just installed 360 and publishing to all three formats and now opening the "story_html5.html" file in Chrome loads my courses like it should.
My recommendation is if you're publishing for Web and plan to use Chrome anyway I'd publish as HTML5 only and avoid trying to include flash or ever opening the story_flash file. I think Chrome will naturally put up a blocker telling you to activate the flash plug in if you want to open the file.
Hope that helps!
This post was removed by the author
This post was removed by the author
I thought this issue only occurred when viewing content from the local hard drive. Are you having the same loading problem when viewing the courses from your LMS? What is the exact problem you are having?
This post was removed by the author
Only on Windows 10? Have you checked Chrome's developer console to see what errors are logged there while trying to load the course? Do you have a sample course file you can post here or a link to the course on your LMS?
Now I’m even more concerned. It’s not even working on the LMS? I was going to test tomorrow. I was having an issue on my local drive. I agree, this is a browser issue and for me, just started on Friday. We publish as Tincan HTML5/Flash fallback. We need a solution- and fast.
Sorry, Gillian. For my team, Publishing our course in SL3 and uploading to our LMS and viewing in Chrome has worked for us. Only if we Publish as HTML5 only because Flash is blocked on our firewall.
I have not tested on a Windows 10 machine yet however. So I apologize if the above didn't help. I did mention I downloaded the Trial Run of SL360 that seemed to fix my Chrome Local Playback issue although it created an enormous amount of other bugs in my course. So I don't think that is currently a solution I can run with.
So I am also still looking for a solution to this.
Hi all,
I'm sorry for the issues you ran into this weekend. Our team has seen with the recent Chrome updates that local playback of content does not work. This would only be for Storyline 3 or 360 content that you had published for Web or LMS and were playing back while housed locally such as on your C drive.
If you've uploaded your courses to the web server or LMS, the playback there should not be effected. If you are seeing issues once you upload to the intended environment as we recommend I'd look at testing outside your environment to narrow down where the issue is. For example:
If you're still running into issues after testing in any of those other environments, please let us know. Our Support team is around 24/7 here (a smaller group on weekends!) but they are happy to help and will keep an eye on if this is specific to one course/LMS or a larger issue across all users that needs to alert our broader team.
This post was removed by the author
Thanks Gillian - I've added these notes to your case.
We are unable to view html5 SL3 presentations uploaded into Canvas on Chrome.
This post was removed by the author
Hi All:
Update:
During testing, my coworker published to the (Web) using our usual settings, HTML5/Flash (fallback) and was able to open and view on her desktop- in Chrome and IE- with no issues. This makes me think that possibly something changed with my security settings.
Additionally, I had an update – or two waiting and once I updated 360 (v3.12.14647.0), it worked as it always did. We are still testing on the LMS (Absorb). Thanks to all for your suggestions/ feedback.