Recently I found out that SCORM has some problems considering groupings: if a SCORM activity is attached to specific grouping, the user with capability to view all groups doesn't have access to reports at all, if he/she is not actually in the grouping. This would force teachers, for example, to add themself to all needed groups, which is not very convenient.
Also, there's a block of code in report.php (line ~128) and a function scorm_get_count_users in locallib.php (line ~1124) with SQL expressions considering groupings. Actually, if a SCORM activity is attached to grouping, this SQL checks if the users it's selecting are inside that grouping too. But there can not be users outside that grouping in this activity because it's unaccessible by them, right? So this SQL looks redundant, or am I mistaking?
- will be (partly) resolved by
MDL-21555 Scorm report improvement