#676 - Represent member email validation in CSVs
-
By Chris Graham
- Added
- 3 views
| Identifier | #676 |
|---|---|
| Issue type | Feature request or suggestion |
| Title | Represent member email validation in CSVs |
| Status | Open |
| Handling member | Deleted |
| Addon | core_cns |
| Description | Say if members have validated their accounts on the CSV (currently on has admin validation on there).
Do this by saying yes/no. When importing... If member already exists: - ignore this field if it is set to 'no'. If it is set to 'yes', mark the member as having validated their account. If it is not in the CSV, do nothing. If member does not already exist: - generate a new random validation code for this field if it is set to 'no'. If it is set to 'yes', mark the member as having validated their account. If it is not in the CSV, assume as 'yes'. |
| Steps to reproduce | |
| Additional information | This is a little complex. It is not just a matter of "yes" or "no" to Composr. There are validation codes involved, which would have already been sent out - so we don't want the CSV operation to mess with this.
When importing a member that has not validated their account, ideally we'd use the same code they know. Except that for a new member that would not be tied into this site so we can't do that. By generating a random one at least they can do a password reset, which has a tacit re-validation built in. |
| Related to | #3758 - Admins can not see users that have not validated their e-mail addresses |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".
Comments
There have been no comments yet