Development:New enrolments in 2.0: Difference between revisions
From MoodleDocs
No edit summary |
No edit summary |
||
| Line 8: | Line 8: | ||
}} | }} | ||
{{Moodle 2.0}} | {{Moodle 2.0}} | ||
=Overview= | |||
The major difference from 1.6-1.9 enrolments is that the course enrolment information is stored again in a separate database table ''course_participants'. The enrolment related information was move from ''course'' table to new ''enrol'' table which holds plugin instances. The old enrolment plugins need to be completely rewritten. Course category enrolments via role assignments is not possible any more, existing category enrolments are migrated to new cohorts and cohort enrolment plugin. | |||
The benefits are: | |||
* we can use SQL to find enrolled users in any course extremely quickly (much better performance) | |||
* multiple enrolment plugins per course are full supported (includes more instances of the same type) | |||
* new enrolment overview interface | |||
* user enrolments may be suspended and reactivated | |||
* plugin may prevent users to change/break enrolment synchronised with external systems | |||
* finer access control, more flexible/configurable course settings UI | |||
* no hardcoded enrolment behaviour - it is possible to completely replace guest access, self enrolments, etc. with custom plugins | |||
Revision as of 21:46, 13 June 2010
Note: This page is a work-in-progress. Feedback and suggested improvements are welcome. Please join the discussion on moodle.org or use the page comments.
Template:Infobox Project Template:Moodle 2.0
Overview
The major difference from 1.6-1.9 enrolments is that the course enrolment information is stored again in a separate database table course_participants'. The enrolment related information was move from course table to new enrol table which holds plugin instances. The old enrolment plugins need to be completely rewritten. Course category enrolments via role assignments is not possible any more, existing category enrolments are migrated to new cohorts and cohort enrolment plugin.
The benefits are:
- we can use SQL to find enrolled users in any course extremely quickly (much better performance)
- multiple enrolment plugins per course are full supported (includes more instances of the same type)
- new enrolment overview interface
- user enrolments may be suspended and reactivated
- plugin may prevent users to change/break enrolment synchronised with external systems
- finer access control, more flexible/configurable course settings UI
- no hardcoded enrolment behaviour - it is possible to completely replace guest access, self enrolments, etc. with custom plugins
