My course has custom navigation so I am not using any of the nav controls on the player. I have some learning check screens which are using a MCQ, they don't use a results page. These work fine, however if I set them to resume saved state and revisit those pages, the next and back player buttons are turning on. I have no idea why. This does not happen if I set them to resume initial state.
that is expected behaviour if the user is reviewing the quiz slides - unfortunately no way around it with custom nav - I have the same issue. If they don't display the user gets to the first slide and then can't progress.
I know it was under review by the Articulate team - haven't seen any update come through.
I'm not a techie by any means but take a look at the published output file story_content > frame.xml and do a find/replace on all the next and prev buttons - see if you can change the True to False if that makes any difference.
Disclaimer: Articulate don't support any change to published output files...let me know how you go.
I inherited a course from a client and this does not happen. In fact mine is based on this course, so unsure why it's doing it. I just re-exported their old one thinking it's my Storyline and it does not happen. In fact i have never seen this happen before.
Thanks for reaching out here, and Wendy is correct that this is the behavior we'd expect and currently by design. I know I've heard of other users who were able to have them not appear at all, similar to how your other file is working - but I don't know how they were able to accomplish that. I know in SL1 you could remove all the player elements as a whole and then they would not appear - but now they can appear on top of the slide stage. If you're other file is working, have you tried to import in the non working file into that one to see if it'll pick up the properties of that set up instead? You could then delete all the other original slides.
7 Replies
Hi Geordie
that is expected behaviour if the user is reviewing the quiz slides - unfortunately no way around it with custom nav - I have the same issue. If they don't display the user gets to the first slide and then can't progress.
I know it was under review by the Articulate team - haven't seen any update come through.
Maybe someone can chime in with a workaround.
I'm not a techie by any means but take a look at the published output file story_content > frame.xml and do a find/replace on all the next and prev buttons - see if you can change the True to False if that makes any difference.
Disclaimer: Articulate don't support any change to published output files...let me know how you go.
Hello Wendy
I inherited a course from a client and this does not happen. In fact mine is based on this course, so unsure why it's doing it. I just re-exported their old one thinking it's my Storyline and it does not happen. In fact i have never seen this happen before.
you using SL1 or SL2?
This is from a recent post
https://community.articulate.com/discussions/articulate-storyline/player-buttons-appear-when-re-visiting-a-slide
SL2
Hi Geordie,
Thanks for reaching out here, and Wendy is correct that this is the behavior we'd expect and currently by design. I know I've heard of other users who were able to have them not appear at all, similar to how your other file is working - but I don't know how they were able to accomplish that. I know in SL1 you could remove all the player elements as a whole and then they would not appear - but now they can appear on top of the slide stage. If you're other file is working, have you tried to import in the non working file into that one to see if it'll pick up the properties of that set up instead? You could then delete all the other original slides.
This discussion is closed. You can start a new discussion or contact Articulate Support.