Skip to main content
chriss47131829
chriss47131829
Participant
January 8, 2016
Question

Captivate 9 project play issues with IE9 - HTML5 only

  • January 8, 2016
  • 3 replies
  • 407 views

I am attempting to transition my consulting company's training component to Captivate.  However, we have run into some apparently new issues with projects playing in IE9 or IE compatibility mode. We are trying to move away from Flash entirely so only publishing as HTML5. Previous tests worked fine in IE9, but most recent test does not seem to auto-play in 9, although works perfectly fine in 10, 11, and Edge.

My situation is somewhat unique as we do not provide training through a standard LMS, but rather on a proprietary cloud-based system that also includes, content management, workflow management, and related tracking and reporting tools. Because our training content has to be hosted and tracked through this system, we have had problems troubleshooting certain captivate issues . Not sure if this new IE9 issue is something we did internally with code when placing on our system or if it is potentially related to a known compatibility issue and/or project settings.

I understand this is a unique situation, but  providing some info below in the hope that someone could point me in the right direction.

  • When using captivate to create course in our system, we break a larger course project up into smaller lessons and upload each of these smaller published projects to separate book pages on our system.
  • Progress tracking and reporting is something that is done on the system side and scored/tracked assessments are handled as separate component. As such, we do have not published with reporting in Scorm format turned on.
  • During original testing late last year, we had no issues with IE9 and seemed to run as well as IE11 and Chrome.
  • However, we tested again this month apparently using the same process to get files on our system and IE9 is no longer working with 10+, Edge, Chrome having no problems.
  • For all other browser, when users navigate to a book page on our system, the respective project will play with no functionality or display issues.
  • However, when a page is accessed in IE9, the project apparently does not play and user only sees a blank screen (including no default play button)
  • For the reasons stated above we are not publishing with reporting turned on or publish Scorm-compatible. Based on my limited tech expertise and fact that IE9 is only issue don't think Scorm is the issue, but did want to make clear.

Rather than making this any longer will leave at that for now, but can provide anymore relevant info in response. If some kind soul can help me crawl my way out of the development hole I have been stuck in, it would be very much appreciated

    This topic has been closed for replies.

    3 replies

    TLCMediaDesign
    TLCMediaDesign
    Inspiring
    January 9, 2016

    Press F12 when you launch the course in IE, press F5 to refresh and check the errors that are thrown in the console. It sounds like "cp is undefined".

    If your page is running inside of a parent frame compatibility will generally have no effect, nor the doc mode. It defaults to the parent window.

    jsvfoto9485530
    jsvfoto9485530
    Inspiring
    January 8, 2016

    I hate those development holes--sometimes it can take a while to get out of them. Have you tried this suggestion?

    BDuckWorks
    BDuckWorks
    Inspiring
    January 8, 2016

    You mention that you tested a while ago, and you are testing again, have you considered changes that may have occured on the desktop environment, or the cloud based management environment?

    Was it recent enough ago that both tests were with Cp 9 output, or was the earlier test Cp8?

    chriss47131829
    chriss47131829Author
    Participant
    January 8, 2016

    Thanks for the response. I don't think desktop environment is a factor and no real relevant differences. C9 came out out just after our initial purchase and we updated to 9 before we published anything for testing on system. However, it is possible that the test course was originally developed in 8 and then published in 9, but hadn't considered that as a potential issue.

    You are definitely on-point regarding possibility of it being related to changes on the management system side as new functionality and features are pushed up every few months often with unexpected consequences and we will need to investigate that further if other troubleshooting provides no results.

    It could also very well be the code used to call projects on the page and/or the places/paths in which certain project assets are placed on the system (paths in default output code is currently modified to point to system paths). I know enough code to evaluate differences and am working to investigate that, but having trouble understanding how these specific issues would result in issue for IE9 only.

    All that being said, I am a development guy rather than tech with tech primarily, if not exclusively, focused on other functionality and responsive mostly to company management priorities in other areas. Unfortunately, I am in a bit of a training ghetto here and is difficult to get anyone to understand importance of leveraging development and design to usability and efficiency and enlisting focused attention from tech is often a struggle. As such, I am trying to do initial troubleshooting and narrowing down of issues so I can get over the inevitable "not our problem" hurdle from the tech black box. I have been struggling to get buy in on development tools for quite awhile now and just getting requisite help to get test courses up and create self-reliant procedures for programming in place has been a delay-filled nightmare. At this point, if I can't get this or some other authoring tool implemented for development, I probably need to move on.

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