I'm having an issue with the published work of a Storyline 2 project. When in the preview mode, all my slides, triggers, etc. will work properly as I want them to. However, after publishing to a folder as an html for google chrome access, I'm stuck on the same slide about halfway through the project. I also have disabled the default 'previous' and 'next' buttons to have my own featured, but the default ones show up after pressing previous on the troubled page and remain. Hopefully that all made sense.
Thanks for sharing those details here. Just a few things to check: are you working from your local hard drive? It sounds like you've published to web - have you uploaded the published content to a web server like Tempshare for testing? If you remove the slide that's giving you issues, are you able to move forward in the course? Have you tried fixing the issue using this import method?
If you're still having trouble, feel free to share your project here, let us know which slide is the culprit, and we'll take a closer look!
I am saving it to a local hard drive. I also tried your tip on deleting the slide and publishing it again. It did allow me to go on to the other slides as allowed/normal. However, it still is wanting to allow the default "previous" and "next" buttons to resurface on top of my personal buttons made after pressing the custom "previous" buttons. I do notice though, that this problem only arises when it is with interactive material they have to complete before continuing. I will still attach the original project so you can see for yourself what might be the possible solutions. Slides 1.24 and 1.25 are where the problems start. Thank you!
Hi Jill, thanks for sharing those details. It looks like you've attached the published file here - would you mind attaching the original .story project file instead?
I did want to mention that previous/next buttons will reappear when the learner revisits quizzing slides, as the user would need a way to continue navigating throughout the course and Storyline may not know that you set up your own custom buttons.
Sorry about that, here is the original .story file. Thank you for sharing that information on the quizzing slides...is there not any way to allow your custom buttons to serve the same capability as the default buttons?
I took a peek into your file, and I found that the drag and drop interaction on Slide 1.24 did not have a "Correct" layer. Therefore, you cannot move forward if you get the question correct. I added a Correct layer to that slide and re-attached your file here.
I published your file to Web, and I did not see the default previous and next buttons appear after clicking the custom previous button. Here is the link to the published output so you can test it on your end. Let me know how it works for you!
Out of curiosity I tested your file with HTML5, and now I see the Previous and Next buttons appearing. Let me do a little more digging on this, and I'll pop back in when I have more information to share!
It looks like a similar issue has been discussed over here in this thread, as well. It seems this is a known issue with HTML5 output, and it's in the hands of our Quality Assurance team. I'll add this thread to the report, and as soon as I have any updates on the issue, I'll post them here in this discussion.
In the mean time, you can try the workaround offered in the thread I linked above:
If you set the correct and incorrect feedback layers to allow seeking = yes (http://screencast.com/t/qAyOOhm3x0G), it stops the issue from happening. However, it also means that when 'replay' is clicked, it doesn't replay the question from the beginning, instead it just replays the feedback layer.
I've tried your suggestion from the thread and it still seems to prevent me from going forward when I press the custom 'next' button and showing the default buttons after pressing 'previous'. Is there are any other solution to work around this problem? It seems to be concentrated around slide 1.25
I'm sorry, Jill, I don't have any other workarounds to offer at this time, other than viewing the content with Flash instead of HTML5. We’re still actively working with our QA team to determine if there is a resolution for this issue, and I'll be sure to share updates with you as soon as more information is available!
9 Replies
Hello Jill,
Thanks for sharing those details here. Just a few things to check: are you working from your local hard drive? It sounds like you've published to web - have you uploaded the published content to a web server like Tempshare for testing? If you remove the slide that's giving you issues, are you able to move forward in the course? Have you tried fixing the issue using this import method?
If you're still having trouble, feel free to share your project here, let us know which slide is the culprit, and we'll take a closer look!
Alyssa,
I am saving it to a local hard drive. I also tried your tip on deleting the slide and publishing it again. It did allow me to go on to the other slides as allowed/normal. However, it still is wanting to allow the default "previous" and "next" buttons to resurface on top of my personal buttons made after pressing the custom "previous" buttons. I do notice though, that this problem only arises when it is with interactive material they have to complete before continuing. I will still attach the original project so you can see for yourself what might be the possible solutions. Slides 1.24 and 1.25 are where the problems start. Thank you!
Hi Jill, thanks for sharing those details. It looks like you've attached the published file here - would you mind attaching the original .story project file instead?
I did want to mention that previous/next buttons will reappear when the learner revisits quizzing slides, as the user would need a way to continue navigating throughout the course and Storyline may not know that you set up your own custom buttons.
Sorry about that, here is the original .story file. Thank you for sharing that information on the quizzing slides...is there not any way to allow your custom buttons to serve the same capability as the default buttons?
I took a peek into your file, and I found that the drag and drop interaction on Slide 1.24 did not have a "Correct" layer. Therefore, you cannot move forward if you get the question correct. I added a Correct layer to that slide and re-attached your file here.
I published your file to Web, and I did not see the default previous and next buttons appear after clicking the custom previous button. Here is the link to the published output so you can test it on your end. Let me know how it works for you!
Hi Jill,
Out of curiosity I tested your file with HTML5, and now I see the Previous and Next buttons appearing. Let me do a little more digging on this, and I'll pop back in when I have more information to share!
Hello again Jill,
It looks like a similar issue has been discussed over here in this thread, as well. It seems this is a known issue with HTML5 output, and it's in the hands of our Quality Assurance team. I'll add this thread to the report, and as soon as I have any updates on the issue, I'll post them here in this discussion.
In the mean time, you can try the workaround offered in the thread I linked above:
If you set the correct and incorrect feedback layers to allow seeking = yes (http://screencast.com/t/qAyOOhm3x0G), it stops the issue from happening. However, it also means that when 'replay' is clicked, it doesn't replay the question from the beginning, instead it just replays the feedback layer.
Alyssa,
I've tried your suggestion from the thread and it still seems to prevent me from going forward when I press the custom 'next' button and showing the default buttons after pressing 'previous'. Is there are any other solution to work around this problem? It seems to be concentrated around slide 1.25
I'm sorry, Jill, I don't have any other workarounds to offer at this time, other than viewing the content with Flash instead of HTML5. We’re still actively working with our QA team to determine if there is a resolution for this issue, and I'll be sure to share updates with you as soon as more information is available!
This discussion is closed. You can start a new discussion or contact Articulate Support.