-
Bug
-
Resolution: Fixed
-
Blocker
-
2.3.4, 2.3.5, 2.5
-
PostgreSQL
-
MOODLE_23_STABLE, MOODLE_25_STABLE
-
MOODLE_23_STABLE, MOODLE_24_STABLE
-
MDL-38173-master -
Difficult
-
After MDL-37939 was applied, we began seeing corruption of modules moving to other courses. I added a number of comments related to that in the bug, but didn't understand the issue well enough to confirm it was caused by that fix. I have now confirmed that.
When course completion enabled, you get two database updates on mdl_course_modules;
UPDATE mdl_course_modules SET section = $2 WHERE id = $1
parameters: $1 = '519934', $2 = '10931'
UPDATE mdl_course_modules SET section = $2 WHERE id = $1
parameters: $1 = '930004', $2 = '10931'
The first one has the wrong value for id, updating a course_module that is wrong. That id is the instance of the module, not it's course_module.id.
- blocks
-
MDL-37642 condition_info performance warning displayed after creating course.
-
- Closed
-
- caused a regression
-
MDL-38378 DB Upgrade script contains hard coded database prefix.
-
- Closed
-
-
MDL-38386 Change upgrade step for 24 and master for MDL-38173
-
- Closed
-
- has been marked as being related by
-
MDL-38228 Major Performance Problem with "Moving Modules" upgrade step
-
- Closed
-
-
MDL-39109 Modules are not correctly added to sections
-
- Closed
-
- is a regression caused by
-
MDL-37939 Moving modules between sections is not properly working
-
- Closed
-
- will help resolve
-
MDL-38228 Major Performance Problem with "Moving Modules" upgrade step
-
- Closed
-