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.
Hi Jacqueline,
This issue is still open with our team. I wanted to share some information on how we define bugs and how we tackle them when they occur.
This conversation is linked to the report so that we can share any updates with you here, but currently, we have no workarounds listed for this scenario.
Can you share a bit more information about how you're using a lightbox during your review process and perhaps we can come up with an idea in the meantime.
Thanks Leslie.
I created a course that uses a "test out" branch. That branch skips directly to the quiz. On each quiz slide, I have a review button that opens a lightbox slide that covers related information. It works fine when the user initially takes the test, but when they open the lightbox during a quiz review and then click NEXT, it circles them back to the 1st quiz question no matter what question they are on.
The steps I have taken to work around this (and thanks to several others who have tried varies approaches on related issues) are as follows:
1. Disable navigation buttons on quiz question slides.
2. On quiz question master, set triggers to hide PREV and NEXT buttons.
3. Remove slide transitions to avoid "flicker" of PREV and NEXT buttons on slide entrance (flicker lasts as long as transition).
4. Create custom PREV, NEXT, and SUBMIT buttons for each quiz question slide.We plan on using a test out option more often going forward, so it would be nice to have an easier solution.
Thank again.
Was there any progress on fixing this bug?
Hi Jacqueline,
This issue is still open with our team. I appreciate you chiming in since we haven't heard from folx on this in a while. I've added a note on our report to let the team know.
