Forum Discussion
"Resume Saved State" is not saving State of Next Button when returning to slide
Hello,
I have a slide that hides the Next button when the Timeline starts, then brings it back to Normal when the users Visits 3 objects (and their States change to Visited). I have the slide set to "Resume Saved State" for when the user returns.
However, when the user does return to the slide, the Next button is still hidden and the user has to click the last object (whose State is still Visited) in order for the Next button to appear. I need the Next button to stay Saved along with all of the other States when returning to the slide. Any help?
Thanks!
23 Replies
I am also having this issue.
Per Walt's comment, I have my slides set to "Save state on revisit", so that's not it.
The workaround Alyssa Gomez posted above (setting the next button to false until timeline reaches 0.5s) works, but if this is a bug, as was referenced above, I'd love to know when it will be resolved...
Oddly, before adding the 0.5s "fix", if I went back a few slides more, then clicked the next button several times in a row, it would work.Even more oddly, if I did that really fast, I could even sometimes get it to advance PAST where I'd been (so avoiding any variable triggering at all).
Would love to have some definitive answers from Articulate as to what's going on. ;)
Thank you!Hello!
We'd love to help! I looked at similar cases where others are running into this same snag. It looks like our Support Engineers were able to offer specific troubleshooting steps and a solution after looking at the affected file. Are you able to share your file with our team? If so, here's a secure upload link. We'll let you know once we receive the file and begin troubleshooting.
Hi Lauren,
Thank you for your reply.
So, is it correct that this is a known bug? I wasn't quite sure based on what you wrote...
Thank you for the kind offer. However, as the 0.5s workaround is doing the job, I'd rather wait until the issue is fixed (I have more than one file impacted).
Thank you!
FYI: There is definitely a bug, because triggers set to execute when the timeline starts do re-execute even when a slide is set to Resume Saved State (i.e., to not replay the timeline).
Until the bug is fixed...
- If only some slides should disable Next, use a condition on the trigger that disables it (as described above).
- If all slides should disable Next until the timeline ends, just set the Menu navigation to Restricted. That automatically disables Next the first time a user visits a slide, enables Next when the timeline ends, and keeps it enabled when the user revisits -- all without the need for triggers.
Note: You can override Restricted navigation on an interaction slide by adding your own triggers to control the Next button.
Dear Staff... did you fix the bug?
Hi Camilla,
I just responded to a similar conversation here.
Adding on to this conversation gave me another clue into what you may be dealing with.
We've consulted with our product team on the behavior where the Next button returns to hidden or disabled when revisiting the slide, and after careful review, we determined it to be by design based on the navigation features.
We recommend using the settings outlined here.
2023 and the issue still persists but @Ronda Otey, EnableNext1 variable solution still fixes the issue.
