Dear colleagues, Today I share with you an unsolved mystery: One of our students got this message from Articulate: "The function of this slide was deactivated while looking locally because the browser does not allow it." (literal translated) The message is in spanish and I attached the screnshot that our student sent us. My proposed solution was to delete the cache files, but I would like to know why this happened and how to prevent it from appearing again.
You can get this error if you publish for LMS and attempt to access the story from a network or local drive.
Sopmetimes you can get this error if you publish for the web and attempt to access the story from a network or local drive.
It is almost always safe to publish for the web, and put the story on a web server, or publish to CD and access it locally or even from a network. The projects really do work best when they are published for a specific environment and accessed from that environment.
How have you published this course and where are you hosting it to share with users? As Walt mentioned that error message is common when you've published for Web or LMS and users are playing it back locally from their desktop, or if the published files are stored in a network drive.
It's exported as LMS SCORM 1.2 und uploaded on a Moodle platform. And this moodle platform is online and for public acces... so I do not understand how the users could play it back locally.
4 Replies
You can get this error if you publish for LMS and attempt to access the story from a network or local drive.
Sopmetimes you can get this error if you publish for the web and attempt to access the story from a network or local drive.
It is almost always safe to publish for the web, and put the story on a web server, or publish to CD and access it locally or even from a network. The projects really do work best when they are published for a specific environment and accessed from that environment.
Hi Eli,
How have you published this course and where are you hosting it to share with users? As Walt mentioned that error message is common when you've published for Web or LMS and users are playing it back locally from their desktop, or if the published files are stored in a network drive.
There's a bit more detail about this here, and some additional methods for publishing and sharing your content.
It's exported as LMS SCORM 1.2 und uploaded on a Moodle platform.
And this moodle platform is online and for public acces... so I do not understand how the users could play it back locally.
Hi Eli,
Have you been able to recreate this error message in your own testing?
Since this problem is happening on Moodle, I'd be curious to find out whether you encounter the same issue in another LMS.
Have you tried testing the output on SCORM Cloud? Let me know if you'd like some help with that!
This discussion is closed. You can start a new discussion or contact Articulate Support.