|
Signed in as admin - Permissions/define role/add a new role then ticked the box Legacy Role Teacher (editing) - assume from this the new role has all the rights of a legacy teacher. Do I take it I must tick every box a teacher role should have?
Yes you need to tick every box ... this is a documentation problem really ... those legacy capabilities should be moved right down the bottom to a different section.
They're only used by old 3rd party code that was not designed for Moodle 1.7 and doesn't support roles yet. In those cases, Moodle will respond to queries like "get all teachers for this course" by using these legacy capabilities. Notes on legacy capabilities added to http://docs.moodle.org/en/Manage_roles
Also additional notes added to each legacy capability page e.g. http://docs.moodle.org/en/Capabilities/moodle/legacy:editingteacher fixed in cvs 1.8dev and HEAD, now the legacy caps have special menu - you can select only one (selecting several of them would cause problems anyway)
thanks for the report! Could the legacy role type drop-down menu have a help pop-up? Perhaps something like this:
"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." Also, could the legacy role type drop-down menu be put at the bottom of the page below the list of capabilities and just above the "Add new role" and Cancel buttons, as it's not so important? Assuming I understand it correctly... Reopening as legacy role types continue to cause confusion. Please see bug
Unfortunately legacy roles are not unimportant yet - a lot of code depends on them
The help popup is a good idea, going to add it closing, please use MDL-9013 to propose improvements
thanks everybody for ideas and participation, I agree we should make roles much easier to use Closing, please see MDL-9013. Thanks again Petr
 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Bug
Closed
Minor
Move legacy capabilities down the bottom of the list in a new section to help avoid confusion
 |
|
AFAIK there is no duplication mechanism in 1.7, only in 1.8.