Conversation
|
Username is supposed to be protected as private data in normal circumstances. Can we please make sure this respects the protectusernames setting at the bare minimum? |
|
But.. this should also really be a setting, not all sites will want to display username in this report. |
|
Thankyou for the feedback @danmarsden . I'll add a new setting for this feature and make sure it respects |
|
That would only be a bare minimum - probably also worth looking at how the 'show user identity' setting works in user policies settings and if it would be more appropriate for this report to respect those settings. Personally I think it's better to allow an admin to opt in adding this field to the report. |
|
Hi @danmarsden , could I please get your feedback for the latest changes to this one? |
|
sorry - unlikely I'll get to this quick - as long as username is not exposed under normal circumstances you should be able find someone in the AU team to do a review. |
Peterburnett
left a comment
There was a problem hiding this comment.
Approved, I've just asked Owen to squash it down a bit, then I'll merge
e2b98b6 to
1a7640b
Compare
This merge requests introduces a new
usernamecolumn for the attendees table. This new column can be toggled on/off with a new configuration setting. This column will also abide by the Moodleprotectusernameanduserpoliciesconfiguration. The attendees download file will include the new field when enabled.What's been done?
usernamecolumn to page and download file.attendeesshowusernamesconfig setting.Testing instructions:
true.true({domain}/admin/search.php?query=protectusername).{domain}/admin/settings.php?section=userpolicies)true({domain}/admin/search.php?query=protectusername).vendor/bin/phpunit --testsuite mod_facetoface_testsuite.Unit testing: