| Table of Contents |
|---|
Troubleshooting Steps
This is the common recommended order to troubleshoot broken Scorm courses:
...
As of version 4.0.x a new manifest mapping has been created and is used on ImportScormany importScorm commands after 4.0. This is to prevent manual mapping of the multiple entry points (e.g. index_lms_html5.html) in the SCOManifest.js after import. The new SCOManifest.js should still have a value mapped after import (lines 6 and 7):
...
Course Is Not Viewable By Students
There is currently an issue on 4.2.x with the importScorm command, caused by
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
- After running importScorm, navigate to the course itself (final link).
- Before changing the template to the SCORM course template as you normally do, you need to Edit > Links > Publish the link.
- Then you can change the template to the proper SCORM template. (Edit > Page > Change Template)
Currently the SCORM templates (at least SCORM.Course.Simple.cshtml) don't seem to be aware of this and so no error is shown anywhere in the console or network trace.
Debug the Scorm Extraction (ImportScorm command)
When debugging the ImportScorm command the first break point should be set in CoreClient.Scorm.cs on line 183 (CreateManifestJSFile()). If the sco_resources count is 0, the course either has multiple child activities (which isn't supported until 4.2.x
), or the manifest is incorrectly made/formatted. If this method is unable to find any sco resources, the package is improperly made, and must be checked on Scorm Cloud (see next section) and/or bounced back to the client/vendor.Jira Legacy server System JIRA serverId 23f523ea-1678-3ca2-a1e8-2de53fd3b74a key COREDEV-4876
Testing the Package Externally
...