Emergency help needed with dreaded "unable to acquire LMS API" error!

Re: Emergency help needed with dreaded "unable to acquire LMS API" error!

by Matteo Scaramuccia -
Number of replies: 0
Picture of Core developers Picture of Peer reviewers Picture of Plugin developers

Hi Rick,
just look at the display settings in the SCORM activity, https://docs.moodle.org/22/en/SCORM_settings#Display_settings, Display package - in current or new window.

I've read about the popup setting straight from the logs inside the document you've attached in the post above:

34:Sat Mar 7 00:18:17 EST 2015 - In SCORM_ScanParentsForApi, win=https://lms.preparis.com/mod/scorm/player.php?scoid=114&cm=93&;display=popup

The strange thing is that you've several "errors" which cannot be related with a small change in the php.ini file like upload file size and even they started together even if not related...

SCORM is affected by the so called Cross-Domain Issue which is due to the actual nature of the SCORM API being based on JavaScript: you can't host your content out of the domain hosting the SCORM API i.e. you need to host the files inside the LMS from which you access the content.
That being said, again it is strange that you've falled into the cross-domain issue after changing the upload file size: what do you mean when you say that the Content is launched from domain A while the LMS is hosted in domain B?

  • Do you mean that in your domain A you've links to the SCORM activities hosted in your domain B? That is legal and it should work: users will click on links pointing to domain B, another site.
  • Do you mean that the raw files are hosted in domain A and you've published a skinny SCORM package in domain B using absolute URLs in the imsmanifest.xml file? In this case you'll fall in the Cross-Domain Issue and that is true regardless the upload size set in the php.ini file.

I'm running out of ideas.

HTH,
Matteo