Issue loading SWF SL file into Dreamweaver HTML
May 21, 2012
By
Laura Rogers
Hi,
I created a Storyline interaction, published the web, and then tried to put the .swf output file into a Dreamweaver HTML page (the same process I followed with Studio '09 to add quizzes to Dreamweaver HTML).
I'm getting some errors. First I get a "Content on this page requires a new version of Adobe Flash Player." With an option to download "Active X controls" on top of page. I do that, and get the error attached - saying the file can't access the story_content/data.swf file.
Any ideas on how I can fix this?
Thanks,
Laura Takach
8 Replies
PS - I am using flash player 10, and Internet Explorer 8 - company settings.
Hi Laura,
Did you publish to HTML5, by any chance? SWF (Flash) files are not supported in HTML5 content.
Hi Peter,
No, I did not. I unselected "Include HTML 5 output" in the publish menu, and I'm definitely not using HTML5 in Dreamweaver.
Any other things to check?
Thanks,
Laura
Hi Laura,
Would you like to submit a case to our support team? They'd be happy to work with you to find a solution for this.
Thanks, Peter!
Sure thing, Laura! I'll keep an eye on it so I can follow up with you here in the forums.
hello, has there been any resolution this besides using an iframe?
Hi Rob,
It looks like Laura's case was closed and the final email from Jayem is included below for you:
If you publish your content for Web or LMS, but you view the content directly from your local drive or a network drive, this may cause the ActiveX pop-up and other unexpected behaviors. This is due to web browser and Flash Player security restrictions. To accurately test your published output, you can try the following methods:
1. Publish for CD. If you simply want to test the functionality of your content offline you should publish for CD and select View Presentation at the end of the publishing wizard. If you plan on distributing the content offline then you should also publish for CD. If someone else needs to view the content they should do so by double clicking the EXE file.
2. View the content in the environment it will be hosted in. To truly test the functionality of your content we recommend testing the content in the environment it will be in when it is live. So if you are publishing for LMS, test the content in your LMS. If you are publishing for the Web, test the content on a web server via a valid HTTP address.
Regarding your other concern, unfortunately, the workaround we provided for embedding Storyline projects to HTML is provided as is. ( I believe the workaround Jayem is referring to is this one he mentioned in an earlier email) I suggest consulting our community forums for further information on this.
This discussion is closed. You can start a new discussion or contact Articulate Support.