Skip to main content
matt_creating
matt_creating
Known Participant
August 15, 2017
Question

Cap9 Standard Project to Responsive

  • August 15, 2017
  • 1 reply
  • 119 views

Hello Team,

I'm updating some courses for a client and they want to change their standard captivate courses to responsive courses.  I started the conversion, all manual work, and published to do a test run on their database LMS (designed by the previous ID who built their original courses).  These courses have a lot of advanced actions and use js to effect bookmarking.  The original courses are published as a swf but with responsive courses you only get the option to publish as html.  So when I publish the responsive course and upload to their LMS, after choosing the option to either start from the beginning or go to the bookmark (either option) the course scrolls through every slide as if it's searching for the bookmark and goes to the completion slide.  So essentially they complete the course and get credit for it without reviewing the info.

So how do I get my advanced actions and js to behave in an html file the same way they do in a swf?

I'm sure you need more info so please let me know what needs to be clarified.

Thanks for any assistance

    This topic has been closed for replies.

    1 reply

    Lilybiri
    Lilybiri
    Legend
    August 15, 2017

    You don't specify which version was used for those 'old' courses: which version of 9? That is very important. I suspect you are now using 2017 for the conversion?

    HTML5 output can behave totally different from SWF output, especially when using advanced actions. JS should just work much better with the HTML5 output than with SWF output. I wonder if this could be solved by posting questions in a forum but you can try.

    Did you try first to publish the normal (nor responsive) course to HTML5 to check the output? Personally I would start by not combining all the problems at once. You have to find out which scripts are causing problems (both advanced/shared actions and JS). Later on you can try to convert to responsive, which is not as easy (even with fluid boxes) as is often told.

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