http://moodle.org/mod/data/view.php?rid=1005&page=16

Do we want (1) a tool for debugging actual roles-related problems or (2) a tool allowing administrators to run academic what-if scenarios? Both are valid use cases, but for me (1) is far more important.

Tim and I discussed this in: http://moodle.org/mod/forum/discuss.php?d=91993

If we want a tool for (2), we should consider incorporating the functionality of the Role debugger into core.

http://moodle.org/mod/data/view.php?d=13&rid=1204

The Role Debugger can be used by any user, not just the administrator, and it gives the user a complete analysis of his own permissions, not just his role assignments. I gave an extended use case for it in MDL-13228 ("Improve the transparency of Roles...").

Please do not misunderstand me: I have been using the User's roles report since March, and I find it very handy for getting a quick snapshot of a user's global role assignments.

I have helped dozens of users debug complex roles-related problems using the Roles debugger (see the use case "A roles expert helping a roles novice debug a roles-related problem"), usually in a single iteration. These were problems of the most difficult kind – self inflicted problems created by administrators who had fiddled with roles without understanding what they were doing. In some cases the administrators could not access the site administration block.

Anyway, this issue should be linked to MDL-13228.

I like Tim's report, because it hit the nail on the head for functionality that I have been missing. If I am sorting out a roles problem, the number one problem is that there is, by default, no way at all to tell what roles a user has throughout the site. Of course, this is 99% the root of roles problems - you didn't know about a role assigned somewhere else. In a complex Moodle site, even if you do know about the assignment, it can be very hard to find. I always considered this a surprising omission.

Tim's addon is very simple and, I suspect, solves a huge percentage of roles problems. However, I'm not partisan about it - but, we need to get something in to handle this function.

On a site note.... the ajax name lookup is inspired! I find myself wishing things like the roles assign screen did something similar.

We may need to think a bit harder about exactly who should be seeing this information. At the moment, it is shown to anyone who can see the roles tab (the rules for that have not changed).

Note that the part about bulk removing role assignments has gone. That may come back, but only if I have time to work on MDL-10002.

Unknown column 'ra.active' in 'where clause'

SELECT ra.id, ra.userid, ra.contextid, ra.roleid, ra.enrol, c.path, r.name AS rolename, COALESCE(rn.name, r.name) AS localname FROM mdl_role_assignments ra JOIN mdl_context c ON ra.contextid = c.id JOIN mdl_role r ON ra.roleid = r.id LEFT JOIN mdl_role_names rn ON rn.roleid = ra.roleid AND rn.contextid = ra.contextid WHERE ra.userid = ? AND ra.active = 1 ORDER BY contextlevel DESC, contextid ASC, r.sortorder ASC
[array ( 0 => '2', )]

• line 292 of lib/dml/moodle_database.php: dml_read_exception thrown
• line 501 of lib/dml/mysqli_native_moodle_database.php: call to moodle_database->query_end()
• line 78 of admin/roles/usersroles.php: call to mysqli_native_moodle_database->get_records_sql()