Forum Discussion
Link to lightboxed slide from a Review quiz layer causes the Quiz review Next button to restart at the first quiz slide.
For years I have used the Review Quiz layer to add an optional link to lightbox the slide where the answer to that quiz question can be found, and it has always worked perfectly. Now using the latest update to Storyline 360 the NEXT button always goes to the first quiz question after viewing that linked lightboxed slide. The previous button works as intended, and the next button works as intended after the previous button is used, or if the link is not used.
To recap - I see this with HTML5 output only. Given that flash is now obsolete it has become a greater problem. I developed a work-around, which is to link to a copy of the slide in an unlinked SCENE with NEXT navigation disabled and PREV navigation set to "previous slide" - or all player navigation disabled and a return to quiz button on the slide. It is also possible to set up conditional navigation based on a variable that would be triggered by clicking on the link and reset by clicking on the return to quiz link if you are using number of screens as a criteria for LMS completion.
I do the same thing. It appears to be a bug. See the thread here:
https://community.articulate.com/discussions/articulate-storyline/review-quiz-mode
Hi Paul,
It sounds like you're using Storyline 360, build 3.25.18088.0 and have run into this odd behavior? If you need to roll back, you can follow the directions here.
It would also help if we can take a look at your project file to investigate what's happening. You can share it publicly here, or send it to me privately by uploading it here.
I’ll delete it when I’m done troubleshooting.
Hi Ashley, I ran into this issue today with build 3.30.19518.0.
Hi Henry,
Sorry to hear this has crept up for you again, but we're still here to help.
To investigate this behavior further, we'll need to take a look at your .story file and it would help to see a copy of the published output. Can you share that with us? If you'd prefer to send along privately, our Support Team is at the ready!
Was this bug supposed to have been fixed in any of the recent releases? I did not see any notes about it. I did notice that it is something that does not happen when publishing to Flash only.
Hi, Paul. Thanks for checking in!
We're still looking into this bug's cause, but you're in the right place to stay up-to-date on our progress. I know publishing to Flash isn't an ideal workaround, so we promise to update this discussion on any new developments.
If there's anything I can do to help in the meantime, I'll be here!
I am also having this issue. What is the latest on the fix for this please? And has anyone found any workarounds?
Katie, is there a bug report filed for this that I can follow please?
This issue is also being tracked in this discussion as well as this one.
