Enable debugging in LMS

[Bobby Jourdan]

Hi there, I want to enable a debugging window to launch when a course is launched in LMS 365. I go to the scormdriver.js and change the SHOW_DEBUG_ON_LAUNCH=false to SHOW_DEBUG_ON_LAUNCH=true The debugging window launches alright, but it stays blank. Would anyone have an idea if I have to change something more? For Storyline SCORMs, changing the line to SHOW_DEBUG_ON_LAUNCH=true works well. Maybe I am missing a step? Thank you in advance B

This is what I can see in the debugger window when pressing F12.

[papaintegrator]

Hi Bobby,

Did you test this on a local system, you can use WAMP or any other server to test this on local machine?

Also, as the following (below) is defined in scormdriver.js; Do you get "Calling Standard Initialize" messages as given here?

You can also add some counters of your own to verify what is exactly happening and then add additional methods as required:

/best

[Bobby Jourdan]

Hi papaintegrator,

I cannot use WAMP since the environment is restricted but will test that. Sorry for the late replies.

B

[Bobby Jourdan]

Hi there papaintegrator,

I still get a blank screen on the LMS 365. I tried the Storyline file and it works well.

Would you have any ideas please?

Thank you

B

[papaintegrator]

Hi bobby,

I was away from the forums for some time due to a dev sprint. I have some time in my schedule next week .. I will look into it and suggest.

Best,

papaintegrator

[MichaelStephens · Accepted solution]

You need to go into the published file and make a change to to the CPM.js file, which is located in assets/js/. Search for debug and you'll find the line quizReportingData:{lWriteDebugInfo:false. Change "false" to "true", save the file, then try the file again. The debugger should now show you the SCORM debug logs.

[Bobby Jourdan]

works like a charm

thanks a million.

I know a bit about scorm but would like to get deeper.

would you recommend a resource/link where I could get more information about the message I am getting in the debugger

Thanks again Michael

[MichaelStephens]

Are you referring to the error message in the original image you posted?

[Bobby Jourdan]

Actually I meant in general where can I find something that would explain in more details the debugging messages that I see.

I have an idea about SCORM but obviously not enough.

Thanks again

"

35:Thu Mar 21 2019 13:51:01 GMT+0100 (Central European Standard Time) - Call GetValue

36:Thu Mar 21 2019 13:51:01 GMT+0100 (Central European Standard Time) - strResult=unknown

37:Thu Mar 21 2019 13:51:01 GMT+0100 (Central European Standard Time) - intSCORM2004Error=0

38:Thu Mar 21 2019 13:51:01 GMT+0100 (Central European Standard Time) - Returning unknown

39:Thu Mar 21 2019 13:51:01 GMT+0100 (Central European Standard Time) - In SCORM2004_CallGetValue strElement=cmi.completion_status

40:Thu Mar 21 2019 13:51:01 GMT+0100 (Central European Standard Time) - In SCORM2004_GrabAPI

41:Thu Mar 21 2019 13:51:01 GMT+0100 (Central European Standard Time) - Grab API, returning, found API = true

42:Thu Mar 21 2019 13:51:01 GMT+0100 (Central European Standard Time) - Call GetValue

43:Thu Mar 21 2019 13:51:01 GMT+0100 (Central European Standard Time) - strResult=unknown

44:Thu Mar 21 2019 13:51:01 GMT+0100 (Central European Standard Time) - intSCORM2004Error=0

45:Thu Mar 21 2019 13:51:01 GMT+0100 (Central European Standard Time) - Returning unknown

46:Thu Mar 21 2019 13:51:01 GMT+0100 (Central European Standard Time) - strSuccessStatus=unknown

47:Thu Mar 21 2019 13:51:01 GMT+0100 (Central European Standard Time) - strCompletionStatus=unknown

"

[RodWard]

Why not try here:

https://scorm.com/scorm-explained/technical-scorm/scorm-2004-overview-for-developers/

[Bobby Jourdan]

thanks Rod