Hia, I noticed that the word "Contents" was always showing at the bottom of all my nodes which had a SCORM field, even when there was no SCO uploaded.
I "fixed" this by moving line 354 in player.php to within the if-statement below (see attached screenshot). However, I haven't really found out when this line *should* be printed so it might be the wrong approach...(?)
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | cckcontents2.png | 388.86 KB | vegardjo |
| #2 | cck_scormcontents.png | 433.79 KB | vegardjo |
| scorm-contents.jpg | 61.38 KB | vegardjo |
Comments
Comment #1
pgerling commentedi cannot reproduce this issue - the word "contents" never appears for me (even with a clean drupal installation)
Comment #2
vegardjo commentedHm, you don't? I just updated to the latest beta, and the bug is back, you can see it live here: http://www.helsekompetanse.no/mangfold/736 (I just picked a page, but you will see it in all pages there, and none of them has any SCORM content attached. But they are all book pages, and that content type has the CCK Scorm field set up.
See also screenshot in case I fix this again on the live site before you get a chance to see it..
Here are lines 356-7 in player.php where it is set:
Comment #3
vegardjo commentedI tried on a fresh install too, and couldn't reproduce it initially, but when I added my book page to a menu (primary links in this case) the bug is back, along with this warning:
warning: mysql_num_rows(): supplied argument is not a valid MySQL result resource in /Applications/MAMP/htdocs/clean/sites/all/modules/cck_scorm/player.php on line 362.See screenshot.
Comment #4
pgerling commentedNow that's strange. I still cannot reproduce your issue, but since I can clearly see it on your website and screenshots - and because I have no idea why "Contents" should appear there anyways - I excluded line 357 from player.php. You can find this fix in the new beta9. Thanks a lot for your help! :o)
Comment #5
vegardjo commentedThanks - I have updated to beta9 and "Contents" no longer shows :)
..however the php warning is still there
Comment #6
pgerling commentedWe could not reproduce this bug in beta10