Uploading new members requires a password to be uploaded too

Uploading new members requires a password to be uploaded too.

Not really a problem, once you know.

But when new members are invited they will be given a username, but an empty PW.

Shouldn't the invitation email set a random password before sending the invitation (when the PW is found to be empty)?

Importing users does not require supplying a password. Remove the password column from your import CSV file and it will auto generate passwords for each imported user.

What you describe is what I expect when I don't upload a password.

However this is the e-mail that I receive.

---

Hello Test Testsson,


You have been added as a User to MySite by an Administrator.

This email has your username and password to log in to www.MySite.com/

Username: Test@mysite.com
Password:


Please do not respond to this message as it is automatically generated and is for information purposes only.

---

Password is completely empty...
So, what is then wrong.

(When I first tried to submit this post as a Reply or a Quick Reply, I got the 404 error "Call to undefined method CB\Plugin\AutoActions\Table\AutoActionTable::runAction()") several times at around 22.30)

Password is not sent in emails unless generate random password is enabled in CB > Configuration > Registration. It also is only able to be sent in the Pending email. It cannot be sent in the Welcome email except for in specific situations like confirmation enabled, approval enable, AND random password enabled as it will generate a new password after being approved.

So, in case a password is not sent in the e-mail, the lines...

Username: Test@mysite.com
Password:

... should be replaced by the lines...

Username: Test@mysite.com
Use the "forgotten password" function to retrieve/reset your password

...or so. Don't you think?

That's up to you. Use language overrides and adjust the email using an IF substitution condition on password if you like. We're not going to implement something like that just to account for specific user import cases. Normally it's best to just turn emails off entirely while performing imports.