I'm trying to add a demo to a lesson. the demo was made in Captivate 6. I published my Captivate as SWF/HTML5. Unfortunately, it will not play in the published SL file. Any suggestion regarding how to make this work.
Hi Kim, here is a sample of a Captivate 6 demo running inside a Storyline file. I added the Captivate swf to the Storyline slide and that worked fine for me. Another option would be to use a webobject to display the HTML file that contains the Captivate demo. What happens in your project? Do you see a blank screen instead of the Captivate demo?
You got it, I just see a blank screen. I tried adding the Captivate URL to a slide within my SL file. I see that was wrong. This produced a blank screen. I just added the Captivate swf file and got a page telling me to actiavte Adobe Flash. Not sure why as I've had to update Flash and use Firefox in order to view my published SL course.
I'll look for a tutorial on creating/adding web objects. I'm hopiing that will be the answer for me. I'll let you know what happens.
You got it, I just see a blank screen. I tried adding the Captivate URL to a slide within my SL file. I see that was wrong. This produced a blank screen. I just added the Captivate swf file and got a page telling me to actiavte Adobe Flash. Not sure why as I've had to update Flash and use Firefox in order to view my published SL course.
I'll look for a tutorial on creating/adding web objects. I'm hopiing that will be the answer for me. I'll let you know what happens.
Please point me in the direction for tutorials for inserting external elements into a course. I'm searching for steps for creating web objects and so on but am not finding what I need. Thanks.
I continue to have problems and I'm wondering if the issue is SL or if it is my working platform. I'm getting close to the end of my day, but I'll return to this matter tomorrow and let you know what happens.
I continue to have problems and I'm wondering if the issue is SL or if it is my working platform. I'm getting close to the end of my day, but I'll return to this matter tomorrow and let you know what happens.
Kim, if you can share your file(s) here, we could have a look and test it.
I'm so confused as to why my links don't work. I'm attaching a file that has two great examples of my problems. Slide 1.8 contains a Web Object and, when the Demo graphic is clicked, it's supposed to launch a published Captivate. Slide 1.9 contains two URL links that when clicked should open new windows and take the learner to the content.
BTW, not sure if this 2nd issue is part of the first, but my Articulate doesn't play in IE--but my published Captivate, as a stand alone object, will--, will sometimes play in Firefox, and is usually stable in Goggle. Honestly, I need for SL to play in all three browsers, especially IE. I plan to post this issue if I don't locate previously cited literature.
Any insight you can provide will be greatly appreciated.
Hi Kim, I had a look at your file and found a few things that needed to be fixed.
On slide 1.8: The Demo button didn't have a trigger to display/launch a web object or external URL. I don't know how you managed to do that, because in the timeline the button shows as a web object. I recreated that button and added a trigger to launch the Captivate demo in a new window.
On slide 1.9: the link to the Change Management page was enclosed in <> tags, I removed those.
Here is a test (I didn't publish my test for LMS/HTML5, just as plain web). Have a look and let me know if that test file fixes your issues with links, Captivate demo. BTW, I also tested this in Chrome and the links worked.
Following Michael's lead, I removed the <> for any links and recreated the DEMO button for the web object so it triggers properly. I published using the LMS and the WEB options and I still can't get my course to run properly in the various browsers. I'm not sure if the issue is Articulate or my work environment. Not sure what my next steps should be.... so discouraged!
Following Michael's lead, I removed the <> for any links and recreated the DEMO button for the web object so it triggers properly. I published using the LMS and the WEB options and I still can't get my course to run properly in the various browsers. I'm not sure if the issue is Articulate or my work environment. Not sure what my next steps should be.... so discouraged!
Kim, don't give up! As a next step, I would upload the course to SCORM Cloud and test if it works from there.
Michael you are a fountain of great information. I did upload to SCORM Cloud, great resource by the way, and it uploaded fine with no errors found. When launched via that application I was able to view it in IE. The only thing that didn't work was the Captivate demo. While I now have some answers to my issues I've also have more questions.... ! However, it is a relief to know that I'm not the source of the problems with my final product and that I'm "getting" SL.
With your insight, I'm starting the think that my real problem is internal and something in my environment is preventing the course from launching properly. I hope to have an update for you once I track an internal help resource. Thanks again, you've given me new resolve to make this work.
Hi Kim, I just republished my test file to SCORM Cloud and ran it ( Ican send you the link if you want). The Captivate demo comes up, the other URL link works and the course tracks completion. That got me thinking about the Captivate demo not being displayed in your test: Make sure that you MANUALLY copy all the folders and files that makes up your Captivate demo (I highlighted them below) into the '\story_content\external_files' directory. These files are NOT copied automatically during publishing. My apologies if I'm stating the obvious here, but I forget about this issue constantly, it's not funny anymore
Great advice. I'll make the update and see what happens. I didn't think to copy in all the support files in the external output as I thought by adding the path would automatically trigger those actions.
Here's another question, as I'm trying to figure out what's happening with SL in my work environment, I was told that during the vetting process with the SW, it was determined that:
·When content is exported, the manifests do have to be manipulated to remove the SumTotal player. We do have steps for this, that we can provide you.
Unfortunately, I haven't been able to contact the person who made this determination but I'm at a loss to determine how the player would impact SL's ability to launch in IE .... I'm researching SumTotal Players through the Articulate community hoping to determine what meaning this could have for me. Any insight that you can share would be helpful.
Great advice. I'll make the update and see what happens. I didn't think to copy in all the support files in the external output as I thought by adding the path would automatically trigger those actions.
Here's another question, as I'm trying to figure out what's happening with SL in my work environment, I was told that during the vetting process with the SW, it was determined that:
·When content is exported, the manifests do have to be manipulated to remove the SumTotal player. We do have steps for this, that we can provide you.
Unfortunately, I haven't been able to contact the person who made this determination but I'm at a loss to determine how the player would impact SL's ability to launch in IE .... I'm researching SumTotal Players through the Articulate community hoping to determine what meaning this could have for me. Any insight that you can share would be helpful.
Hi Kim, I don't have any experience with SumTotal, but I wouldn't be surprised if the LMS player somehow interferes with the Storyline content. From (painful) experience with other LMSs I know that while an LMS may be 'SCORM-compliant', there are often caveats and 'gotchas' that may require additional steps or edits of the manifest file, Javscript bits, etc.
I didn't have to manually move the CP support files in SL's external folder. When I added the CP into SL (slide 1.8) I selected the CP zip file and, once published, I checke the external files folder and all of the necessary support files were there. In all honesty I can't say that previous uploads to CP were done accurately as I didn't check the external files before. However, this is the first time that I was asked to choose how to open a file.
Bewildering!
I've uploaded the latest versions of my published CP and SL files, I'm just confused as to what's happening. Please if you could, send me your SCORM test file. There has to be something that I'm missing. I'm stepping away from this tonight. Will revisit tomorrow morning. Thanks for all of the help so far.
42 Replies
Hi Kim, here is a sample of a Captivate 6 demo running inside a Storyline file. I added the Captivate swf to the Storyline slide and that worked fine for me. Another option would be to use a webobject to display the HTML file that contains the Captivate demo. What happens in your project? Do you see a blank screen instead of the Captivate demo?
You got it, I just see a blank screen. I tried adding the Captivate URL to a slide within my SL file. I see that was wrong. This produced a blank screen. I just added the Captivate swf file and got a page telling me to actiavte Adobe Flash. Not sure why as I've had to update Flash and use Firefox in order to view my published SL course.
I'll look for a tutorial on creating/adding web objects. I'm hopiing that will be the answer for me. I'll let you know what happens.
Thanks Michael!
Kim, here is some info on Web objects.
Please point me in the direction for tutorials for inserting external elements into a course. I'm searching for steps for creating web objects and so on but am not finding what I need. Thanks.
Kim
Hi Kim! Looks like Michael is taking care of you here, just let us know if you need anything further.
Michael,
thanks for the link. I'll review and hopefully try and follow the directions. Will let you know what happens (fingers crossed)
Anytime Kim
Sounds great Kim, thanks for the update
Thanks Michael!
I continue to have problems and I'm wondering if the issue is SL or if it is my working platform. I'm getting close to the end of my day, but I'll return to this matter tomorrow and let you know what happens.
Kim, if you can share your file(s) here, we could have a look and test it.
I'm so confused as to why my links don't work. I'm attaching a file that has two great examples of my problems. Slide 1.8 contains a Web Object and, when the Demo graphic is clicked, it's supposed to launch a published Captivate. Slide 1.9 contains two URL links that when clicked should open new windows and take the learner to the content.
BTW, not sure if this 2nd issue is part of the first, but my Articulate doesn't play in IE--but my published Captivate, as a stand alone object, will--, will sometimes play in Firefox, and is usually stable in Goggle. Honestly, I need for SL to play in all three browsers, especially IE. I plan to post this issue if I don't locate previously cited literature.
Any insight you can provide will be greatly appreciated.
Ooops, here's the published file.
BTW, the Web Object tutorial was really easy to follow. Thanks for that link.
Hi Kim, I had a look at your file and found a few things that needed to be fixed.
On slide 1.8: The Demo button didn't have a trigger to display/launch a web object or external URL. I don't know how you managed to do that, because in the timeline the button shows as a web object. I recreated that button and added a trigger to launch the Captivate demo in a new window.
On slide 1.9: the link to the Change Management page was enclosed in <> tags, I removed those.
Here is a test (I didn't publish my test for LMS/HTML5, just as plain web). Have a look and let me know if that test file fixes your issues with links, Captivate demo. BTW, I also tested this in Chrome and the links worked.
Hi Kim! Looks like Michael has stepped in to assist again
Thanks Michael!
Micheal.... THank you so much! I was going crazy trying to find my error. I appreciate the assist!
Great! Glad Michael was able to help you out Kim and thanks for the update
Following Michael's lead, I removed the <> for any links and recreated the DEMO button for the web object so it triggers properly. I published using the LMS and the WEB options and I still can't get my course to run properly in the various browsers. I'm not sure if the issue is Articulate or my work environment. Not sure what my next steps should be.... so discouraged!
Kim, don't give up! As a next step, I would upload the course to SCORM Cloud and test if it works from there.
Michael you are a fountain of great information. I did upload to SCORM Cloud, great resource by the way, and it uploaded fine with no errors found. When launched via that application I was able to view it in IE. The only thing that didn't work was the Captivate demo. While I now have some answers to my issues I've also have more questions....
! However, it is a relief to know that I'm not the source of the problems with my final product and that I'm "getting" SL.
With your insight, I'm starting the think that my real problem is internal and something in my environment is preventing the course from launching properly. I hope to have an update for you once I track an internal help resource. Thanks again, you've given me new resolve to make this work.
Awesome! Thanks for the update Kim.
Thanks Michael!
Hi Kim, I just republished my test file to SCORM Cloud and ran it ( Ican send you the link if you want). The Captivate demo comes up, the other URL link works and the course tracks completion. That got me thinking about the Captivate demo not being displayed in your test: Make sure that you MANUALLY copy all the folders and files that makes up your Captivate demo (I highlighted them below) into the '\story_content\external_files' directory. These files are NOT copied automatically during publishing. My apologies if I'm stating the obvious here, but I forget about this issue constantly, it's not funny anymore
Great advice. I'll make the update and see what happens. I didn't think to copy in all the support files in the external output as I thought by adding the path would automatically trigger those actions.
Here's another question, as I'm trying to figure out what's happening with SL in my work environment, I was told that during the vetting process with the SW, it was determined that:
· When content is exported, the manifests do have to be manipulated to remove the SumTotal player. We do have steps for this, that we can provide you.
Unfortunately, I haven't been able to contact the person who made this determination but I'm at a loss to determine how the player would impact SL's ability to launch in IE .... I'm researching SumTotal Players through the Articulate community hoping to determine what meaning this could have for me. Any insight that you can share would be helpful.
Hi Kim, I don't have any experience with SumTotal, but I wouldn't be surprised if the LMS player somehow interferes with the Storyline content. From (painful) experience with other LMSs I know that while an LMS may be 'SCORM-compliant', there are often caveats and 'gotchas' that may require additional steps or edits of the manifest file, Javscript bits, etc.
Bewildering!
I've uploaded the latest versions of my published CP and SL files, I'm just confused as to what's happening. Please if you could, send me your SCORM test file. There has to be something that I'm missing. I'm stepping away from this tonight. Will revisit tomorrow morning. Thanks for all of the help so far.
This discussion is closed. You can start a new discussion or contact Articulate Support.