mahara-contributors team mailing list archive

[Richard Mansfield <605750@xxxxxxxxxxxxxxxxxx>]

I don't think we can set the fields to locked at the institution level,
because unfortunately you can have some users in one institution who
come from moodle, and others who don't, or users from two different
moodles in the same institution, and some of these users may need to be
able to edit their data.

So I think we should just add another check in the profile area to see
if the user comes from a moodle that synchronises, and if they do,
disable the appropriate profile fields (but leave them unlocked in the
institution page in the admin area).

-- 
SSO and non-locked fields doesn't go well together
https://bugs.launchpad.net/bugs/605750
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.

Status in Mahara ePortfolio: Triaged

Bug description:
When Mahoodle is in existence, students cannot change their name and introduction. It would be good to disallow editing of the name fields (or any other field that is managed) by default so that they are not tempted to edit it anyway and then run into problems or wonder why the new info is changed back to the old one.

There is the possibility to lock fields and disallow editing. However, per default, a Mahoodle allows editing, but it always overwrites the data with the data it imports from Moodle the next time students log in. A number of users have complained about that (e.g. on Twitter) because they didn't know that Moodle's info would be inserted again as the fields in Mahara were editable. 

I had this issue also on the 1.3 master.dev that I installed on my computer. If I disallow the synchronization of data while setting up Mahoodle, SSO does not work. Therefore, I think it would be good to disallow editing of the managed fields all together for Mahoodle institutions.