nasko7
Forum Replies Created
-
Hi Javier, I donated.
This is TransactionID: ********75087
When you have time please solve somehow duplicated usernames issues when updating users. For now we will use Username and Email fields to have same values in CSV file.
Thank you.
- This reply was modified 5 years, 6 months ago by nasko7.
Hi Crios,
when importing CSV file: the new users are created, password is generated/or provided from CSV Data – the email is sent.
When updating old users, if you check
* Do you wish to send this mail also to users that are being updated? – CHECK
They will receive same email as the new users. With random generated password or CSV data provided.
Because you checked
* Never update passwords – NEVER UPDATE PASSWORDS…
This password will not be updated. That’s why you can still can login with the old password, but receive email with new password.Solutions:
Option 1) DONT SEND EMAILS TO UPDATED USERS
* Do you wish to send this mail also to users that are being updated? – UN-CHECKOption 2) the plugin author to make separate template in the Plugin settings for Updated User. We will have 2 email templates (1 for creating new users, 2 for updating old users)
I am using Option 1 now, but will be good to have separate emails and to send separate messages to our users.
Yes, that will solve our problem.
You identify which user is new or old by username, not by email. You can make option to choose which field to be leading/primary (username or email) in comparing process. I know it’s a lot of refactoring but you can make more flexible the process of updating users. If email is unique we just will override the email and will update other fields.
For now, the way you offered is okay. Let it be suffix ‘duplicated_username’ + ‘_3013’.
Which PayPal account do you want to donate
Arbimportusers@gm… Or imalrod ?Thanks
Yes but by mistake, the admin can mess up, some accounts and he will not understand what happened. Yes he is responsible, he has the admin rights.
How should this checkbox “allow updating emails of users by their username” work?
if I click disallow,
1) is it going to add the duplicated username CSV row as a new user – with prefixed username?
OR
2) it will be skipped?We import different CSV files with different companies’ list of employees. The unique person is identified by his working email.
Thanks.
Thanks, it works perfectly.
Yes, “Never update passwords” sounds good name for this option.
Thanks.
- This reply was modified 5 years, 6 months ago by nasko7.
Thanks for the fast response.
I want to use single CSV file for creating and updating users. I don’t want to edit CSV file and to change fields, or to have 2 different files 1st for creating and 2nd for updating.I think it’s good feature the plugin to manage this.
This is my CSV I have 3 columns
Username, Email, subscription_date
test, [email protected], 2021-12-10I want to use the same file for bulk register/update users.
– Register will add new user and create random password
– Update only will update their subscription_date meta field.Thanks.