Conversation
TimWolla
commented
Nov 18, 2020
TimWolla
commented
- Add Setup::getUser() method
- Add EmailMultifactorMethod
| <item name="wcf.user.security.multifactor.email.code"><![CDATA[Einmalcode]]></item> | ||
| <item name="wcf.user.security.multifactor.email.code.description"><![CDATA[Der Einmalcode wurde um <strong>{$lastCode|date:'H:i:s'}</strong> an {if LANGUAGE_USE_INFORMAL_VARIANT}deine{else}Ihre{/if} E-Mail-Adresse bei <strong>{$emailDomain}</strong> gesendet.]]></item> | ||
| <item name="wcf.user.security.multifactor.email.subject"><![CDATA[{if LANGUAGE_USE_INFORMAL_VARIANT}Dein{else}Ihr{/if} Einmalcode for {@PAGE_TITLE|language}]]></item> | ||
| <item name="wcf.user.security.multifactor.email.body.html"><![CDATA[{if LANGUAGE_USE_INFORMAL_VARIANT}Dein{else}Ihr{/if} Einmalcode lautet: <pre>{$code}</pre>]]></item> |
There was a problem hiding this comment.
I would expect a short text here why this email came. I would also highlight the one-time code with some CSS (bigger and possibly in a box in the middle), so that it can be found visually quickly.
There was a problem hiding this comment.
The phrasing is somewhat intentional here for several reasons:
- The email address most likely is already confirmed to belong to the account.
- Thus the email does not go to unrelated persons.
- The user expects the email to arrive, because they are sitting right in front of a form that requires it.
That's why I opted to keep the email free from any fluff and get straight to the point. Specifically I avoided including any links whatsoever to reduce chances for phishing based off this type of verification email. As a best practice also avoided including personal information in case the email gets misrouted for some reason.
But I'm happy to make some adjustments to the phrasing / layout if you feel that the UX improvement weights enough.
3 participants
