The only reason why two users would have the same email address is when a Leap2A import is made or if the same user is added a second time through an external authentication method. In both cases it would be better I think if the system alerted the admin to the fact so that a duplicate account could be avoided. With the interactive import of a Leap2A file, a user doesn't have to create a new account anymore to get their content into Mahara, but content can be imported directly into an existing portfolio. And when a user tries to set up a new account with the same email through an external auth method, it would be good to alert as well because then rather than having two accounts (or more) and getting confused which one to use, the admin would be able to set up the proper auth method for the one account the user should be having.
Since a user can discern which content to make available to whom, two accounts or more shouldn't be necessary. -- 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/903494 Title: Uniqueness of email addresses not enforced in artefact_internal_profile_email Status in Mahara ePortfolio: Triaged Bug description: The uniqueness of email addresses is not enforced by the database in the artefact_internal_profile_email table. We should consider adding a unique constraint on that column because elsewhere we prevent users from adding an email address already claimed by another user. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/903494/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~mahara-contributors Post to : [email protected] Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
