Since my data was migrated from an old forum that didn’t have an email field, I had to fabricate email addresses for the users. This causes issues when verifying the old email during email change, as the verification code can’t be received. For this situation, is there a recommended or effective solution? please!
Only admin addresses have to be verified to change, so make the user not an admin.
2 Likes
I’m really happy to receive such a quick reply—thank you! I just ran a test and found that even when using a non-admin user to change the email, it still requires verification of the old email. I really don’t want to go down the path of modifying the source code—it’s frustrating. Could this be an issue with the version I’m using?
There is also the Require change email confirmation admin setting (default disabled) which would force all non-staff users to perform this check as well:
Though the message in your screenshot looks like the version where it’s only asking you to verify the new email address rather than both old and new. Could you check the new email address inbox for the confirmation just to double check?
4 Likes
Thank you very much. I think I’ve figured out where the problem was — I had set “Disable emails” to “non-staff”, which caused all regular users to be unable to receive emails. You were right, regular users don’t need to verify their old email addresses. Thanks everyone for the suggestions.
4 Likes
Change the email Feild. After changing email address you can manually activate the user in the admin user page.
There is also this plugin. It is marked broken but this post another user has said to have rewrote the plugin to work with newer discourse. If self hosted you could install. Just be sure to make a backup just in case
It looks like this topic is already solved, but for this:
I don’t think that would work? What are the steps you used so I can test it out.
2 Likes
I use this method to create null accounts for testing. Sign up with a fake email address then manually activate the account using the admin account. As an extra step I adjust the t at account email settings to not send after activation also used this on our old test server as it originally had no email server except for the initial setup. Ppl that were asked to join were manually activated
I also used this idea before to restore an anonymoized account by renaming back to previous user name. Adding the email address back andanualky reactivated the account.
Can you help me understand your steps? I usually struggle to change the e-mail address of my test accounts. So I tried what you described with an anonymized test account.
- Change email in the preferences
→ a new unverified email is added - Disable and enable the account
→ old email is verified, new one is still unconfirmed
What is the step I am missing to confirm the new email?
I also tried to deactivate the user before changing the email. That didn’t work either
Did you try logging into the account after changing email and manually activating account?
It may still say email unconfirmed but you should be able to log into the account
I don’t know if core has changed r gently so will spin up a fresh test account and check
Checked the email will not change like it used to. It keeps both email addresses pr sent with the new one unverified. You can still log in with the user name. So it works for fresh accounts to not need the email verification. But email change no. On the past I could edit the email address in the admin panel. It has now moved to user preferences page.