Sounds like it could be a local security restriction causing the problem. If you view published Storyline content on your local hard drive or send it to someone else to view on their local hard drive, you'll encounter security restrictions from the computer, web browser, Flash Player, and network that'll cause various features of your content to fail.
To properly test your published content and share it with others, upload it to the environment for which it was published. This article has all the details. Let us know if that resolves it, or if you have any questions.
Does the SWF contain AS3 or AS2? If AS2, some problems could arise. You'll normally only see security sandbox issues when the SWF attempts to communicate with the browser. You can isolate this by publishing to CD. If it runs from the EXE (still published as HTML but wrapped in a local player) then it's quite likely that the security sandbox is the cause. If not, there's something else afoot.
2 Replies
Hey Mark, welcome to the forums!
Sounds like it could be a local security restriction causing the problem. If you view published Storyline content on your local hard drive or send it to someone else to view on their local hard drive, you'll encounter security restrictions from the computer, web browser, Flash Player, and network that'll cause various features of your content to fail.
Hi Mark,
Does the SWF contain AS3 or AS2? If AS2, some problems could arise. You'll normally only see security sandbox issues when the SWF attempts to communicate with the browser. You can isolate this by publishing to CD. If it runs from the EXE (still published as HTML but wrapped in a local player) then it's quite likely that the security sandbox is the cause. If not, there's something else afoot.
This discussion is closed. You can start a new discussion or contact Articulate Support.