Details
-
Type:
Task
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.8
-
Fix Version/s: 2.0
-
Component/s: Roles / Access
-
Labels:None
-
Affected Branches:MOODLE_18_STABLE
-
Fixed Branches:MOODLE_20_STABLE
Description
Legacy roles were originally created to help with transition to new roles system, but unfortunately the transition is not over yet and sometimes the legacy caps are used for something else than intended.
Legacy roles are needed for:
1/ old modules and plugins
2/ not fully converted code in core - guest access, primary admin, creators in ldap sync, restore, etc.
3/ upgrades of existing caps
4/ reseting of existing caps
In general it should be recommended to set legacy type for roles that are similar to old student/teacher/admin/creator and not set for roles that are assigned to add extra capabilities to users that already have student/teacher-like role
Possible solutions:
1/ remove use of all legacy caps from code - the worst problems is legacy:guest; creators are being worked on; it needs extra settings and configuration options which are going to add some more headaches 
2/ improve/redesign reset permissions to defaults
3/ add help icon to role definition
4/ improve docs
5/ implement role templates instead of legacy types - or if the legacy types are not used in code, we could just rename the legacy to template.
I am afraid we can not do this properly before the 1.8 release
Any ideas?
Issue Links
Activity
- All
- Comments
- History
- Activity
- Source
- Test Sessions
Unfortunately it is still required to set legacy roles in some cases - the most abused one is legacy:guest and teacher
Suggestion for legacy role drop-down menu help pop-up (copied from
MDL-7633):"Legacy role types provide backward compatibility. A legacy role type may be set if your site uses old 3rd party code that was not designed for Moodle 1.7 and doesn't yet support roles. Otherwise, it's not necessary to set a legacy role type.
Setting a legacy role type does NOT provide a new role with all capabilities of a pre-Moodle 1.7 role."
MDL-7633): "Legacy role types provide backward compatibility. A legacy role type may be set if your site uses old 3rd party code that was not designed for Moodle 1.7 and doesn't yet support roles. Otherwise, it's not necessary to set a legacy role type. Setting a legacy role type does NOT provide a new role with all capabilities of a pre-Moodle 1.7 role."