[Mahara-contributors] [Bug 605750] Re: SSO and non-locked fields doesn't go well together
** Changed in: mahara Milestone: None => 1.3.0 ** Changed in: mahara Status: New => Triaged ** Changed in: mahara Importance: Undecided => Medium -- 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. ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 605750] Re: SSO and non-locked fields doesn't go well together
"If I disallow the synchronization of data while setting up Mahoodle, SSO does not work. " That sounds like a different bug! ** Changed in: mahara Assignee: (unassigned) => Richard Mansfield (richard-mansfield) -- 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. ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 605750] Re: SSO and non-locked fields doesn't go well together
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. ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 605750] Re: SSO and non-locked fields doesn't go well together
** Changed in: mahara Status: Triaged => Fix Committed -- 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: Fix Committed 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. ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 605750] Re: SSO and non-locked fields doesn't go well together
If it is not possible to lock the fields due to more complex scenarios, then I like your idea of another check on the profile. -- 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: Fix Committed 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. ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 605750] Re: SSO and non-locked fields doesn't go well together
** Changed in: mahara Status: Fix Committed => Fix Released -- 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: Fix Released 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. ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
