I had a problem with the ASP.NET CreateUserWizard, which was giving me the 'Duplicate user name!' exception, even though the user name I was trying to register did not exist.
The post also says that this problem exists only in versions prior to 4.5.2, but I am using umbraco 4.7.0.378, and this user was at some point mysteriously created in my database anyway.
Unfortunately, I could not reproduce it, so I don't know why this invalid row was created. However, I really think that this should not be allowed to occur; an empty LoginName, however it arises, should be blocked from entering the database. If it happens again, the problem will re-emerge, until I go into the database again to remove this row.
Niels created a fix that should be in 4.7.1 that enures you can't create empty logins on class level instead of UI level that has been fixed earlier. Maybe worth to upgrade?
member with empty login name created
Hello,
I had a problem with the ASP.NET CreateUserWizard, which was giving me the 'Duplicate user name!' exception, even though the user name I was trying to register did not exist.
I found this forum post: http://our.umbraco.org/forum/developers/api-questions/12757-Duplicate-User-name-when-trying-to-add-new-member which explains that the problem is caused by a member with an empty LoginName in the database, and that you need to remove this row to fix it.
The post also says that this problem exists only in versions prior to 4.5.2, but I am using umbraco 4.7.0.378, and this user was at some point mysteriously created in my database anyway.
Unfortunately, I could not reproduce it, so I don't know why this invalid row was created. However, I really think that this should not be allowed to occur; an empty LoginName, however it arises, should be blocked from entering the database. If it happens again, the problem will re-emerge, until I go into the database again to remove this row.
Thank you.
Niels created a fix that should be in 4.7.1 that enures you can't create empty logins on class level instead of UI level that has been fixed earlier. Maybe worth to upgrade?
Cheers,
Richard
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.