Player buttons not compliant with parameters

Sep 01, 2014

Hi

After publishing my Storyline material, I got problems with 2 features :

- I choose "Exit the course" when user clicks the "Quit" button, but nothing happens when I click it

- I choose "Free" in the "Navigation restriction" menu, but nothing happens when I click on the items in the "Menu" items"

Someone can help me please?

4 Replies
Emily Ruby

Hello Thomas, 

Welcome to Heroes!

Are you testing this locally or have you tested this in the LMS or web server you are setting this up for?

You can look here for some information about publishing and sharing your file.

If you are testing on the intended environment and are still having issues, could you please attach the file so we can look at it for you?

Also, the exit course button does have some known issues based on browser security.

Thank you.

Thomas Vuaillat

Hello Emily,

Thanks for your answer !

In fact I published my Storyline content for web broadcasting, but I tested it only from local hard drive location and from another hard drive on my company’s network.

In both cases the “Quit” button was not efficient, and also the “Free navigation” from the “Menu” button is not efficient.

I had a look at the Storyline help online, I found that the “Quit” button may not be efficient due to security parameters of the web browser…so maybe it will be ok when I’ll put my training material on a website?

I tested my material with Internet explorer and Google Chrome, and I got the same bad result.

See attached screenshots about the parameters I choose, maybe you’ll notice I made some mistakes?

Thank you for your help

Emily Ruby

Hello Thomas,

have you tried testing it in a live environment such as Tempshare or the SCORM Cloud (this is the industry standard for testing content)

We have seen a few issues with Google Chrome on local computers. See here for the information.

Can you attach the actual .story file so we can look at the trigger?

Thank you.

khoi arvin

Hi Thomas,

We have the same issue when publishing to a "shared" network drive.

In addition to Emily's ideas about Tempshare and Scorm Cload, do you have admin rights in your LMS to create a folder that nobody else can see.

We created a "feedback" folder in our LMS. This let's us publish to the final environment but nobody else can see the content.

Khoi

This discussion is closed. You can start a new discussion or contact Articulate Support.