1.2 is now pretty much only for security fixes, so I wouldn't worry about that one.
In terms of 1.3, I'm not sure how important this is. I mean it's bad that we get duplicate emails but it has always been the case (i.e. not a regression) and while it's easy to do when you know how to do it, it's not so easy to do by mistake. And I would tend to be conservative in changing the registration code on the stable branch because it could introduce bugs that could be worse. What do you think? -- You received this bug notification because you are a member of Mahara Contributors, which is subscribed to Mahara. https://bugs.launchpad.net/bugs/692614 Title: Registration email can be sent out more than once within the initial 24 hour period Status in Mahara ePortfolio: Fix Committed Bug description: A user can register, and be sent emails, multiple times with the same details prior to completing the registration process from the link sent. There are multiple records in usr_registration with only the sequential id differing. Perhaps we need to check for a unique email in here and offer some notification to the user that the email has already been used? However, there is also the issue that if this initial email wasn't received it might not be easy for the user to wait 24 hours until it clears from the database to try again, or to get hold of a sysadmin to delete the record manually so they can do so without hassle so there might be extra requirements around this or this might be the reason it currently allows for multiple records. _______________________________________________ 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
