Skip to main content
L
LeadJedi
Participating Frequently
June 9, 2020
Question

Tweaking Exported HTML5/SWF Publish to route to HTML5 Only

  • June 9, 2020
  • 1 reply
  • 1144 views

Greetings all, thanks in advance for any help / insight on this. 

 

The Scenario: 

We have 200+ published Captivate 9 tutorials that were all published as BOTH HTML5 / SWF in AICC format. I'm not sure how relevant AICC vs SCORM is on this, but our LMS requires AICC. 

 

When we launch the course through our LMS (Oracle's Taleo) it launches the swf file consistently.

 

The Goal:

We WANT to be able to tweak the already exported files so that they route directly to the HTML5 version of the files published in the same directory WITHOUT having to re-export all of these 200+ individual courses. 

 

I'm familair with HTML and some basic javascript but when I try to follow what's going on with these files from the index.html file I get lost. 

 

Thoughts? Suggestions? I've included a screen shot of the output files from one of our projects. 

 

This topic has been closed for replies.

1 reply

RodWard
Community Expert
RodWardCommunity Expert
Community Expert
June 10, 2020

Just wondering if you have heard that Flash/SWF is officially dead as of the end of 2020?  You should be ditching all of the SWF versions of your courses and just publishing ONLY to HTML5. 

 

Regarding your current question: With Captivate's dual output publishing option, the multiscreen.html file is the one that decides where to redirect the user, based on whether or not they are using a mobile device.  Unfortunately this 'sniffer' script will send everyone NOT on a mobile device to the SWF version of the content.  If you wanted to avoid republishing and just modify one of the files so that everyone gets the HTML5 content then that's the file I would suggest you look at.  Somewhere inside all of that code you will find these lines:

As you can see, my CPTX project was called Test_Dual and that's why the .htm file has that name.  If you look for this code where it uses the name of your project in the multiscreen file then you should just be able to change the code at this spot to point to the index.html file instead so that regardless of whether the user is on a mobile or non-mobile (i.e. desktop or laptop) then everyone gets the HTML5 output.

 

Give that a try.

L
LeadJediAuthor
Participating Frequently
June 10, 2020

Rod, Thank you so much for your response!

 

The answer your'e presenting was the solution I initially found. Sadly, it doens't quite apply to us. Our output files DO NOT contain a multiscreen.html file. If you look at the attached image in my post above you'll see that file is not present there, nor in any of the sub folders.

 

I BELIEVE this may be because we are forced to publish in AICC format. That's not something we can change at the moment so we have to stick with that.

 

You hit the nail on the head though as far as solutions. How do we find where the AICC equivelent of that is happening?

 

Incidently, We're no longer publishing SWF formats as a matter of practice for that very reasy. These training courses were published over the last five or six years. They knew the writing was on the wall, which is why they were dual publishing and not worrying about it. The assumption was always that they could tweak the files to point to the HTML5 content.... hence... here we are 🙂  

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices