We have a master file that publishes out 4 different versions of our course. In one module there are mutliple slides that will not allow the user to navigate with the back button or use the menu - even though the trigger is set up to allow the back button to work. I reimported this module from the last version (where this module did not have this issue) and rebranded everything only to find it still has the same issue. This is 2 days of troubleshooting and rebuilding....does anyone have any ideas what is causing this to happen? It happens in about 10 of the 19 slides in that module.
Hello Cheryl, would you be willing to share your SL file here so that either me/someone can take a look at your file and offer you with a possible solution. Without looking at the triggers that were set up on your file it's hard to say.
Thank you so much, Jurgen!! I think that might be it. I don't use that setting but this is not a course I developed so it does happen to have that setting. Fingers crossed@
This definitely fixes the issue. This is misleading thought as you are on the Slide Properties window so one would think that if you choose Resume saved state that it was referring to resume the state of the slide when the user revisits that slide...but instead it is meaning resume the course where you last left off. Very confusing. I have not yet had a situation where I thought I might need the Resume saved state...I doubt I'd ever use it now that I know what it really does. Is this something new with the last upgrade?
* Important: "jump the previous slide" don't mean "jump to the previous slide in the structure", it means "jump to the slide where the learner was before" => result: strange behaviour for linear courses or chapter
Here is the reply I got from the Articulate Customer Support Engineer this morning:
The Slide Property will affect just the specific slide, not the entire course. You are also correct that the "resume saved state" resumes the state of the slide when the user revisits it. In your case, the behavior was caused by combining the "jump to slide when timeline ends" trigger and the slide's property to resume saved state. Here's how it goes:
1. You visit a slide with the "resume saved state" property enabled. 2. The slide jumps to the next slide at the end of its timeline. 3. The final state of that slide is saved. 4. You click back to return to that slide. 5. Since you resume its saved state, you return to the end of its timeline which will then activate the trigger to jump to the next slide.
In short, you return to the previous slide but are immediately taken to the next slide because of the trigger that fires at the end of its timeline.
8 Replies
Hello Cheryl, would you be willing to share your SL file here so that either me/someone can take a look at your file and offer you with a possible solution. Without looking at the triggers that were set up on your file it's hard to say.
I thought I did share it - I uploaded it with this message. Perhaps it was blocked on my end.
This post was removed by the author
do you mean the behaviour
change all slides (at least in the affected chapter) from
"Resume save state" -> "Reset to initial state"
now the back button and the click in the menu should work
Hello Cheryl MacLeod, I hope you will be able to follow Jürgen Schoenemeyer solution to overcome the issue. Good luck.
Thank you so much, Jurgen!! I think that might be it. I don't use that setting but this is not a course I developed so it does happen to have that setting. Fingers crossed@
This definitely fixes the issue. This is misleading thought as you are on the Slide Properties window so one would think that if you choose Resume saved state that it was referring to resume the state of the slide when the user revisits that slide...but instead it is meaning resume the course where you last left off. Very confusing. I have not yet had a situation where I thought I might need the Resume saved state...I doubt I'd ever use it now that I know what it really does. Is this something new with the last upgrade?
what happens in detail with "Resume saved state" (of the slide) plus "auto jump to next slide":
here is a small peak what can happen with this settings
(I have moved the menu to the left -> always open)
https://360.articulate.com/review/content/d94ec3ee-c1b3-4237-9faa-2c686f99fa51/review
* Important: "jump the previous slide" don't mean "jump to the previous slide in the structure", it means "jump to the slide where the learner was before" => result: strange behaviour for linear courses or chapter
Thanks, Jurgen.
Here is the reply I got from the Articulate Customer Support Engineer this morning:
The Slide Property will affect just the specific slide, not the entire course. You are also correct that the "resume saved state" resumes the state of the slide when the user revisits it. In your case, the behavior was caused by combining the "jump to slide when timeline ends" trigger and the slide's property to resume saved state. Here's how it goes:
1. You visit a slide with the "resume saved state" property enabled.
2. The slide jumps to the next slide at the end of its timeline.
3. The final state of that slide is saved.
4. You click back to return to that slide.
5. Since you resume its saved state, you return to the end of its timeline which will then activate the trigger to jump to the next slide.
In short, you return to the previous slide but are immediately taken to the next slide because of the trigger that fires at the end of its timeline.