I am trying to insert Captivate simulations as web objects. I want them to launch in a new browser window. When I insert them and test the link, they work. However, when I published and sent it for upload to our LMS, we got the attached errors. And the simulations were blank pages.
There used to be a tutorial around here, I can't remember but I think Steve Flowers may have posted it, but it outlined a pretty cool way to get Storyline to create folders and include content for web objects in your published output automatically.
They are on my laptop. I am navigating to the folder which contains my Index.html file (and the .swf and .js files too - they're all in the same folder).
They are on my laptop. I am navigating to the folder which contains my Index.html file (and the .swf and .js files too - they're all in the same folder).
Ok, then this is probably the problem.
You need to make sure that your captivate files are being uploaded to a web server location and that your web object is pointing to the http URL for that location.
If you're updating an existing course that is working in your LMS already, you may try figuring out the http location of the existing captivate files and use that in your updated course.
Hi Linda - I'd say that's a possible cause. Depends on the LMS / Server setup. If it launches fine when tested outside of the LMS, this seems like a strong possibility.
11 Replies
Hi Linda!
Are your captivate files uploaded to a web server? If so, when you create your web object are you using the http URL to point to the captivate files?
There used to be a tutorial around here, I can't remember but I think Steve Flowers may have posted it, but it outlined a pretty cool way to get Storyline to create folders and include content for web objects in your published output automatically.
If I can find it I'll post it here...
Hi Brian,
They are on my laptop. I am navigating to the folder which contains my Index.html file (and the .swf and .js files too - they're all in the same folder).
What's weird is, I'm updating and translating an existing e-learning and everything worked fine before.
Ok, then this is probably the problem.
You need to make sure that your captivate files are being uploaded to a web server location and that your web object is pointing to the http URL for that location.
If you're updating an existing course that is working in your LMS already, you may try figuring out the http location of the existing captivate files and use that in your updated course.
Brian, do you think the Portuguese characters in a file name would cause this? For example: Atividade – Acessar uma Transação.swf.
Brian, I didn't have to do that before. Is this a new requirement for Storyline 2?
I'm not familiar enough to say with any authority, but I would definitely test it without special characters and see if that fixes the issue for you.
Hi Linda - I'd say that's a possible cause. Depends on the LMS / Server setup. If it launches fine when tested outside of the LMS, this seems like a strong possibility.
Hi,
When I removed the Portuguese punctuation characters from the file names, we were able to load the published e-learning, and it works.
Do you have a lot of users in Portugal and Brazil?
Hi Linda,
I don't know the exact numbers but suspect we do - but including the characters in the file name/path is an issue documented here for Windows as well.
This discussion is closed. You can start a new discussion or contact Articulate Support.