Moving it to course_backend keeping generic
methods and attributes in backend class.
AMOS BEGIN
MOV [size_0,tool_generator],[coursesize_0,tool_generator]
MOV [size_1,tool_generator],[coursesize_1,tool_generator]
MOV [size_2,tool_generator],[coursesize_2,tool_generator]
MOV [size_3,tool_generator],[coursesize_3,tool_generator]
MOV [size_4,tool_generator],[coursesize_4,tool_generator]
MOV [size_5,tool_generator],[coursesize_5,tool_generator]
AMOS END
Function add_mod_to_section() has very confusing arguments when object looks like record from
table course_modules but field ->section refers to relative section number (course_sections.section).
In table course_modules the field section refers to course_sections.id.
Also add_mod_to_section() does not update table course_modules and does not call rebuild_course_cache()
which developer can forget to do afterwards.
- Added function course_add_cm_to_section()
- In the core code add_mod_to_section() is replaced with course_add_cm_to_section()
- Function add_mod_to_section() is deprecated