-
Bug
-
Resolution: Fixed
-
Minor
-
2.0, 2.2
-
MOODLE_20_STABLE, MOODLE_22_STABLE
-
MOODLE_23_STABLE
-
MDL-19125_module_security -
Currently the way this works is:
- Enforce settings (as defaults) for newly created courses.
- Per course, use a whitelist to determine which modules can be added.
This is kind of useless, as an empty whitelist is ambiguous. It could either mean "use the site default", or it could mean "i don't want to allow anything at all".
One way to get around this is a new setting (maybe course.restrictedmodules) which indicates that the course has overridden the site default.
Another way is to add a capability to each module 'canaddtocourse' or similar, and override it for a role at a course context. I think the latter is probably more correct in a 'moodle sense' but has the following drawbacks:
1. Third party module authors must implement this capability, for their module to implement this setting (stupid)
2. Eh, roles are complicated enough as it is, and Howard will kill me if we must override things further.
The former is probably simpler (and easier to implement) but means adding yet another field to course. Do courses have extra settings? Maybe we could have a course_preferences table or something.
- caused a regression
-
MDL-34082 Moodle 2.2 upgrade to 2.3 error: Unknown column 'retrictmodules' in 'where clause'
-
- Closed
-
- Discovered while testing
-
MDL-32158 Fix course restricted module restore from 1.9 to 2.x
-
- Closed
-
- has a non-specific relationship to
-
MDL-19110 If modules are restricted, courses created by a user with 'course creator' role don't contain any modules
-
- Closed
-
-
MDL-39274 Update Moodle 1.9 to 2.2 and finally to 2.4
-
- Closed
-
- is duplicated by
-
MDL-11894 Restricting activity module to course/category of courses
-
- Closed
-