Skip to content
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

Polylang email language after activating account #3

Open
umdevelopera opened this issue Nov 22, 2023 · 0 comments · Fixed by #6
Open

Polylang email language after activating account #3

umdevelopera opened this issue Nov 22, 2023 · 0 comments · Fixed by #6

Comments

@umdevelopera
Copy link
Owner

This is a copy of the thread "Polylang email language after activating account" in the Ultimate Member support forum.
See https://wordpress.org/support/topic/polylang-email-language-after-activating-account-2/


I use Ultimate Member with Polylang. I installed the integration plugin “Ultimate Member – Polylang”. The main language is Dutch (nl_NL), and the translated language is English (en_US). I have a few problems tho:

Problem 1:

I translated the emails I use, and created a new registration and login form which I translated to English to be used on my English pages. However, some emails arent sent in English. I will show them in order here

  • Account Activation Email: Is being sent in English, so great. However, the Account Welcome Email is not being sent in English after verifying. That one is sent in Dutch. Both the Dutch and English email use this shortcode for the verifying: {account_activation_link}.
    When I verify by clicking the button, it sents me straight to the Dutch “/my-account” page aswell. I have a “/en/my-account” page for the English version, but every new registered person is being sent to “/my-account” (since both Dutch and English users are both assigned the role “Customer”);
  • Account Welcome Email: Is not being sent in English, but in Dutch;
  • Account Deleted Email: Is Is not being sent in English, but in Dutch;

Problem 2:

I also use Password Reset Email and Password Changed Email, but when I put in my email to reset the password in the password reset form, it only works on the Dutch translated page, not on the English translated page.

When I do it on the English translated page, I get no message and also no email is being sent out.

When I do it on the Dutch translated page, it works, but of course I get the emails in Dutch.

Note that I have not set Polylang to “detect browser language”. If there are translated shortcodes for {account_activation_link} that is for English or another translated language, like: {account_activation_link_en} and {account_activation_link_nl}, maybe that would solve problem 1.

Another solution might be creating different user roles per language, but I see that conflicting with other aspects of my webstore, including transactional woocommerce emails. Also, I do not know how to send translated UM emails to certain user roles.

For problem 2 I have no idea what could be happening.

Any help would be HIGHLY appreciated. I know this is a lot, but I hope we can get this working (also for other people facing this issue).

UPDATE: changing the redirect of the “Customer” role from “/my-account” to “/en/my-account” and then testing still sends me, after clicking the verify account button to the Dutch my-account page (and still sends the Account Welcome Email in Dutch)

UPDATE: I added a language dropdown in the registration progress according to this tutorial: https://docs.ultimatemember.com/article/1596-site-language-custom-field.

Unfortunately, that didn’t help. Although it changes the site language in the User profile to English (United States), after activating the account via the email button, I still get sent to the Dutch my-account page and the Welcome email is still in Dutch aswell, isntead of English (what I selected at the registration process).


The page I need help with: http://www.vestie.nl/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant