Importing leap2A file does not respect the locked fields rules
Bug #1747795 reported by
Robert Lyon
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mahara |
Fix Released
|
High
|
Unassigned |
Bug Description
In the institution settings we can lock profile fields, eg firstname, lastname so that a user can't change the values of them.
However, if we upload a Leap2A file with profile details in them that are different to the current ones we can save the new info to our profile - ignoring the 'lock' on the fields
The import should respect the lock
Changed in mahara: | |
status: | New → Confirmed |
Changed in mahara: | |
status: | Confirmed → In Progress |
Changed in mahara: | |
status: | In Progress → Fix Committed |
tags: | added: usermanualupdate |
Changed in mahara: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Patch for "master" branch: https:/ /reviews. mahara. org/8545