I've created multiple courses in Storyline 2 using the disabled state for the Next button to restrict the learner from clicking through the course. So far it's been working great. Recently a particularly crafty individual figured out a way to bypass this feature. Is it possible to close this loophole in future builds of Storyline?
I didn't want to post the actual workaround in an open forum so you'll have to contact me directly and I can let you know how they did it..
Well, I can think of two ways to bypass a disabled next button depending on how you have configured Storyline.
1. If you are using the player menu, users will be able to open the menu and select the last slide in the menu effectively bypassing the course. To get around this you have to set the menu to settings to either restricted or locked. This will ensure the learner has to wait until the timeline on the slide ends before proceeding to the next slide.
2. If you have set up a trigger to change the state of the next button to normal when the timeline ends AND you have the seekbar enabled - you will have to change the seekbar to read only; otherwise, the learner will be able to drag the seekbar to the end of the timeline which will enable the next button.
If your learners have come up with another way - then I am intrigued.
I took a look and was able to re-create the issue you described here. It is something our QA Team is aware of and I will share this thread with them for user awareness as well as my sample file.
7 Replies
Well, I can think of two ways to bypass a disabled next button depending on how you have configured Storyline.
1. If you are using the player menu, users will be able to open the menu and select the last slide in the menu effectively bypassing the course. To get around this you have to set the menu to settings to either restricted or locked. This will ensure the learner has to wait until the timeline on the slide ends before proceeding to the next slide.
2. If you have set up a trigger to change the state of the next button to normal when the timeline ends AND you have the seekbar enabled - you will have to change the seekbar to read only; otherwise, the learner will be able to drag the seekbar to the end of the timeline which will enable the next button.
If your learners have come up with another way - then I am intrigued.
Don't use a menu or the seekbar...
Try this: Shift-Tab through the slide till there's a yellow box around the
disabled next button then hit 'enter'
Thanks
Brian Steers
Implementation and Product Development
SafeStart a Div. of Electrolab Ltd.
(800)267-7482 ext 312
brian@electrolab.ca
Hi Brian!
Thanks for popping in to share. I'm going to take a look at that.
Please note that replying to the forums via e-mail attaches your signature. You are welcome to pop in and edit if needed.
Setting the state of NEXT to hidden prevents this.
Yet another reason to hide navigation controls that don't function.
That's a good one. I think Walt is right. You have to hide the button instead of disabling it.
Thanks Brian for posting. I use the disabled state to on my custom buttons, too. I'll have to rethink. Thanks for tip Walt.
Hi Brian!
I took a look and was able to re-create the issue you described here. It is something our QA Team is aware of and I will share this thread with them for user awareness as well as my sample file.
I will update when applicable.
Thank you.
This discussion is closed. You can start a new discussion or contact Articulate Support.