-
New Feature
-
Resolution: Fixed
-
Critical
-
3.1, 3.6
-
MOODLE_31_STABLE, MOODLE_36_STABLE
-
MOODLE_36_STABLE
-
MDL-53566-master -
As discussed at the 2015 Australian Moot, a feature was discussed whereby it is possible to 'freeze' or 'lock' a context and all content in that context.
The implementation proposed at the moot was to:
- add a new field to the context table to indicate that a context is frozen;
- when that context, or any parent context, is frozen the has_capability() function will return false for all write capabilities
A new capability is introduced to control locking of a context, and a further capability to control unlocking of the context. The person who locks a context may not be the same one able to unlock it.
The capability required to unlock the context must be a 'read' context to ensure that it is not denied by the capability itself.
- caused a regression
-
MDL-63984 Followups for Context Freezing
- Open
-
MOBILE-2788 Handle context freeze in the Mobile app
- Closed
- has a non-specific relationship to
-
MDL-79924 Context freezing should allow backup and importing from courses
- Open
-
MDL-43426 Locking Course on Completion (make read-only archive)
- Closed
-
MDL-51301 Creation of new "read-only" capability/permission to build "read-only" roles
- Closed
- has a QA test
-
MDLQA-12871 An administrator can freeze categories, courses, activities and their content
- Passed
- has been marked as being related by
-
MDL-64336 When an assignment is frozen students cannot see their submission
- Closed
-
MDLQA-12872 CLONE - An administrator can freeze categories, courses, activities and their content
- Passed
- is duplicated by
-
MDL-62639 Allow a course or activity to be put into a read-only mode
- Closed