I have an issue where when users apply the back button (on the master templates) at some points in my module they get stuck in a loop (e.g They will just start going back and forth between 2 pages).
This has started happening since a 3rd party developed some navigation templates for my organisation and is usually around pages with quiz ineractions.
Are you able to look at the triggers associated with the "previous" button for your player on your master slide template - the default setting for previous is to return to the last slide seen - and therefore if you change the behavior you'll see the trigger within the trigger pane. You mentioned they're stuck in a loop because of the quiz slides, which likely didn't include a previous/next button on the first time through but a submit button? So are they revisiting the quiz slide and resuming it or seeing it reset to it's initial state?
It may help if we're able to take a look at this .story file so that we can see where the loop occurs and then any associated triggers.
It sounds like that may be contributing to it - but without seeing where the loop occurs and what the user is clicking on, I can't say for certain. Can you try to change it to "resume saved state" or "automatically decide" and see how it goes from there? We're happy to take a look at the .story file or even a sample/mocked up version and you can attach it here using the paperclip icon.
3 Replies
Hi Steve,
Are you able to look at the triggers associated with the "previous" button for your player on your master slide template - the default setting for previous is to return to the last slide seen - and therefore if you change the behavior you'll see the trigger within the trigger pane. You mentioned they're stuck in a loop because of the quiz slides, which likely didn't include a previous/next button on the first time through but a submit button? So are they revisiting the quiz slide and resuming it or seeing it reset to it's initial state?
It may help if we're able to take a look at this .story file so that we can see where the loop occurs and then any associated triggers.
Hi,
I have them set to "Reset to initial state", this would be the problem I assume?
Thanks,
Steve
Hi Steve,
It sounds like that may be contributing to it - but without seeing where the loop occurs and what the user is clicking on, I can't say for certain. Can you try to change it to "resume saved state" or "automatically decide" and see how it goes from there? We're happy to take a look at the .story file or even a sample/mocked up version and you can attach it here using the paperclip icon.
This discussion is closed. You can start a new discussion or contact Articulate Support.