← Back to team overview

mahara-contributors team mailing list archive

[Bug 1747795] [NEW] Importing leap2A file does not respect the locked fields rules

 

Public bug reported:

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

** Affects: mahara
     Importance: High
         Status: New

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1747795

Title:
  Importing  leap2A file does not respect the locked fields rules

Status in Mahara:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1747795/+subscriptions


Follow ups