Yesterday i imported 10.000 members to Umbraco using the CMSImport.
Before that i had of course tested thoroughly.
The import was configured to send an email with a new password to the imported members. The import went well and all the mails was sent. I made some quick test afterwards and everything seemed ok. I could login with the generated password and all the members was correct imported to the member section.
The problem now is that some of the members have started to write back that they can't login. Right now it seems that there are two problems:
In some of the generated passwords the pipe | is present. Some of the members simply don't know how to write this symbol. Of course you could just copy and paste from the email - but sadly not all end users are so clever :) So - is it possibly anywhere to configure wich characters are used in the password generator?
The second problem is a bit more concerning. Sadly i have only one example of this - the problem is that there could be many more. One of the members couldn't log in with the password provided in the email: y!(0)SDH - when i checked in the database i could see that the right password was: y!0)SDH I don't know if this could have anything to do with the mail client? Do you have any suggestions what could have gone wrong - or any good ideas how we can check for other generated passwords in the database which could have the same 'symptoms'? Have you seen this behavior before?
Sorry to hear you had issues with some members. I hope the most members worked ok. I'm using the default Membership API generate password method. Maybe I can change that in a future release. The Membership password is also directly inserted into the mail template so it must be the mail client that caused the other issue.
Wrong passwords and funny characters
Hi Richard
Yesterday i imported 10.000 members to Umbraco using the CMSImport.
Before that i had of course tested thoroughly.
The import was configured to send an email with a new password to the imported members. The import went well and all the mails was sent. I made some quick test afterwards and everything seemed ok. I could login with the generated password and all the members was correct imported to the member section.
The problem now is that some of the members have started to write back that they can't login. Right now it seems that there are two problems:
Hi Emil,
Sorry to hear you had issues with some members. I hope the most members worked ok. I'm using the default Membership API generate password method. Maybe I can change that in a future release. The Membership password is also directly inserted into the mail template so it must be the mail client that caused the other issue.
Best,
Richard
is working on a reply...