Forum Discussion
Continue Button Workaround?
I've created a course with multiple audio and video clips. Because there is no native autoplay in Rise (which there should be), I've added a javascript player. It works well, thanks to anthonyvecchi.com linked here.
https://anthonyvecchi.com/RiseVideo/index.html#/lessons/-i0Q5dN_3fhA-55EI9fjx7Owsd7WJKPw
The issue is that if multiple audio or video clips are in the same lesson, they all start at the same time. The solution was to add a Continue button between the clips, so the next one in line starts after you click continue. After adjusting the browser to allow autoplay, it works great; however, Rise's behaviors for continue buttons is that they disappear when clicked. if you go back to a lesson, there are not continue buttons and the clips once again play at the same time. I've seen a possible solution to add a Button, but that only allows to jump to a different lesson, not a to a block within the lesson it is in.
So, other than putting every single audio/video clip in a separate lesson, has anyone figured out a workaround to either get the continue buttons to stay, or any other solutions/ideas?
I will say this has been a hot topic in threads for at least 7 years, with multiple users asking for the option to retain the continue button (and autoplay), but Articulate seems to not care. Too bad.
1 Reply
One thing worth flagging before the workaround hunt: the browser autoplay setting you changed is local to your machine. Most learners' browsers block unmuted autoplay by default, so the clips that work great for you will likely sit silent (or behave inconsistently) for everyone else. Autoplay is a losing battle in the wild.
The pattern I'd build on instead: gate every clip behind a tap. One Storyline block per clip, video set to not autoplay, with a plain Play button the learner clicks. Nothing can stack or double-play, on first visit or on revisit, because nothing plays until the learner starts it — no autoplay flags, no Continue-button gymnastics. It also survives the LMS, where autoplay is almost always blocked.
You already found the answer on the Continue button: it disappears by design once clicked (it marks progress), so any solution that depends on it sticking around will break on revisit. And you're right that Button blocks can only jump to lessons, not blocks — so within-lesson gating has to come from click-to-play, not navigation.
If you want to stay 100% native in Rise, one clip per lesson is the only clean option, which you've ruled out. The Storyline-block-per-clip route is the one I'd ship.
