Hi to everyone! I've published a course using StoryLine 360. Using Chrome to some users appears the attached screen ; a great play on a grey background. However, the screen is locked and it is not possible to continue with the lesson. What could be the problem?
Its not a video though Matthew. I get why if there was a video there that the PLAY button would appear.
This is before the course has even started playing the very first slide, (and there isnt even any video used anywhere in my course!)
Articulate seems to have packaged it up in a way that it believes it either is a video, or that the mobile interface is being adopted when run within the desktop browser.
Matthew shared the link on the Video autoplay in Chrome, but you'll see it's also the case for audio here. If you think it's something other than the Chrome update detailed there, submitting a case is a good step!
I see it came to our team last night - thanks! Someone will be in touch shortly, but it looks like you didn't share a copy of your course or a screenshot to demonstrate what you're seeing? That's always a helpful step and gives our team a bit more insight into what you're experiencing.
I'll send you the link to upload that information as a part of your case, so keep an eye out for an email from Support@articulate.com.
If your fix, or that article help - no worries, we can always close out the case.
Re: sharing files. Sorry, this is a bit of a bugbear with me as its the general response that anyone from Articulate seems to come back with.
Articulate has to understand that alot of people using their product are doing so for commerical reasons. We are under strict NDA and other binding legal contracts. With the new GDPR regulations coming into effect later this month for the EU, we are even more under scrutiny to adhere to a precise set of laws.
Sending out clients commerically sensitive work is just not an option.
It feels as if Articulate dont take reports of problems and bugs seriously until the Story file is submitted, but I hope they can change their policy to help out those of us who make a living as a Storyline developer!
Sorry, this is definitely not directed at you or any one individual, but towards Articulate as a company.
I understand if you're unable to share your course, or feel like it's an indication of our team not taking a report seriously, but it's the best way to demonstrate the problem and document a defect. It helps to confirm we're testing with the same exact setup and conditions to quickly replicate an issue and figure out next steps to troubleshoot and resolve it.
I saw Abel responded to your Support case too, and he also let me know that our team is looking into any other changes in this latest update that could be impacting course playback. We haven't heard yet that other browsers such as Firefox have implemented similar guidelines around autoplay, but I wouldn't be shocked if that's on their roadmap.
As far as GDPR, we're still understanding it and the implications, but I did share your thoughts here with our team who handles Security and Compliance. They're working through all the ways that this may impact our processes and workflow.
Please let me know if I can help with anything else.
Hey everybody. I'm excited to let you know that we just released update 17 for Storyline 360! It includes new features and fixes - check them all out here.
One of the fixes addresses an issue where in HTML5, the course does not automatically play in Firefox when audio or video is added to the first slide.
Here’s how you can update Storyline 360 to take advantage of everything the latest release has to offer. Let me know how you make out!
8 Replies
I got exactly the same thing and have reported it as a bug yesterday.
Heard nothing back though.
Infuriating!!
Its not a video though Matthew. I get why if there was a video there that the PLAY button would appear.
This is before the course has even started playing the very first slide, (and there isnt even any video used anywhere in my course!)
Articulate seems to have packaged it up in a way that it believes it either is a video, or that the mobile interface is being adopted when run within the desktop browser.
Thank mate.
It gets weirder as now Im going back to old courses, republishing them with latest version of SL360, and they dont have the play button.?!?!?!? Argh.
Im off to try loud shouting at the computer. That always helps. ;)
This post was removed by the author
This post was removed by the author
I might have found a fix...
https://community.articulate.com/discussions/articulate-storyline/important-a-fix-if-you-have-a-play-button-appearing-at-start-of-courses
Hi Andrew,
Matthew shared the link on the Video autoplay in Chrome, but you'll see it's also the case for audio here. If you think it's something other than the Chrome update detailed there, submitting a case is a good step!
I see it came to our team last night - thanks! Someone will be in touch shortly, but it looks like you didn't share a copy of your course or a screenshot to demonstrate what you're seeing? That's always a helpful step and gives our team a bit more insight into what you're experiencing.
I'll send you the link to upload that information as a part of your case, so keep an eye out for an email from Support@articulate.com.
If your fix, or that article help - no worries, we can always close out the case.
Hi Ashley.
Re: sharing files. Sorry, this is a bit of a bugbear with me as its the general response that anyone from Articulate seems to come back with.
Articulate has to understand that alot of people using their product are doing so for commerical reasons. We are under strict NDA and other binding legal contracts. With the new GDPR regulations coming into effect later this month for the EU, we are even more under scrutiny to adhere to a precise set of laws.
Sending out clients commerically sensitive work is just not an option.
It feels as if Articulate dont take reports of problems and bugs seriously until the Story file is submitted, but I hope they can change their policy to help out those of us who make a living as a Storyline developer!
Sorry, this is definitely not directed at you or any one individual, but towards Articulate as a company.
Hi Andrew,
I understand if you're unable to share your course, or feel like it's an indication of our team not taking a report seriously, but it's the best way to demonstrate the problem and document a defect. It helps to confirm we're testing with the same exact setup and conditions to quickly replicate an issue and figure out next steps to troubleshoot and resolve it.
I saw Abel responded to your Support case too, and he also let me know that our team is looking into any other changes in this latest update that could be impacting course playback. We haven't heard yet that other browsers such as Firefox have implemented similar guidelines around autoplay, but I wouldn't be shocked if that's on their roadmap.
As far as GDPR, we're still understanding it and the implications, but I did share your thoughts here with our team who handles Security and Compliance. They're working through all the ways that this may impact our processes and workflow.
Please let me know if I can help with anything else.
Hey everybody. I'm excited to let you know that we just released update 17 for Storyline 360! It includes new features and fixes - check them all out here.
One of the fixes addresses an issue where in HTML5, the course does not automatically play in Firefox when audio or video is added to the first slide.
Here’s how you can update Storyline 360 to take advantage of everything the latest release has to offer. Let me know how you make out!
This discussion is closed. You can start a new discussion or contact Articulate Support.