search

google-code-export / flies

Automatically exported from code.google.com/p/flies
GNU Lesser General Public License v2.1
2 stars 0 forks source link

[Register] "Transaction failed, Unexpected error" when registering a new user with an existing email. #248

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Register "tester1" with email "tester@example.com"
2. Register "tester2" with email "tester@example.com", which already used by 
"tester1"

What is the expected output?
Either allow the tester2 to register, 
or showing error message like
"This email has been used by other user!'
when registering the tester2.

What do you see instead?
Error message:

Transaction failed
Unexpected error

after "tester2" clicks the Register.

What version of the product are you using (displayed at the bottom of the
login page)?
Both 1.3-SNAPSHOT (20110222-0102) and 1.2-SNAPSHOT (20110216-1737)

Please use labels and text to provide additional information.

Original issue reported on code.google.com by dchen%re...@gtempaccount.com on 22 Feb 2011 at 12:44

GoogleCodeExporter commented 9 years ago

Original comment by Helen.Ding.UQ@gmail.com on 22 Feb 2011 at 3:08

GoogleCodeExporter commented 9 years ago 
Since we decided not to support internal authentication any more, the priority 
for this bug is low.

Original comment by Helen.Ding.UQ@gmail.com on 22 Feb 2011 at 8:34

GoogleCodeExporter commented 9 years ago 
If we DECIDED not to support internal authentication ANY MORE, then I think 
it's safe to close this issue as WontFix

Original comment by dchen%re...@gtempaccount.com on 23 Feb 2011 at 12:06

GoogleCodeExporter commented 9 years ago 
WHY are we YELLING?

Actually, I don't think we should abandon all bugs with AuthInternal just yet.  
Any new Flies developers will probably have to start with internal 
authentication until we have another solution.  Just mark these issues with 
AuthInternal so we can categorise them easily.

Original comment by sean.flanigan@gmail.com on 23 Feb 2011 at 5:20

GoogleCodeExporter commented 9 years ago 
This bug is fixed in zanata 1.3

Original comment by Helen.Ding.UQ@gmail.com on 16 May 2011 at 3:10