New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unify user email templates #1344

Closed
natt-tester opened this Issue Nov 13, 2018 · 4 comments

Comments

Projects
None yet
2 participants
@natt-tester

natt-tester commented Nov 13, 2018

Right now we have one improved email template for password reset that uses the user name and good formatting:

pwd_reset_mail

Can we do the same with the rest of the confirmation emails we send to users, e.g. registration confirmation email:

reg_confirm_mail

It could be something like "Hi [name], A user has been registered for [email]. Click the following link to confirm it: [link]"

or make smtp config email:

smtp_config_email

something like this: "Hi [name],
your SMTP server configuration has been successfully verified.

Also, it would be great to have all of the email strings in one file so that it would be easier to compare/edit them if necessary.

@syntrydy

This comment has been minimized.

Contributor

syntrydy commented Nov 17, 2018

Here is the template i propose for user registration mail.

image

@syntrydy

This comment has been minimized.

Contributor

syntrydy commented Nov 17, 2018

image

@syntrydy

This comment has been minimized.

Contributor

syntrydy commented Nov 17, 2018

@syntrydy

This comment has been minimized.

Contributor

syntrydy commented Nov 17, 2018

We don't have to customize this one, only admin see this, No useful even if it is write in Hexadecimal.
The goal is just to test The mail server settings is correct and messages can be send out.
image

syntrydy pushed a commit that referenced this issue Nov 17, 2018

syntrydy added a commit that referenced this issue Nov 17, 2018

Merge pull request #1354 from /issues/1344
Unify user email templates #1344

syntrydy pushed a commit that referenced this issue Nov 17, 2018

@syntrydy syntrydy closed this Nov 18, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment