Details
-
Type:
Sub-task
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.0
-
Fix Version/s: 2.0
-
Component/s: Roles / Access
-
Labels:None
-
Affected Branches:MOODLE_20_STABLE
-
Fixed Branches:MOODLE_20_STABLE
Description
1/ UI forbids one role to have more legacy types at the same time - unfortunately this is not enforced at db level.
2/ We still use legacy caps a lot - the main reason is unsolevd enrolment problems in 1.7-1.9
New course participation concept (aka enrolments) should finally solve all problems here and let us get rid of old legacy caps and move this role type info into role table itself.
It might be the right time to stop using work legacy because it is confusing for many ppl,
long time ago David Mudrak proposed word "archetype" and used it in Czech localisation - seems more appropriate to me 
+1 for this, and choice of word archetype.