E-Learning Heroes - Advice and ideas from the Articulate Community

Hello everyone,

..I have tried to insert a web object into storyline and it does not work.

The web object is flash and bundled in a folder structure. To start it I have an index.html file and it works fine in my browser.

When I test the link the web object opens normally, however I have to tell my browser to start this potentially dangerous content.

When I than publish and start the WBT the page is empty and the web object not displayed.

Does this have to do with the security settings or is there anything I have to check?

Ah and by the way, when I than go into the source files of the course, I find the web object and can play it from there.

Any ideas or help?

Best regards,

Max

PS.: Storyline is awesome and I am really excited about the coming month of work because of it

Hi Brian,

thanks for the advice and the warm welcome. You were perfectly right It all runns on the LMS.

Thanks a lot!

I'm now having this same problem with web objects in Storyline but it doesn't appear to be any of the problems described in the article at Brian's link. 

• I'm testing by adding a web object to a slide going to google and it's not working locally or on Moodle. 
• Weird thing is that I used web objects in a different project last week that are working fine.  I didn't do anything different for the web objects that are working. When I open last weeks project the web objects are still working fine.  Just can't get them to work in any new projects.
• I attached my story file and the published package for reference.

It seems that web objects magically stopped working for me in Storyline. Thanks in advance for your help.

Hey Joe,

I published your course to the Web. When I tried to open it in Chrome I got crickets. HOWEVER, when I opened it in IE, I got this below. I then added a slide with a different URL...try opening this file.

Tricia nailed it.  Many websites like Google don't want their content in a frame.  So, they change the "x-frame-options" tag to DENY to prevent that:

https://developer.mozilla.org/en-US/docs/The_X-FRAME-OPTIONS_response_header

Some browsers like Chrome will just display a blank page.  Other browsers will actually give the end-user a reasonable error message.  

Wow...I just got a "nailed it" from Brian! My day is complete and Elvis has left the building!