Jump to URL Trigger Not working when revisiting slide
Oct 13, 2016
Hi All,
I'm having a challenge with the Jump to URL Trigger not working when I revisit a slide after I've clicked on the Jump to URL target
This happens when revisiting the slide from both the menu and via the prev button
As you can see above, I have two rectangles, the green and yellow ones.
When the user clicks on them, they each send the user to a different URL.
When both links have been clicked, the next button is enabled, and the user can progress onwards.
The rectangles are have a visited state that looks as follows:
So, for some reason, while on the slide for the first time, you can click on the rectangles and get sent to the URL as many times as you want, regardless of the state.
BUT, once you go away from the slide (whether by the next button or the menu) and return, whether via the menu or via the prev button, the links fail to respond, even if I tell the slide to reset to the initial state.
Any help on this would be appreciated.
6 Replies
If possible you might consider sharing your .story file via ADD ATTACHMENT so the community might help you troubleshoot things faster.
I'd love to, but there's just too much confidential information in this course to put it out in open forum. Also, its quite a large file - fully voice acted - is there a file size restriction on attachments?
Hi Martin!
How about a importing this slide into a new file so that we could take a look at the particular set up? If you need to make dummy URLs or change info - that's perfectly fine.
You are also welcome to work privately with our support team here if needed.
Hi Martin
what slide property do you have set for 'revisit'
Hi Wendy,
Currently, I have reset to initial state set. I've submitted this challenge to support and they can't figure it out and are having to look into it, so this likely has greater fundamental issues than a setting at this point.
Hi Martin!
Thanks for mentioning that you reached out to support as well. I see your support case (00908179) and it does look like they shared it with our QA Team, so no resolution to share at this time.
This discussion is closed. You can start a new discussion or contact Articulate Support.