NEXT Button not working

I have a package which I have almost finished. I have the NEXT button moving from one slide to the next. It is a branching course with numerous menus. It was all working great. Unfortunately the button has stopped working on two slides. The settings are exactly the same on this slide to the other slides. Each slide advances "by user" and when revisiting it "automatically decides".

The correct slde comes after both sldes where the Next button is not working.

Unfortunately the button just does not do anything.

Why? What can I do to make the button work again.

20 Replies
Graham Betts

Unfortunately the file is way too big to upload. This is a very large package with an interactive site map that tracks usage, glossary, 3D animations and video footage, not to mention formative assessment tasks.

However the next button is just the standard one. Are there any known bugs with the Next button? Alternatively what things can prevent the NEXT button from working?

Nancy Woinoski

Graham Betts said:

Unfortunately the file is way too big to upload. This is a very large package with an interactive site map that tracks usage, glossary, 3D animations and video footage, not to mention formative assessment tasks.

However the next button is just the standard one. Are there any known bugs with the Next button? Alternatively what things can prevent the NEXT button from working?


Is the next button jumping to a slide in a new scene by any chance? If it is then you have to specify which slide it is in the button trigger. The default for the trigger is jump to "next slide" but when you are jumping to a slide in a new scene storyline does not know what the next slide is unless you tell it.

Simon Perkins

If Nancy's idea doesn't work then you could try uploading the "broken" piece of your course here so someone can take a look or import all your content into a new Storyline file.  I'm not saying you have a bug - it's more likely a setting that's out - but if it is, then importing into a new file can sometimes get things back on track.

Rory Lavender

Leslie, are you implying in your response to Vince that the Player Next button on free navigation might be having issues in SL2? I ask because all of a sudden it seems like some of my standard player Next buttons are not working when they once did. I am revisiting some older files for updating. I know they worked before, but now I am having to create buttons on the slide because I can't get the player to advance. I do understand that with non-free navigation, the timeline must finish, but it seems like this is happening on free navigation now too. Thanks. Just wondering if there is some recent bug... thanks.

Leslie McKerchie

Hmm, not that I'm aware of Rory. 

I popped in to take a look at Vince's case (because there have been a lot of posts in 3 months) and it looks like I was not able to recreate the issue, asked some follow-up questions, and did not hear back.

So, I do not have an update to share on that specific scenario, but I could certainly take a look at your .story file if you'd like so that we can see if something is going on.

Rory Lavender

Hey Scott - I just retested to be sure. I published to Web then View Project. It works on Chrome 69 and IE 11. I used Storyline 2 as well. I just uploaded it to our LMS (Valamis) and it worked there as well, in both Chrome (with Flash allowed) and IE. Might I recommend that you import the  slides in to a new story or recreate the slide to see if that fixes the problem? Sometimes when I have a slide that is wonky, starting from scratch can fix - even when what you create is exactly the same as the original slide or story. 

Matt Kurtin

When Next button becomes enabled, but nothing happens after you click the button, the first thing to check is to make sure you are publishing the whole project and not just one of the scenes. If you have only published the first scene, the Next button cannot jump to the next scene because it doesn't exist in the published course, but there is no error message detectable to end user.

Another thing that can make this tricky is that the setting for whether you are publishing the whole course or just a scene is preserved individually by Publish target, so it may be set to Entire Project for Review 360, but sets itself back to single scene when you switch from there to publishing for LMS if that is how it was last set for LMS.

Be careful not to miss that. Otherwise, you can spend a lot of time looking in your code for what is wrong with the next button trigger, when there is nothing wrong there.