Zero2Cool
2012-07-15T00:01:51Z
A member registered a second time because they forgot their old password. I tried updating the old account with the new email and received this message below.

Sponsor
tha_watcha
2012-07-15T04:09:24Z
Please check if the membership connection string has the value require unique email is set to true.
UserPostedImage
Zero2Cool
2012-07-15T16:23:30Z
Originally Posted by: tha_watcha 

Please check if the membership connection string has the value require unique email is set to true.


Yes sir, it is set to true. I do not wish to have multiple members with the same email. Out of curiosity I tried updating a members profile with what I knew would be a duplicate email assuming a YAF dialog box would display instead of "Server Error in '/' Application."

<add name="AspNetSqlMembershipProvider" applicationName="DotNetNuke" connectionStringName="yafnet" enablePasswordReset="true" enablePasswordRetrieval="false" maxInvalidPasswordAttempts="5" minRequiredNonalphanumericCharacters="0" minRequiredPasswordLength="5" passwordAttemptWindow="15" passwordFormat="Hashed" requiresQuestionAndAnswer="false" requiresUniqueEmail="true" type="System.Web.Security.SqlMembershipProvider" />

I'm no longer using DotNetNuke, but I'm not sure how to get it working without that applicationName value set as such and it's not hurting anything, well, to my knowledge, lol.
squirrel
2012-07-15T16:48:03Z
Really the duplcate email thing has been an issue for several versions.

It should be as easy to implement a check for this:

1. checking the config to see if duplicate emails are allowed (and really, duplicate emails should never be allowed in a registration system).
2. running a SELECT statement to check for the email address exists. Additionally, check the 'awaiting confirmation' table as well.
3. if the recordset returns anything more than 0 records, the system should catch the exception and throw an alert.

I'm sure it's more complicated than that or it would have been fixed already, but still -- and it's understandable if nothing has been done with it because it's a host/admin error only.


If you can't find it using the forum search, try my signature link -- searches this site using Google: Google is my Friend 
Dr-Hack
2014-02-04T13:33:25Z
I see that this issue is still open in the wild.

Turned UniqueEmails to "true" yesterday" and today whiel uploading an attachment got the error as zero2cool shared and later whole DNN site crashed. had to turn it to false for now .
JP
  •  JP
  • 100% (Exalted)
  • YAF Leader
2014-02-04T19:53:41Z
Haven't had this issue - but when I update an existing user email directly in the db, I do like this:

1 - Update the "Email" field in the yaf_User table...

2 - Update the "Email" and "EmailLwd" fields in the yaf_prov_membership table...

I always use lower-case in the email addresses in all fields.

Since the user profile dialog email update did not work so well in 1.9.x.x, I've done this many many times...
Don't know if it's fixed in 2.x since I haven't had any requests from users to change their email.

Same goes for changing a user name, update both tables.

If you get errors, you most likely have duplicate emails in the db and that is as designed with unique primary keys, since you should
not have 2 users with the same email address...

I am not running DNN, so maybe my comments are not valid at all in this particular case...

He who asks a question is a fool for five minutes. He who does not ask a question remains a fool forever. [Old Chinese Proverb]

About Us

The YAF.NET is an open source .NET forum project. YAF.NET is supported by an team of international developers who are build community by building community software.

Powered by Resharper Donate with PayPal button

Project Twitter Updates

Copyright © YetAnotherForum.NET & Ingo Herbote. All rights reserved