I have uploaded a Storyline file into Moodle 2.2 as a SCORM package. On the last slide I have included links to the course main page and to the Exit Activity link in Moodle.
I was hoping that the Exit Activity link would close the Stoyline file and return to the Moodle course page. Is there any way I can return to the course page without it opening up in a new window?
As you mentioned this thread is a bit older, and I'm not certain folks are still subscribed. In regards to what you set up, is the web object the Moodle site or something similar? Could you share an example here to let the community take a look at what you've set up? Have you also reached out to the Moodle team for assistance?
I have used this technique with success two years ago on a Moodle's site. Now, when I use the same method again using SL2, it no longer works. Can someone help to make this work?
Have you checked in on which version of Moodle you're using? I know they're also regularly updating so it may be that the solution shared here doesn't play well with the latest from both Storyline and Moodle.
I am on Moodle 2.5. The course I developed two years ago is also hosted on this platform and this exit course method still works. But with the new course I am developing using SL2, the method does not work. It just stays on the last page of the course and does not exit the SCORM to go back to the Moodle's webpage. I wonder if it's a SL2 issue. Have you used this method successfully in SL2?
I don't use Moodle and it seems this set up was something a user created as a custom behavior - so I can't speak to how it works in SL2 or not. It seems Tim was the last user to respond here, and I don't see any updates from him. Perhaps reaching out to him directly he could tell you where things stand on his end?
Alice is correct. This worked fine on Storyline 1 and does not work when those files are republished in Storyline 2. It is not related to Moodle as I have loaded the old files onto a new moodle site and they work while new files on the old moodle site do not.
sorry when I say does not work, it does not work the way it did in Storyline 1. I used to be able to control the web object on a layer and now it starts immediately regardless what layer it is on or whether that layer is called.
Thank you Tim for sharing your experience. It's too bad that this method does not work in SL2. This will definitely cause navigation issues with our users.
Thanks Tim - as I read back through this thread it seems to involve a modification of the index.html file which is a part of the published output. That's not something I can assist with so I'd have to defer to the community regardless for additional insight and work here.
Actually for me it is not about the index file. That part of the web objectvis working fine. My problem is about when web objects run in Storyline2. In Storyline 1 I could run a web object on a layer and not call it until then. In Storyline 2 web objects now run immediately regardless whether they are on a layer that has been called or not.
I may not be understanding your set up than. I don't have an issue with the web object appearing on the base layer if I haven't accessed the layer where it exists yet. For example, I set up a really simple file - where the layer is set to show after about 5 seconds and there is a web object there just linking to the Articulate site. I uploaded it to SCORM Cloud here. Everything works normally there. If you've got a different set up that is behaving inconsistently are you able to test it at SCORM Cloud or share it here with us? I ask, as it's an industry standard for testing SCORM content and you can read more about testing files there in this article.
35 Replies
Hi Tim,
As you mentioned this thread is a bit older, and I'm not certain folks are still subscribed. In regards to what you set up, is the web object the Moodle site or something similar? Could you share an example here to let the community take a look at what you've set up? Have you also reached out to the Moodle team for assistance?
I have used this technique with success two years ago on a Moodle's site. Now, when I use the same method again using SL2, it no longer works. Can someone help to make this work?
Thanks
Hi Alice,
Have you checked in on which version of Moodle you're using? I know they're also regularly updating so it may be that the solution shared here doesn't play well with the latest from both Storyline and Moodle.
Hi Ashley,
I am on Moodle 2.5. The course I developed two years ago is also hosted on this platform and this exit course method still works. But with the new course I am developing using SL2, the method does not work. It just stays on the last page of the course and does not exit the SCORM to go back to the Moodle's webpage. I wonder if it's a SL2 issue. Have you used this method successfully in SL2?
Hi Alice,
I don't use Moodle and it seems this set up was something a user created as a custom behavior - so I can't speak to how it works in SL2 or not. It seems Tim was the last user to respond here, and I don't see any updates from him. Perhaps reaching out to him directly he could tell you where things stand on his end?
Hey Ashley;
Alice is correct. This worked fine on Storyline 1 and does not work when those files are republished in Storyline 2. It is not related to Moodle as I have loaded the old files onto a new moodle site and they work while new files on the old moodle site do not.
sorry when I say does not work, it does not work the way it did in Storyline 1. I used to be able to control the web object on a layer and now it starts immediately regardless what layer it is on or whether that layer is called.
Tim
Thank you Tim for sharing your experience. It's too bad that this method does not work in SL2. This will definitely cause navigation issues with our users.
Thanks Tim - as I read back through this thread it seems to involve a modification of the index.html file which is a part of the published output. That's not something I can assist with so I'd have to defer to the community regardless for additional insight and work here.
Ashley;
Actually for me it is not about the index file. That part of the web objectvis working fine. My problem is about when web objects run in Storyline2. In Storyline 1 I could run a web object on a layer and not call it until then. In Storyline 2 web objects now run immediately regardless whether they are on a layer that has been called or not.
Tim
Hi Tim,
I may not be understanding your set up than. I don't have an issue with the web object appearing on the base layer if I haven't accessed the layer where it exists yet. For example, I set up a really simple file - where the layer is set to show after about 5 seconds and there is a web object there just linking to the Articulate site. I uploaded it to SCORM Cloud here. Everything works normally there. If you've got a different set up that is behaving inconsistently are you able to test it at SCORM Cloud or share it here with us? I ask, as it's an industry standard for testing SCORM content and you can read more about testing files there in this article.
This discussion is closed. You can start a new discussion or contact Articulate Support.