Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cmi.interaction tracking broken in MCQ v2.2.0 & 2.2.1 when used with 'legacy' branch #2204

Open
moloko opened this Issue Aug 2, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@moloko
Copy link
Member

moloko commented Aug 2, 2018

Subject of the issue/enhancement/features

As per this forum thread, 'interaction tracking' is not working for anyone using the two most recent versions of MCQ together with the 'legacy' branch of the framework - so this will affect most authoring tool users.

I haven't tested this specifically but it may also affect GMCQ since that has a dependency on MCQ.

Your environment

  • Framework v2.2.x, adapt-contrib-mcq v2.2.0/2.2.1, adapt-contrib-spoor v2.1.x
  • any browser, device

Steps to reproduce

Get the latest 'legacy' version of Adapt using adapt create course my-adapt-course legacy. build and run the course with the SCORM debugger open, answer any MCQ.

Expected behaviour

You should see calls to write to cmi.interactions in the SCORM debugger

Actual behaviour

No calls to cmi.interactions take place. If you debug the function onQuestionRecordInteraction in adapt-stateful-session.js, you can see that the calls to questionView.getResponseType(), questionView.getResponse() etc. all return undefined since mcqView.js no longer contains these functions - they have been moved to mcqModel.js and, since there is no 'redirect' code is in place like there is in Adapt v3 it falls back to calling the 'abstract' implementations of these functions in questionView.js

Need to make sure any fix doesn't break interaction tracking for those question components that have not yet been split into model/view.

Screenshots (if you can)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.