Has anyone figured out the problem for the Exit Course button issue yet??? I have changed my configuration files according to instructions, and STILL the Exit Course button does not close out the Storyline file. My boss is starting to get irritated with Storyline and I DON'T want to have to change programs! I love all the other features!
Have you reviewed this article with some solutions based on how you have published your course?
As it sounds like you've already reviewed a few of the other threads, would you be able to share your .story file with us here or submit a Support case?
I am having the same issue with Storyline. I followed the instructions in the article and it will still not close the course. It is doing this both in Chrome and IE9. I created a launch page and I tried both modifications of the configurations.js file and nothing seems to work. The content is being launched from a web server though not through an LMS. I will try it from the LMS, but I want the ability to have the content launch from both places and close correctly.
I don't know if this would work for you, but I had a similar issue with a client that launched Storyline course from within a Moddle LMS. The Exit Course triggers didn't work for them. I ended up using a JumptoURL/File trigger that calls an HTML page in the current browser window. This HTML page does nothing else but close on itself. Here is a quick example: http://dev.keypointlearn.com/xcl71_SL/Exit/V1/story.html
I am willing to give that a shot, but I am not sure I am fully tracking your suggestion. Did you set-up the called HTML page and if so, does it have code on it that drives the closure? I'm not sure what I am pointing to with the JumptoURL command.
I am willing to give that a shot, but I am not sure I am fully tracking your suggestion. Did you set-up the called HTML page and if so, does it have code on it that drives the closure? I'm not sure what I am pointing to with the JumptoURL command.
Thanks for your help.
Hi Brent, the HTML page I set up only has a few lines, see attached. Just make sure that you set up the JumpToURL trigger to open this HTML page IN THE CURRENT BROWSER WINDOW and then give it a try. It worked for my client and I know they did quite a bit of testing with various browsers in their LMS.
For some reason this is also not working. The extra page opens and immediately closes itself but not the course. For now, I added a layer that tells the user to just close the browser.
Thanks for you help and time. I'm not sure why it is not working.
I am willing to give that a shot, but I am not sure I am fully tracking your suggestion. Did you set-up the called HTML page and if so, does it have code on it that drives the closure? I'm not sure what I am pointing to with the JumptoURL command.
Thanks for your help.
Hi Brent, the HTML page I set up only has a few lines, see attached. Just make sure that you set up the JumpToURL trigger to open this HTML page IN THE CURRENT BROWSER WINDOW and then give it a try. It worked for my client and I know they did quite a bit of testing with various browsers in their LMS.
Michael,
I love the idea but the link to windowcloser.htm is not working for me.
9 Replies
Hi Gina,
Have you reviewed this article with some solutions based on how you have published your course?
As it sounds like you've already reviewed a few of the other threads, would you be able to share your .story file with us here or submit a Support case?
I am having the same issue with Storyline. I followed the instructions in the article and it will still not close the course. It is doing this both in Chrome and IE9. I created a launch page and I tried both modifications of the configurations.js file and nothing seems to work. The content is being launched from a web server though not through an LMS. I will try it from the LMS, but I want the ability to have the content launch from both places and close correctly.
I don't know if this would work for you, but I had a similar issue with a client that launched Storyline course from within a Moddle LMS. The Exit Course triggers didn't work for them. I ended up using a JumptoURL/File trigger that calls an HTML page in the current browser window. This HTML page does nothing else but close on itself. Here is a quick example: http://dev.keypointlearn.com/xcl71_SL/Exit/V1/story.html
Michael:
I am willing to give that a shot, but I am not sure I am fully tracking your suggestion. Did you set-up the called HTML page and if so, does it have code on it that drives the closure? I'm not sure what I am pointing to with the JumptoURL command.
Thanks for your help.
Hi Brent, the HTML page I set up only has a few lines, see attached. Just make sure that you set up the JumpToURL trigger to open this HTML page IN THE CURRENT BROWSER WINDOW and then give it a try. It worked for my client and I know they did quite a bit of testing with various browsers in their LMS.
Michael:
Thank you. That makes sense. I will use this a work around.
Let me know how it goes. I'm interested to hear if my 'sledgehammer method' worked for someone else
For some reason this is also not working. The extra page opens and immediately closes itself but not the course. For now, I added a layer that tells the user to just close the browser.
Thanks for you help and time. I'm not sure why it is not working.
Michael,
I love the idea but the link to windowcloser.htm is not working for me.
Any chance you could post a sample Story file?
Thanks!
This discussion is closed. You can start a new discussion or contact Articulate Support.