Hi I have built a Rise 360 course and used some activities from Storyline. I have published to Review 360 with no issues and now it is coming up with this error message instead of the Storyline activities. window.THREE = { };
I have not changed the activities recently and the course worked perfectly in Review 360 last week.
No it is fine in Rise 360 and when I preview it in that. It was when I published it to Review 360 for people to review and provide feedback. The issue was it was fine after being published last and today the error message came up. I have managed to fix it by uploading the Storyline activities again and republishing but it did take a few times of deleting and updating as well as several times re-publishing to get all the storyline activities to work. Sometimes one or two worked and one wouldn't. There was no real reason I could work out for the issue.
We use Chrome as the browser and advise everyone else t use that. I also cleared the cache & cookies. That made no difference.
Thank you for the clarification. I am sorry you had to reupload the Storyline activities. If you experience this again, please open a case here. We would love to take a closer look.
Quick note - when you reply via email, it includes your email signature with contact information in the public discussion. You can edit it out of the post here if you wish!
I'm having this same issue. My Rise course has 11 Storyline files in it and despite re-uploading the files and re-exporting the SCORM roughly 20 times already, it still is having issues. It seems to be completely random.
In today’s update for Rise 360, we fixed the issue where some Storyline blocks weren’t loading in Review 360 and Rise 360 courses. You can preview your Rise course in Review 360, or export for web or LMS again, and everything should work as expected.
8 Replies
Hi Margaret,
I am here to help.
Do you see window.THREE = { }; directly in Rise 360, or is it in a course that has been exported and loaded into an LMS or web server?
Have you tried using a different browser such as Google Chrome or Firefox? For the best results, make sure that your browser is fully updated.
Hi Chino
No it is fine in Rise 360 and when I preview it in that. It was when I published it to Review 360 for people to review and provide feedback. The issue was it was fine after being published last and today the error message came up. I have managed to fix it by uploading the Storyline activities again and republishing but it did take a few times of deleting and updating as well as several times re-publishing to get all the storyline activities to work. Sometimes one or two worked and one wouldn't. There was no real reason I could work out for the issue.
We use Chrome as the browser and advise everyone else t use that. I also cleared the cache & cookies. That made no difference.
Hi Margaret,
Thank you for the clarification. I am sorry you had to reupload the Storyline activities. If you experience this again, please open a case here. We would love to take a closer look.
Quick note - when you reply via email, it includes your email signature with contact information in the public discussion. You can edit it out of the post here if you wish!
I'm having this same issue. My Rise course has 11 Storyline files in it and despite re-uploading the files and re-exporting the SCORM roughly 20 times already, it still is having issues. It seems to be completely random.
Hi Casey,
I can see that you created a case and are working with our Support engineer Sheila. You are in good hands.
Yes, I am also having this issue. Sometimes the error shows in Review, sometimes in my LMS. I also have a support case in progress.
Thank you, Sue. Our team is hard at work implementing a fix for this issue. As soon as it is resolved, we will let you know!
Hi All!
In today’s update for Rise 360, we fixed the issue where some Storyline blocks weren’t loading in Review 360 and Rise 360 courses. You can preview your Rise course in Review 360, or export for web or LMS again, and everything should work as expected.
Have a great day!
This discussion is closed. You can start a new discussion or contact Articulate Support.