I have a serious problem with a Storyline 2 project. I'm using the default player. On every screen, the "Next" button won't work until the timeline for the slide completes.
Myself nor anyone on my team can figure out what's causing it. We don't have any triggers setup to do this.
So, if I want to lockdown the overall navigation, it also locks down each individual screen? That's epically moronic. Thanks. Guess I have a lot of new work to do.
This just saved me some serious tears! Could not figure out why the Next button wouldn't work until timeline ended! Thought locking the menu just kept users from skipping around in the slides!
I have to agree with Adam. This is a difference between SL 1 and 2. It's causing me a lot of trouble with upgraded projects. There should be at least a slide option "Enable player navigation before the timeline ends".
In Articulate Storyline 1, restricted and locked navigation settings only affected the menu. In contrast, the navigation settings in Articulate Storyline 2 affect both the menu and the player buttons, making it much easier to control the overall navigation for your course. To learn how to restrict or lock navigation in Storyline 2, see this article.
We have gotten feedback that users would like more options. You are welcome to share your thoughts with our product development team here as well.
I can understand why, if menu navigation is restricted, that the next button would not work on a slide until the slide has been completed. But upon completion of the slide, the next button should work, especially when revisiting that slide. Currently, if the completed slide is revisited, the next button still doesn't work. Also, if the next button isn't going to work on a slide by default in a menu-restricted course, the next button should at least appear disabled. Otherwise, it just appears to the learner that the next button is broken. (I'm aware I can disable the next button, but that doesn't really solve the problem.)
Did you also check the slide properties to ensure that they're not resetting the timeline on a revisit? If so, Storyline is resetting the whole slide including the timeline meaning that the entire slide is reset which would also reset the behavior of the next button.
If anyone is still struggling with this - my workaround is just to add a new "next" button, not using the built in one. Now the learner can click on this next button and move forward before the timeline ends.
Thanks for sharing that idea here - we've seen a few examples of ways around the locked/restricted navigation, but it's always good to have a couple more in the idea bank.
Hey there, Phil. If you need a hand, let us know! I wasn't sure which version of Storyline you're using, but we made some changes to navigation restriction options in Storyline 360 based on users needing tighter control over individual slide behavior.
15 Replies
Check the menu under player and make sure it is set to free and not restricted or locked
Hi Adam! Looks like Phil is helping you out here and it does sound like a navigation issue. Here is a tutorial if helpful.
So, if I want to lockdown the overall navigation, it also locks down each individual screen? That's epically moronic. Thanks. Guess I have a lot of new work to do.
This just saved me some serious tears! Could not figure out why the Next button wouldn't work until timeline ended! Thought locking the menu just kept users from skipping around in the slides!
Glad that this was able to help you out as well Brande :)
Thank you for this information!!!
We appreciate you letting us know you found the help you needed, Isabelle! :)
I have to agree with Adam. This is a difference between SL 1 and 2. It's causing me a lot of trouble with upgraded projects. There should be at least a slide option "Enable player navigation before the timeline ends".
I can't stop thinking this is not a bug.
Hi Lars!
I can understand why, if menu navigation is restricted, that the next button would not work on a slide until the slide has been completed. But upon completion of the slide, the next button should work, especially when revisiting that slide. Currently, if the completed slide is revisited, the next button still doesn't work. Also, if the next button isn't going to work on a slide by default in a menu-restricted course, the next button should at least appear disabled. Otherwise, it just appears to the learner that the next button is broken. (I'm aware I can disable the next button, but that doesn't really solve the problem.)
Hi James,
Did you also check the slide properties to ensure that they're not resetting the timeline on a revisit? If so, Storyline is resetting the whole slide including the timeline meaning that the entire slide is reset which would also reset the behavior of the next button.
If anyone is still struggling with this - my workaround is just to add a new "next" button, not using the built in one. Now the learner can click on this next button and move forward before the timeline ends.
Hi Kristin,
Thanks for sharing that idea here - we've seen a few examples of ways around the locked/restricted navigation, but it's always good to have a couple more in the idea bank.
This one get's me every time ;-/
Hey there, Phil. If you need a hand, let us know! I wasn't sure which version of Storyline you're using, but we made some changes to navigation restriction options in Storyline 360 based on users needing tighter control over individual slide behavior.
This discussion is closed. You can start a new discussion or contact Articulate Support.