We just created a course in Storyline where there are multiple slides under one section heading in the TOC. To keep the TOC looking cleaner, only the main slide in that "section" is displayed.
However, what we've found is that if a user "double-clicks" the next button, they can essentially skip several slides instead of going to the next slide. If the user does a "single-click" everything is fine.
Hi, Lisa -- Thanks for reaching out with your question! May I ask if you are seeing the same behavior when you are testing your course in the intended environment? And would it be possible for you to share your file so that we can take a closer look and do some testing for you on our end perhaps?
Hi, Lisa -- Thanks for your response and yes, you are welcome to use this form to submit your file for private review. I'll check it out as soon as possible and will be in touch with my findings. :)
Hi, Lisa -- Apologies for my delay in response, but I did want to let you know your file has been received and will be reviewed/tested momentarily. I will reply via the email address we have on file for you with my results as soon as possible.
When using restricted navigation, with the Next/Prev button option selected, double clicking on the next button when it is enabled will jump ahead 2 screens. Is there any resolution or workaround for this?
I'm having the same issue as Paul--in restricted navigation, a user can move backward or forward two slides when they double click Prev or Next. Any updates on this case?
I reviewed the previous cases and there appeared to be different solutions for both. This may be more of a case by case scenario. To offer a more tailored solution, I am more than happy to review your file! You can share it publicly here, or send it to me privately by uploading it here. I'll share my findings and delete it when I'm done troubleshooting!
My case is not resolved but I have found the following conditions frequently produce the result: Restricted navigation with Prev/Next enabled on modern player (HTML5 output obviously) in a course with content that was imported from PowerPoint. I was NOT successful when trying to reproduce this error with a plain vanilla powerpoint sample, but my guess is that it may be related to the time it takes to make a transition or execute an action or trigger - it only happens if the double click is quite rapid, before the NEXT button becomes disabled.
Thanks for the info, Paul. We definitely have some similarities in our course set-ups. We use:
Restricted navigation Restricted PREV/NEXT Modern Player We never import from PowerPoint. We also incorporate slides that have a variable preventing the user from progressing to the next slide until a certain action flips the variable. When I try double-clicking and the next slide is constrained by a variable, I see the next (correct) slide load, but with our warning message displayed, which tells the user they must complete an action. That message displays when the user tried to click next, which of course they should not even be able to do with restricted navigation, as the slide has not completed (and therefore the next button should not be active).
I'm not sure if any of that info will help you, but thought I'd put it out there. Back before restricted navigation was introduced to Storyline, we used to restrict the next button with a variable on every slide. This could probably still be used as a work-around to this problem, but what a pain!
Thanks for the info Rena, We have VO on every screen and use the feature which prevents the user from dragging the seekbar before the timeline is complete. It seems to me that there is some action or script activity or transition that occurs on screen load before the next button is disabled, which allows the second click if it is done quickly enough, to work. I have not seen it happen with content that is not originally imported from powerpoint.
Interesting. We don't use the seekbar, and we don't import from PowerPoint. I think your assessment of what's happening on the back-end is correct; it certainly tallies with what I see on our courses.
You can use a true/false variable that flips to true once the timeline completes. Then add a condition to the "Next" trigger that the variable must be true. However, this is a huge pain to have to do on each slide. I wish Articulate would just fix the problem.
Thanks for reaching out and sharing that you're runninginto a similar issue.
I took a look a the support cases that we worked on with some of the above users and it looks like the issue was file specific in each scenario (due to: importing from PowerPoint, corrupt Player) and our team was unable to replicate the behavior in a new file.
I don't have a solution to share with you at this time, but we'd be happy to investigate with you.
With your permission, I'd like you to share your project file with our support engineers to investigate what's happening. You can share it privately by uploading it here. It will be deleted when troubleshooting is complete.
I am running into a very similar issue. I have voiceover and media on almost every slide of my course, and when taking the course on an iPad (Chrome or Safari), if I time the clicks just right, I can jump ahead several slides at a time. The navigation in the course (Next/Previous) is restricted in the menu.
It seems like if the next slide hasn't loaded all the way, and there's just a little delay from when the Next button becomes active on the current slide to when the next slide loads and locks the Next button, I can get in there and keep jumping forward.
I'm running v3.46.23620.0. This is also happening on the desktop, though it's slightly harder to replicate, but most of our students are using iPads.
Thank you for sharing these details with our team! I've looked at other cases and it looks like this is an issue with the Player in the course. Can you try importing your project into a new project? If you've customized the player, you can export the Player and save the .XML file to your local drive. After importing the course, head over to the Player and import the custom player.
I'm happy to return to this discussion with an update! We justreleased Storyline 360 Update 52, and in it, you’ll find a fix for the bug you encountered where:
Rapidly Clicking the Next button on an iPad While the Next Slide Loads Allows the Learner to Skip Slides on a Restricted Navigation Course.
22 Replies
Hi, Lisa -- Thanks for reaching out with your question! May I ask if you are seeing the same behavior when you are testing your course in the intended environment? And would it be possible for you to share your file so that we can take a closer look and do some testing for you on our end perhaps?
Hi Christie,
Yes, it happens even in the intended environment -- Traincaster.
Is there a way I could privately share the file with you?
Lisa
Hi, Lisa -- Thanks for your response and yes, you are welcome to use this form to submit your file for private review. I'll check it out as soon as possible and will be in touch with my findings. :)
Hi, Lisa -- Apologies for my delay in response, but I did want to let you know your file has been received and will be reviewed/tested momentarily. I will reply via the email address we have on file for you with my results as soon as possible.
great. thank you so much for your help!
-lisa
When using restricted navigation, with the Next/Prev button option selected, double clicking on the next button when it is enabled will jump ahead 2 screens. Is there any resolution or workaround for this?
Hi Paul,
Thanks for reaching out! I see you have a case open, and my team is looking into it. Be on the lookout for a response soon.
You're in good hands, and I'll follow along as the case progresses!
Hi Ren,
I'm having the same issue as Paul--in restricted navigation, a user can move backward or forward two slides when they double click Prev or Next. Any updates on this case?
Hi Kate,
I reviewed the previous cases and there appeared to be different solutions for both. This may be more of a case by case scenario. To offer a more tailored solution, I am more than happy to review your file! You can share it publicly here, or send it to me privately by uploading it here. I'll share my findings and delete it when I'm done troubleshooting!
Sounds good, thanks Vincent--I've uploaded my project privately.
I am also experiencing this on PC. We used to have this problem on mobile, but it was fixed (https://community.articulate.com/discussions/articulate-storyline/able-to-break-restricted-menu-on-mobile).
My case is not resolved but I have found the following conditions frequently produce the result: Restricted navigation with Prev/Next enabled on modern player (HTML5 output obviously) in a course with content that was imported from PowerPoint. I was NOT successful when trying to reproduce this error with a plain vanilla powerpoint sample, but my guess is that it may be related to the time it takes to make a transition or execute an action or trigger - it only happens if the double click is quite rapid, before the NEXT button becomes disabled.
This post was removed by the author
Thanks for the info, Paul. We definitely have some similarities in our course set-ups. We use:
Restricted navigation
Restricted PREV/NEXT
Modern Player
We never import from PowerPoint. We also incorporate slides that have a variable preventing the user from progressing to the next slide until a certain action flips the variable. When I try double-clicking and the next slide is constrained by a variable, I see the next (correct) slide load, but with our warning message displayed, which tells the user they must complete an action. That message displays when the user tried to click next, which of course they should not even be able to do with restricted navigation, as the slide has not completed (and therefore the next button should not be active).
I'm not sure if any of that info will help you, but thought I'd put it out there. Back before restricted navigation was introduced to Storyline, we used to restrict the next button with a variable on every slide. This could probably still be used as a work-around to this problem, but what a pain!
Thanks for the info Rena, We have VO on every screen and use the feature which prevents the user from dragging the seekbar before the timeline is complete. It seems to me that there is some action or script activity or transition that occurs on screen load before the next button is disabled, which allows the second click if it is done quickly enough, to work. I have not seen it happen with content that is not originally imported from powerpoint.
Interesting. We don't use the seekbar, and we don't import from PowerPoint. I think your assessment of what's happening on the back-end is correct; it certainly tallies with what I see on our courses.
We're experiencing the same problem. Did anyone ever find a resolution?
You can use a true/false variable that flips to true once the timeline completes. Then add a condition to the "Next" trigger that the variable must be true. However, this is a huge pain to have to do on each slide. I wish Articulate would just fix the problem.
Same problem. Does anyone have solution?
Hi Prathmesh and welcome to E-Learning Heroes 😊
Thanks for reaching out and sharing that you're runninginto a similar issue.
I took a look a the support cases that we worked on with some of the above users and it looks like the issue was file specific in each scenario (due to: importing from PowerPoint, corrupt Player) and our team was unable to replicate the behavior in a new file.
I don't have a solution to share with you at this time, but we'd be happy to investigate with you.
With your permission, I'd like you to share your project file with our support engineers to investigate what's happening. You can share it privately by uploading it here. It will be deleted when troubleshooting is complete.
I am running into a very similar issue. I have voiceover and media on almost every slide of my course, and when taking the course on an iPad (Chrome or Safari), if I time the clicks just right, I can jump ahead several slides at a time. The navigation in the course (Next/Previous) is restricted in the menu.
It seems like if the next slide hasn't loaded all the way, and there's just a little delay from when the Next button becomes active on the current slide to when the next slide loads and locks the Next button, I can get in there and keep jumping forward.
I'm running v3.46.23620.0. This is also happening on the desktop, though it's slightly harder to replicate, but most of our students are using iPads.
Hi Jordan!
Thank you for sharing these details with our team! I've looked at other cases and it looks like this is an issue with the Player in the course. Can you try importing your project into a new project? If you've customized the player, you can export the Player and save the .XML file to your local drive. After importing the course, head over to the Player and import the custom player.
Hello Jordan,
I'm happy to return to this discussion with an update! We just released Storyline 360 Update 52, and in it, you’ll find a fix for the bug you encountered where:
Rapidly Clicking the Next button on an iPad While the Next Slide Loads Allows the Learner to Skip Slides on a Restricted Navigation Course.
Be sure to install the latest version of Storyline 360 to take advantage of all the recent features and fixes!
If this happens again, please let us know! Or you can work directly with our support engineers here.