Hi, we are having the same problem on all courses that run on Moodle, using the "launch in new window":
if you have set an "exit course" trigger on a label in the player, when testing, if you click that button (and wait) nothing happens the first time, but you must click a second time to close the window and return to LMS.
Thank you Christine for suggestion, scorm is correctly packaged and we decided to include the exit functionality because sometimes exiting with the close button of the window it generated randomly a "missing scoID" error.
I tested also on SCORM cloud, and the close trigger works fine on the frst click. It seems something related to Moodle when the activity is opened in a new window.
I examined storyline dedicated funcions by viewing the various js file published. When the scorm try to estabilish a connection to LMS it makes several attempts using different path (same window, parent window, etc.) so it seems like it happens something similar when you try to exit the course, like if a first attempt tried to close communication on a wrong path for the LMS core, and then failed and stopped, then when clicked again, he finds the right parameters (but mine is just an hypotesis)
It sounds like the issue is Moodle-specific, if it's working in SCORM Cloud correctly. It may help to start a new thread and include "Moodle" in the title, so our community members with Moodle experience can take a look and share their suggestions.
I still recommend reaching out to Moodle, if you haven't already done so as well. Even if they don't have a solution, it would be good to ensure that they're aware of the issue and can look into it.
I don't recall hearing about this before - I couldn't see any reference to the Moodle version you are using either - make sure you're using a recent supported stable release.
7 Replies
Hi Zio,
Do you know if this is specific to Moodle, or have you tested this on a different server?
I think this blog post is the place to begin. You also want to be certain that you are packaging your published content properly for your LMS. Also, be certain that you have contacted the Support Team for your LMS, since they are best-equipped to tell you whether or not that type of behavior is expected when using a launch page with content hosted through Moodle.
If you wind up empty-handed after reviewing the links above, I would next recommend comparing the performance of your content at SCORM Cloud. If you cannot reproduce the problem there, this is likely an LMS-specific issue, and you will want to generate debug logs and supply them to your LMS Provider for additional troubleshooting.
Please let us know how it goes!
Best,
Christine
Thank you Christine for suggestion, scorm is correctly packaged and we decided to include the exit functionality because sometimes exiting with the close button of the window it generated randomly a "missing scoID" error.
I tested also on SCORM cloud, and the close trigger works fine on the frst click. It seems something related to Moodle when the activity is opened in a new window.
I examined storyline dedicated funcions by viewing the various js file published. When the scorm try to estabilish a connection to LMS it makes several attempts using different path (same window, parent window, etc.) so it seems like it happens something similar when you try to exit the course, like if a first attempt tried to close communication on a wrong path for the LMS core, and then failed and stopped, then when clicked again, he finds the right parameters (but mine is just an hypotesis)
searching the forum i founded a suggestion in this page
http://www.articulate.com/support/storyline/exit-course-trigger-does-not-work
that says:
To: var EXIT_BEHAVIOR = “ALWAYS_CLOSE”;
If it still doesn't work, try changing the line in step 3 to: var EXIT_BEHAVIOR = “ALWAYS_CLOSE_TOP”;
i tried using both "ALWAYS_CLOSE" and "ALWAYS_CLOSE_TOP" with no different results.
Hi Zio,
It sounds like the issue is Moodle-specific, if it's working in SCORM Cloud correctly. It may help to start a new thread and include "Moodle" in the title, so our community members with Moodle experience can take a look and share their suggestions.
I still recommend reaching out to Moodle, if you haven't already done so as well. Even if they don't have a solution, it would be good to ensure that they're aware of the issue and can look into it.
Let us know if you find anything!
Best,
Christine
I don't recall hearing about this before - I couldn't see any reference to the Moodle version you are using either - make sure you're using a recent supported stable release.
Good idea, Dan - thanks for the suggestion!
Let us know how that goes, Zio - or let us know which version your using for Moodle.
Thanks!
Christine
This discussion is closed. You can start a new discussion or contact Articulate Support.