button states after publishing
Nov 04, 2016
I am creating a course which has buttons on many of the slides which trigger layers with additional information. I have the buttons set to change state when clicked on to show the learner they have looked at that information. Everything works fine when I preview the course but when I publish the course the buttons do not work in the same way. They do not stay in the down state when the user clicks anything else on the slide. I have tried different settings but am not sure what to try now.
3 Replies
Hi Caroline,
do you preview your course locally on your pc? Then try the story_html5.html instead of the story.html. Or did you upload it and it didn´t work? If you use the preset button from storyline which have different states already you own set trigger could cause problems.
Susi
Thanks for popping in with those questions and suggestions, Susi! Always appreciated :)
Caroline- In addition to what Susi suggests, I'd like to know what environment you're publishing for and where you're viewing the published output from. If you're viewing it on your local hard drive, you may encounter security restrictions from the computer, web browser, Flash Player, and network that can cause various features of your content to fail. To properly test your published content and share it with others, upload it to the environment for which it was published. For instance, if you're publishing for the web then you'll want to upload the published output to a web environment, such as tempshare, to properly test it.
If you're testing in it's proper environment and still seeing this issue with your button states, would you be able to share your project file here for us to do some testing? You can add it as an attachment right to a comment in this thread. Thanks!
Thank you, Ali and Susi. I had published the course for our LMS but had been testing it right off the server. I uploaded onto our LMS and it works fine. Thank you both the the super quick responses!
This discussion is closed. You can start a new discussion or contact Articulate Support.