I have a big problem with SCORM packages not running properly in our Moodle 2.6 platform. They are only loading properly for admin users not students.
I made the SCORM packages using Storyline and up until 2 weeks ago they were working fine. Nothing has changed on the Moodle site, or with the SCORM packages, but now, if a student tries to view the SCORM package, a pop-up window will open and display the header, but no content loads in the middle of the window.
Welcome to the community! Have you tested this through the SCORM Cloud? This is the industry standard for testing content. If it is something on the end of Moodle, I am sure other members will jump in with some assistance.
there is a bug with the Chrome browser that they have fixed in the Chrome development version but not the main stable release that you will have - does this occur in other browsers or just Chrome?
It's happening in all browsers. The SCORM packages were all working totally fine until about a fortnight ago. Now they will only load properly for admin users. The weird thing is that nothing has been changed in the Moodle settings.
I'd try elevating your debugging settings and turn display errors on to see if any further errors are shown when you load the page that was previously blank.
make sure you turn it off again after getting the error messages.
If there are no error messages I'd try switching site themes to see if that makes any difference or using a browser debugging tool to see if any JavaScript errors are being reported.
Thanks Dan. I'm a bit out of my depth to be honest, so this might be a stupid question, but I just want to make sure I'm trying the right thing...
I turned debugging on (as per the moodle guide) but am I right in thinking I wouldn't be able to see any debugging information when I'm logged in with a normal student profile? (which is the only time the SCORMS start behaving oddly). Or am I just looking in the wrong places?
When you turn debugging on and elevate the debugging level it will display for all users unless someone has modified your Moodle config.php file directly and added the parameter "debugusers" which allows you to set the debugging on for certain users but this is unlikely.
If there is no change with debugging elevated to "developer" and display errors "on" but a blank screen still shows then it means it hasn't found any other error information and you should turn it back off. (leaving debugging on when it isn't needed is usually a bad idea)
If you can't diagnose it further yourself you could contact your local Moodle Partner who should be able to provide commercial level support to help you track the problems down.
I can't see any errors unfortunately (even after following your advice, e.g. developer mode etc...), how would I go about locating my local Moodle partner? I could really do with someone who knows what they're doing (as opposed to me) taking a look at the whole Moodle, to be honest...
I work for the Moodle Partner Catalyst IT (links to our different offices on my profile) Flick me a private message if you want more information on the services we provide.
8 Replies
Hello Leah!
Welcome to the community! Have you tested this through the SCORM Cloud? This is the industry standard for testing content. If it is something on the end of Moodle, I am sure other members will jump in with some assistance.
there is a bug with the Chrome browser that they have fixed in the Chrome development version but not the main stable release that you will have - does this occur in other browsers or just Chrome?
It's happening in all browsers. The SCORM packages were all working totally fine until about a fortnight ago. Now they will only load properly for admin users. The weird thing is that nothing has been changed in the Moodle settings.
I'd try elevating your debugging settings and turn display errors on to see if any further errors are shown when you load the page that was previously blank.
https://docs.moodle.org/en/Debugging
make sure you turn it off again after getting the error messages.
If there are no error messages I'd try switching site themes to see if that makes any difference or using a browser debugging tool to see if any JavaScript errors are being reported.
Thanks Dan. I'm a bit out of my depth to be honest, so this might be a stupid question, but I just want to make sure I'm trying the right thing...
I turned debugging on (as per the moodle guide) but am I right in thinking I wouldn't be able to see any debugging information when I'm logged in with a normal student profile? (which is the only time the SCORMS start behaving oddly). Or am I just looking in the wrong places?
When you turn debugging on and elevate the debugging level it will display for all users unless someone has modified your Moodle config.php file directly and added the parameter "debugusers" which allows you to set the debugging on for certain users but this is unlikely.
If there is no change with debugging elevated to "developer" and display errors "on" but a blank screen still shows then it means it hasn't found any other error information and you should turn it back off. (leaving debugging on when it isn't needed is usually a bad idea)
If you can't diagnose it further yourself you could contact your local Moodle Partner who should be able to provide commercial level support to help you track the problems down.
I can't see any errors unfortunately (even after following your advice, e.g. developer mode etc...), how would I go about locating my local Moodle partner? I could really do with someone who knows what they're doing (as opposed to me) taking a look at the whole Moodle, to be honest...
There are a list of the Official Moodle Partners available here: http://moodle.com/partners/
I work for the Moodle Partner Catalyst IT (links to our different offices on my profile) Flick me a private message if you want more information on the services we provide.