-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
I18n support for emails #2886
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
Comments
That's actually a good idea for a first PR, @Hitabis |
Email adapter like mailgun have templates, cant you just add the language there? |
@agent3bood the goal would be to have multiple languages. You could detect the language in the useragent for the html pages. It would be harder within the mails. But we always save the language in the installation. |
@Hitabis does parse currently save the user language ?
|
We were able to accomplish this with express middleware and using different email templates. First we intercept the request: Then we get the user object and check their locale (our application saves locales), and then respond with the appropriate language template. Hope that helps! |
Email localization can now easily be accomplished with the Parse Server API Mail Adapter. The adapter is still new, if you have any feedback for improvement or encounter any bugs, please file an issue. |
At the moment all emails to the user are hardcoded in src/Controllers/UserController.js.
Has anyone a fork supporting other languages?
Are there any plans to implenent I18n in emails and html-files?
The text was updated successfully, but these errors were encountered: