Prev button issue


I tried what Dena said "Thank you for your help! I hadn't disabled the Submit button on the individual questions in the question bank and that was turning on the Prev/Next buttons!"  (

which is to replace the default SUBMIT button with the custom made SUBMIT button. 

I had turn off the "previous" and "submit" at the setting at base layer. But the PREV button still comes out after I interact with all the question and came back to review it. The most obvious one is the first question as it is the first slide.

I have attached a dummy storyline for your review.

Please help urgent!



18 Replies
James Picton

Agreed. This is a pain.

If a user completes the course, by previously pressing Next/Submit (whatever you may have setup as a trigger) and then returns to the same screen and exits - without pressing the trigger button - their completinon flag for this screen will be erased.

Not cool if you are using it, like I am as a trigger to take you to the final screen in a course and the result is going to an LMS.

Has this been resolved yet?



Ashley Terwilliger-Pollard

Hi James,

As Phil mentioned, it's expected behavior - so I'm not sure what you're referring to in regards to resolving it? 

Typically if you've met the completion requirement (slides viewed or results slide) and then you exit and resume the course, most LMS's would consider it in review mode.  Is your LMS giving you a second chance through the course and resetting it? 

If as Dena mentioned, you'd like to have an option to disable the Prev and Next buttons during quiz review so you can use your own custom navigation buttons, please let us know. We value your feedback.

James Picton

Hi Ashley,

Completely understand the logic and yes, it makes perfect sense. However in my case, this is what is occurring ....

Firstly, I'm using custom PREV/NEXT buttons in my course. All screens have the default PREV/NEXT buttons turned off - I have triple checked this. I have changed my second-last screen into a freeform 'pick one' interaction and use the NEXT button to submit a 'course completed' variable which then also takes the student to the final (summary) screen - and sends a completion flag to SABA LMS.

My problem is this: If the student presses PREV from the final screen (taking them back to the freeform 'pick one'), in addition to my custom PREV/NEXT buttons, I now also get the standard Storyline PREV/NEXT buttons! Ordinarily I'd simply click the base layer, click the cog and de-select the PERV & NEXT buttons...but they're not activated. Weird. So, the question is, why are the default Storyline PREV/NEXT buttons appearing on the screen, when they're turned off? If I reset the option on the second last slide to 'Reset to initial state' the buttons do not appear, but as discussed in my original email this is not the best solution to the problem. 

Unfortunately all my content is classified, so I can't post sample courses etc.


James Picton

Just re-read your previous post, Ashley! I attempted to submit a feature request through Chrome and IE, but both times the form submission failed with a message:

"Your browser does not have Flash support. Please install the Flash plugin and try again."

Um...yes I do...double checked both of them. Both at the latest version and Flash works on all other pages.

Can you do me a favour and log the request for me, please? Whilst you're at it, you also told me to log a feature request for  a confirmatory dialogue box when using the 'Confirm on Exit' functionality ( - could you possibly slide that one in as well?

Cheers - I owe you a beer!


Ashley Terwilliger-Pollard

Hi Jim,

I can definitely send it in on your behalf - and I just read about an issue we're having with our site right now where the upload page for support cases and the Feature request submission are not working - so you're not alone! Our team is working on it and hope to have it resolved shortly. 


Mr Brown

Hi there Ashley - was the issue with the Next/Prev default buttons resolved?? I have the same issue but I'm having a hard time finding a solution in the thread. This is my final day (deadline day) and this is the only thing that is preventing me from submitting the final version of my course. If you could point me in the direction of the solution I'd be grateful. just to confirm I have custom buttons and all defaults are disabled, but the buttons still show up when returning to a question. Many thanks.... 

Alyssa Gomez

Hi Mr. Brown! 

Sorry you're running into this problem. I know you're on a deadline, so I want to get you the help you need right away. Since this is an older thread, let's start fresh.

Can you tell me what version of Storyline you're using? You can check by going to Help >> About Storyline. 

Also, do you find that this problem happens in Storyline preview mode, or only after you've published the project?

Mr Brown

Hi Alyssa - I opted to reset each question (on review)... this stopped the prev and next buttons showing up... not ideal. But the client opted for no results page and just to use the quiz as a knowledge check only (i.e. no formal assessment / pass or fail). 

So I don't have the issue at the moment. However it would be good to know how to resolve this for Storyline 2 and 3, because when i create each course I do so with No Defaults at all. As you know clients are fickle creatures and I fear that it may come back on review :)Everything is custom to client branding, so having a default back and next show up is not the best.

In answer to your question... preview mode doesn't show the defaults only occurs when I've published the course. Thanks for replying! ;)

Leslie McKerchie

Hi Mr. Brown,

When learners review a quiz (or revisit question slides they've already submitted), they'll see Articulate Storyline's built-in Prev and Next buttons in the lower right corner of the player—even if you've disabled them throughout your course. These navigation buttons are necessary for learners to review quiz slides.

If you'd like to have an option to disable the Prev and Next buttons during quiz review so you can use your own custom navigation buttons, please let us know

Dan Marigot

This is not good for everyone, clients that look at us as developers and developers that want A to do B but cannot. Storyline is basically kicking us to the curb. All you have to do is add some sort of check box to give us the choice to either show/hide the "review quiz" mode. Over 5 years and you still can't find a fix??

As an FYI, I already fired the employee who recommended this software to the company. Now things are getting done correctly here. I understand you might want to hold out on this basic function to sell on your next version but I truly hope you guys come to your senses and give the people what they desperately need. Or else more people will get fired due to the inability to fix issues.

Dan Marigot

Thanks Phil for chiming in.

So it sounds like it's either an "all or nothing" structure. The player should still give us an option to choose rather than pop-in when unwanted.

It's like driving a car down a street (we think we have control to go straight) but suddenly the car can only turn left no matter what we do to the steering wheel.

Over 5 years ... still no fix. How much longer will this go on?

Mr Brown

Hi and thanks Leslie -

I kinda figure this was not an option as I've used SL for a while and I could not find a solution other than removing the ability to review the quiz for the students. I would've assumed that a 'custom back and next button' would be part of default functionality using the buttons I had already designed for my course. (How wrong I was). So no review for my clients, unless I use SL3 defaults, so it doesn't look a mess. Mmm not much customisation ability there... when I can customise pretty much everything else.

"If you'd like to have an option to disable the Prev and Next buttons during quiz review so you can use your own custom navigation buttons, please let us know. "

I found this strange as I would of thought with all the other customisation options this would taken as read...

Thanks for the reply.... I know where I stand now.