Exit Course issue

Hi Adam I am using an Opigno LMS and now having that same issue since yesterday...

Hi Adam,

Thanks for contacting us and sharing what you've run into with your published course.

Our team is currently looking into this and I've attached this conversation so that we can share any updates with you here.

The following support article may help while Articulate looks into this issue... https://articulate.com/support/article/exit-course-trigger-doesnt-work-sl2

Thank you Leslie.

Brian: i tired to edit the Configuration.js file but i keep getting access denied message when i go to save it.  Is there a possible reason why it would not let me save it. My initial thought could be because i don't have admin rights but i'm not sure...

It probably is admin permissions... I'm running into similar issues this morning with a different app.

That's what i thought. I'm going to see if i can get one of the IT guys to remote into my machine so we can try this. I'll let post the result once we can do do that.  

I have been trying that I used notepad to edit the Config file but in order to edit you have to open note page as an administrator...right click on notepad and select run as administrator....am still getting the access denied error after republishing the files

This wasn't working for me either, then i realized i had edited the wrong file. Once i edited the correct file, Exit no longer works.  

Update, i changed to var EXIT_BEHAVIOR = “ALWAYS_CLOSE_TOP”  in the scormdriver.js file and it finally worked in closing!!  

Hi, Guys what seems to be happening is that the config file is changing when the course is published and zip...so what I did and it WORKS is use javascript on my exit button and use the following code in the javascript file

window.location.href = "lms/goodbye.html";

AH --So you found a solution as well!  

Hello everyone,

Thanks for reaching out! I'm so sorry you're seeing an error when exiting courses that you published with the latest Storyline 360 update. We'll fix this in our next update, and here's how you can avoid it in the meantime.

1. Go to the following folder on your computer, depending on your version of Windows:

32-bit Windows
C:\Program Files\Articulate\360\Storyline\Content\scormdriver_v7

64-bit Windows
C:\Program Files (x86)\Articulate\360\Storyline\Content\scormdriver_v7

2. Open the scormdriver.js file in a text editor, such as Notepad.

3. Find "goodbye.html" and replace it with "lms/goodbye.html" (including the quotes).

4. Save and close the scormdriver.js file.

5. If you've customized the goodbye.html file, you also need to copy and paste your custom goodbye.html file into the folder from step 1 above. If you haven't customized the goodbye.html file, you can skip this step.

Then republish your course and upload it to your LMS. Let me know if that solves the problem.

Hi all, 

Good news! We released an update for Storyline 360 that fixes the 404 error you recently reported.

If you already fixed your courses using the instructions from Leslie, you don’t need to republish those courses. The latest update prevents the 404 error from happening in courses that you publish from this point forward.

Let us know if you have any questions. We're happy to help!

Awesome!!!!

Sent from Mail for Windows 10

Hi all,

A quick update for you regarding the goodbye.html file. The latest update (Update 41) of Storyline moves the goodbye.html file back to its original location in your program files. If you’ve customized the goodbye.html file for your Storyline courses, you’ll need to copy and paste your custom file into the following folder on your computer after installing the latest Storyline 360 update.

32-bit Windows
C:\Program Files\Articulate\360\Storyline\Content\lms

64-bit Windows
C:\Program Files (x86)\Articulate\360\Storyline\Content\lms

See this article for details on customizing the goodbye.html file: https://articulate.com/support/article/Storyline-360-Customizing-or-Suppressing-the-Goodbye-html-Page

Let us know if you have any questions. We're happy to help!