Skip to main content
C
Customer Perceptions
Participating Frequently
July 10, 2019
Question

Resume Failing in Modules Published with CP 11.5

  • July 10, 2019
  • 2 replies
  • 657 views

Any modules I publish since upgrading from CP 11.0 to CP 11.5 fail to resume.

I get a JavaScript error "b is undefined" in the function getCustomSlideItemList in CPXHRLoader.js.

We are using a custom LMS with xAPI. Modules published in previous versions of CP (including 11.0) work fine.

Does anyone know what's going on? Did something change in 11.5 in how the JS output works with xAPI?

Any help appreciated.

This topic has been closed for replies.

2 replies

Lilybiri
Lilybiri
Legend
July 11, 2019

Did you try to test on SCORM Cloud as well? Just to fcheck if this indeed due to Captivate, or the cause has to be found in the LMS which could have had updates.

Does it happen with all browsers?

    C
    Customer PerceptionsAuthor
    Participating Frequently
    July 12, 2019

    Thanks for the reply, I tested on SCORM Cloud and in other browsers and the issue persists. I also made a tiny test module and it wasn't happening with that until I added a random quiz question and now I can reproduce it. I did some JS debugging and found it seems that the JS tries to build an array of slide items for the content slides from their 'si' attribute but it goes too far and tries to do this for the first random question slide as well and the si attribute is undefined and that leads to the error. I will contact Adobe thanks for the help.

    D
    davidc74154763
    Participant
    July 18, 2019

    Have you had any luck getting this issue resolved? I'm running into a similar issue with Captivate 11.5

    Re-launching any of my published SCORM packages from the LMS results in a hanging loading screen. I can't even test whether or not the bookmarking works because the course never loads after the first attempt. Here's what I got out of the console:

      Paul Wilson CTDP
      Community Expert
      Paul Wilson CTDPCommunity Expert
      Community Expert
      July 11, 2019

      I would submit this as a bug using Adobe's form. Click on your profile icon and selet Submit bugs/Feature request. I sent in a bug earlier this week and I already have a patch to fix it. They take these sorts of things very seriously. The user forum is not likely going to have  a fix for this. At least not right away.

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