I'm pleased to announce that Storyline 2 Update 5 is now available. This update makes it easier to create accessible e-learning content, improves HTML5 performance, and of course squashes lots of bugs. Read all about it now (or just jump over to the update page).
I had the oddest thing happen after installing the update. When I opened up a module that I was working on before the update, the background of the Notes section of all my slides turned purple. It's a custom purple that I've been using in my module, but I definitely didn't apply it to my entire presentation. Anyone know how to switch it back to white with black text?
Yes, it seems so. I was using purple as the background color on my Menu and Resources tabs. If I change the color of the Menu background, I can correct it. If there's a way to use different colors for Notes and the tabs, definitely let me know. Otherwise, I'll make it work. Thanks for your quick response.
I may be misunderstanding, but according to the release notes what you're seeing is by design as a new feature.
"Added feature to show the player background color and the default notes color in the Storyline notes panel, so content authors can see how their notes will look in their published output."
Whoa, a massive update here with many HTML5 fixes I'm keen to try out. You have been busy!
However, please, please stop adding new 'Flash only' features, the disparity between Flash and HTML5 authoring in storyline is a major pain pointfor me. Especially since we can only preview in Flash.
Yeah it's been requested and discussed a few times. Unfortunately everyone is moving away from Flash these days and it's becoming harder to support. Of course HTML5 has it's own share of issues too...
Can someone please help me out with figuring out these new accessibility features, how they work, and how I can test them?
I also noticed now that when tabbing around a published file that the Enter key no longer seems to work. I used to be able to tab to the NEXT button and hit the Enter key and the slide would advance. Now it doesn't.
Edit: I should clarify to say that the tab functionality does not seem to function as expected when running a published output file locally. It does seem to work when I upload it to Articulate Tempshare.
I took am curious about the accessibility features. Still not support captions without a major labor intensive work around which is highly disappointing.
We always recommend testing the published output within the intended environment as mentioned here. I haven't tested all the features of SL2 Update 5 yet myself, but have you tried the enter key vs. the spacebar? Was this while viewing the published output locally or the preview?
Thanks David for the update and glad everything worked in Tempshare. I don't believe all the tutorials were linked as a part of the initial announcement, so thanks for sharing that here for other users who may be looking for it.
This new patch seems to have broken all my right-click interactions. I see from previous posts that right-click interactions have been tricky at best, but I haven't had a problem until now. The interaction is not working at all - in preview or publish mode. I've tried multiple browsers, with the same results.
I then gave the file to a co-worker who has not patched yet, and all the interactions worked fine. This leads me to believe its this patch.... HELP!
I'm sorry to hear about the issue you've run into. I haven't done the update myself yet, so if you'd like to share it here with us we're happy to check it and than I could also share it with my colleagues who have done Update 5 to see how that behaves for them as well. You mentioned you see it in preview/publish - and I'd also want to confirm that you were testing the published output within the intended publish environment.
I have tried to get the update and after it finishes 'running' the download, it comes up with an error code and says the download failed. Error code 80070652. I've tried from scratch at least 6 or 7 times. It goes through everything and seems to be downloading, and then I get the attached message. Anyone else had this problem or know what I might try? Thanks.
On a related sidenote, I notice that Articulate doesn't offer the ability to download previous builds. I understand the need for the most current version out there. Would there be any consideration for allowing access to earlier versions to help with rare instances like this?
208 Replies
Nice! Lots of good stuff here.
Thanks Brian.
Great work team!
Awesome update! Any tutorial videos in the works that cover how these new features work? If so, please let me know where I can access them. Thanks!
I had the oddest thing happen after installing the update. When I opened up a module that I was working on before the update, the background of the Notes section of all my slides turned purple. It's a custom purple that I've been using in my module, but I definitely didn't apply it to my entire presentation. Anyone know how to switch it back to white with black text?
W00t!
That's the oddest thing, Tina. Does it also affect the Notes background color in the sidebar during Preview or Publish?
Yes, it seems so. I was using purple as the background color on my Menu and Resources tabs. If I change the color of the Menu background, I can correct it. If there's a way to use different colors for Notes and the tabs, definitely let me know. Otherwise, I'll make it work. Thanks for your quick response.
I may be misunderstanding, but according to the release notes what you're seeing is by design as a new feature.
"Added feature to show the player background color and the default notes color in the Storyline notes panel, so content authors can see how their notes will look in their published output."
See all release notes here (the above is the 7th bullet): http://www.articulate.com/support/storyline-2/issues-addressed-in-the-latest-articulate-storyline-2-update/
Just read the release notes. I can't tell if I'm more excited about the WCAG 2.0 updates or all the bug fixes!
Whoa, a massive update here with many HTML5 fixes I'm keen to try out. You have been busy!
However, please, please stop adding new 'Flash only' features, the disparity between Flash and HTML5 authoring in storyline is a major pain pointfor me. Especially since we can only preview in Flash.
Good point Christian. Hadn't thought of that before but having the ability to Preview in HTML5 would be an excellent option.
Perhaps Storyline 2 Update 6 ?
Yeah it's been requested and discussed a few times. Unfortunately everyone is moving away from Flash these days and it's becoming harder to support. Of course HTML5 has it's own share of issues too...
Not to get into the Flash/HTML5 debate, but it'll be awhile yet before the world is "Flash Free".
Can someone please help me out with figuring out these new accessibility features, how they work, and how I can test them?
I also noticed now that when tabbing around a published file that the Enter key no longer seems to work. I used to be able to tab to the NEXT button and hit the Enter key and the slide would advance. Now it doesn't.
Edit: I should clarify to say that the tab functionality does not seem to function as expected when running a published output file locally. It does seem to work when I upload it to Articulate Tempshare.
I took am curious about the accessibility features. Still not support captions without a major labor intensive work around which is highly disappointing.
Hi David,
We always recommend testing the published output within the intended environment as mentioned here. I haven't tested all the features of SL2 Update 5 yet myself, but have you tried the enter key vs. the spacebar? Was this while viewing the published output locally or the preview?
Hey Ashley. The published output seemed to work OK when I uploaded it to Tempshare. It just would not work when I tested it locally off my hard drive.
I stumbled across a pretty good tutorial on the new accessibility features of Update five here -
https://community.articulate.com/series/articulate-storyline-2/articles/customizing-the-tab-order-of-slide-objects
Didn't see that mentioned in the original announcement, but maybe I missed something.
Thanks David for the update and glad everything worked in Tempshare. I don't believe all the tutorials were linked as a part of the initial announcement, so thanks for sharing that here for other users who may be looking for it.
This new patch seems to have broken all my right-click interactions. I see from previous posts that right-click interactions have been tricky at best, but I haven't had a problem until now. The interaction is not working at all - in preview or publish mode. I've tried multiple browsers, with the same results.
I then gave the file to a co-worker who has not patched yet, and all the interactions worked fine. This leads me to believe its this patch.... HELP!
Hi Joe,
I'm sorry to hear about the issue you've run into. I haven't done the update myself yet, so if you'd like to share it here with us we're happy to check it and than I could also share it with my colleagues who have done Update 5 to see how that behaves for them as well. You mentioned you see it in preview/publish - and I'd also want to confirm that you were testing the published output within the intended publish environment.
I have tried to get the update and after it finishes 'running' the download, it comes up with an error code and says the download failed. Error code 80070652. I've tried from scratch at least 6 or 7 times. It goes through everything and seems to be downloading, and then I get the attached message. Anyone else had this problem or know what I might try? Thanks.
Here you go...
I also tried just creating a new course with just the right click interaction, and got the same thing.
I've reverted back to Update 4, and the interaction works again.
Yes... I published to web, and dumped it onto our website to test.
See my note below for additional info.
On a related sidenote, I notice that Articulate doesn't offer the ability to download previous builds. I understand the need for the most current version out there. Would there be any consideration for allowing access to earlier versions to help with rare instances like this?
Hi Joe! You would need to work directly with our support team on this.
This discussion is closed. You can start a new discussion or contact Articulate Support.