Forum Discussion
Slide master button to jump scenes not working
I'm wondering if there are constraints around actions for buttons on a slide master. I created a master slide with a button that is set to jump to the next scene. I insert the slide into the presentation and can see the button, hover over it, and click it, but it doesn't do anything.
I have other buttons on slide masters that work (exit, jump to next slide, etc.). Is this a glitch or is it not designed to be able to jump to next scene? I couldn't find any documentation about what is/isn't allowed.
Thanks!
Hello Everyone!
I wanted to share some great news! We are no longer seeing the bug that caused the Jump-to-next-scene triggers on slide masters to stop working.
Please make sure that you are using the current version of Storyline 360 (Build 3.77.30568.0). This guide walks you through installing, updating, and opening Articulate 360 apps.
Please let us know if you're still encountering the issue and we'd be happy to continue troubleshooting with you in a support case.
That is interesting, I haven't needed to jump to the next scene from a button on the slide master. Typically I like to explicitly say which slide/scene I want to go to vs. relying on "next" as that may go to an unexpected slide/scene, if navigating using the Menu, but I get if you have a global button where they could jump to the next scene from any slide, that would make sense.
I tested in attached file, assuming this is what you are referring to, the next slide works, but next scene doesn't, maybe I am missing something. Thinking SL may not have reference to what the next scene may be?
Yes, that's exactly what I'm experiencing but you are right, next scene is a little sketchy and could cause issues. I did some more testing based on what you said and I CAN have it jump to a specific scene so there must be something about it not knowing "next scene." Since I'm using this in a Template, I was able to have the slide master jump to the "Final Assessment" scene in the template and it works. This is definitely a smarter option than what I was originally trying to do. Thanks!
Hi Mary Kate,
Thanks for contacting us to share what you are experiencing with your slide master.
I'm glad that you were able to find a workable solution.
This is an issue that has been shared with our team for further investigation. I've added this conversation to the report so that we can share any updates we have in the future.
Same deal here too. I have attached my .story file which in the second scene, third slide, you'll see three buttons. A button right above the page numbering which is in the slide master (does not work). Above that are two other buttons, one is set to jump to the next scene (works) and another that jumps to a specific scene (also works).
My goal is to replicate the client's current HTML courses and use my own navigation buttons instead of the player's previous and next arrows.
Hello there, Bill!
Thank you for sharing your findings with us. I added your example to this bug's report, and you're spot-on: the main workaround is to place the 'Jump to next scene' and navigation triggers directly on a slide rather than the slide master.
Let me know if there's anything else I can do, and I promise to reach out as soon as we have more details!
Hi all!
I am happy to report that we are not seeing this behavior in Storyline 360 (Build 3.49.24347.0):
- Triggers for previous and next buttons on the Slide Masters didn't work.
If you're still running into this snag, make sure you're using the latest version of Storyline 360.
Don't hesitate to reach out to us in this discussion or in a support case if you have additional questions!
Hello Everyone!
I wanted to share some great news! We are no longer seeing the bug that caused the Jump-to-next-scene triggers on slide masters to stop working.
Please make sure that you are using the current version of Storyline 360 (Build 3.77.30568.0). This guide walks you through installing, updating, and opening Articulate 360 apps.
Please let us know if you're still encountering the issue and we'd be happy to continue troubleshooting with you in a support case.
