Next button hangs for one slide

Jul 29, 2015

I am able to use the next and previous buttons for the first 4 slides, then using next to go to the first slide in the next scene, the player hangs and the spinner won't stop spinning. However, if I click on the 6th slide from the menu, it will advance and then I can use the next and previous buttons to navigate correctly. I have the story in Canvas, and have tried fifty times to tweak and overcome this issue. It works locally, but when I load to Canvas, this error happens every time. Any assistance will be greatly appreciated.

11 Replies
James Means

Wendy,

I'm sorry I didn't think of that last night (it was very late).  I will try to get a stripped down version posted as soon as I can.  Thank you for pointing that out.  :-)

Nancy,

I have had the triggers set both ways... and neither one worked.  By the way, is there a best practices method for jumping to the next scene?  If there is I would like to know.  Still relatively new to Storyline.  :-)

One thought.  There is another learning module posted in Canvas that works fine.  I have compared all of the files between that module and the one that isn't working and can find no differences.  Is it possible that the other one works because it was created in Storyline 1 and the one not working was created in Storyline 2?  Maybe a bug with 2 not working well in Canvas?

Thank you VERY much for your replies... I am on team of people trying to get these modules up for the UF School of Medicine and things are going down hill quick.

 

 

James Means

Thank you all very much!!

We are being assisted by Articulate at this time.  They were able to run the Storyline file just fine in one of their LMS's that they use.... unsure if it was Canvas or not..... They could not see anything wrong with how the file was published.   So we are still trouble shooting.  :-(

I will update if we find out what the problem is.  It could be the Canvas build UF is using, or it could that something isn't turned on in Canvas at UF.  Our IT department is just getting the whole university up and running with Canvas as they just made the switch from their old LMS.

Sincerely,

James

 

James Means

Thank you for your reply!

Did a little digging and found that Storyline 2 is generating java script errors.  I do not know enough about java scripting to understand why the errors occur, but I see that Instructure is trying access files from an Amazon Cloud service and the UF LMS is not going to allow it.

Here are the errors occurring when Storyline freezes:

 instructure-uploads.s3. amazonaws.com/account_ 10160000000002010/attachments/ …hment%3B%20filename%3D%22lms. js%22%3B%20filename%2A%3DUTF- 8%27%27lms.js:28 Uncaught SecurityError: Blocked a frame with origin "https://cluster30-files. instructure.com" from accessing a frame with origin "https://ufl.instructure.com". Protocols, domains, and ports must match.

lms.js?AWSAccessKeyId= AKIAJFNFXH2V2O7RPCAA&Expires= 1438694062&Signature= jDjxxu4DWnSjjvtpaqmDk1jvK0I…: 28 Uncaught SecurityError: Blocked a frame with origin "https://cluster30-files. instructure.com" from accessing a frame with origin "https://ufl.instructure.com". Protocols, domains, and ports must match

Can anyone figure out what Storyline is trying to do that Canvas won't allow?

Thank you all!

James

 

James Means

Well,

Got it mostly figured out.

When using Canvas equipped with SCORM, you cannot load Storyline files into your course without loading your files into the SCORM folder as a SCORM Package.  Even if it is not a graded assignment.... this I did not know until reading through volumes of info on the Canvas website and other discussion forums.... seems like you should be able to load up a Storyline file that is for training only and not graded directly into your course site files, but this is not so.

I even tried publishing only for web with Storyline and Canvas still didn't like that.

At any rate, thank you all for responding.   Hopefully someone who might be having the same problem will stumble upon this thread.

Oh, and by the way, the java script errors were all from SCORM trying to access files that weren't there because I didn't load them in the right place!  :-)  User error on that one.

James

 

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