[Resolved] Account page not translated

Hello Otto,

I have checked the site again, and your solution did not fix the issue.
In fact, the situation is now worse than before:
• When the site is set to Dutch, clicking “Home” suddenly switches the entire site back to English
• Dutch category pages still show English text
• The homepage language behavior is broken
• The part you said was “translated” is still not translated
• Everything was functioning better before your modification

This means that your recent changes have introduced new problems instead of resolving the original issue.

I paid for WPML specifically so the language logic would work correctly.
Right now it is not working, and changing the source language has clearly broken the behavior even more.

Please stop applying changes that make things worse.
I need these issues properly fixed, and if you cannot resolve them, please escalate this ticket to a senior WPML technician who can.

Thank you.

Best regards,
Youssef

Hello Otto,

Thank you for your reply.

I want to make it very clear that the problem is not solved.
In fact, after the recent changes, the situation became worse:
• The Dutch homepage now switches back to English automatically
• Dutch category pages are showing English text
• WPML language logic is not working correctly anymore
• Nothing has been fixed, and new issues have been added

Because of this, I cannot mark this issue as resolved.

If another supporter will take over the case, that is perfectly fine —
but I expect the original behaviour to be restored and the translation logic to work correctly again.

This is a paid plugin, and I expect a proper solution, not additional problems.

Please make sure the next supporter fixes the issues created this morning and fully resolves the original problem.

Thank you.

Best regards,
Youssef

Hello Bobby,

Thank you for your explanation.
However, I still have two major issues that must be solved, because they are NOT working correctly and I cannot fix them myself.

1. “Add to Wishlist” does NOT translate into Dutch

All other languages translate correctly (French, German, Italian, Spanish), except Dutch.
The string is translated inside WPML, the source is correct, but WPML does not output the Dutch translation on the frontend.

As you can see in the screenshot:

The Dutch translation exists ✔️

All other languages work ✔️

Dutch always falls back to English ❌

This is not a hardcoded string — it comes from the TI WooCommerce Wishlist plugin and should be fully translatable.
So something is wrong on WPML’s side with the Dutch language mapping.

Please check why WPML is ignoring the Dutch translation for this string and fix it.

2. This MailPoet checkbox sentence does NOT translate:

“I would like to receive exclusive emails with discounts and product information.”

This text shows on the checkout page and stays English in all cases.
It is translated inside MailPoet AND registered in WPML, but WPML still does not output the Dutch version.

Again:

The translation exists ✔️

WPML does NOT display the Dutch version ❌

This is NOT hardcoded — it is generated by MailPoet and should be detected by WPML ✔️

Conclusion

The remaining problems are now pure WPML translation failures, not hardcoded links.

Please fix:

“Add to Wishlist” → Dutch translation not showing

MailPoet checkbox sentence → Dutch translation not showing

I cannot solve this myself — this must be corrected on WPML’s side.

Thank you,
Bram

Hello Bobby,

Thank you again for your amazing help.

Everything is working great now except for one last string:

“I would like to receive exclusive emails with discounts and product information.”

This string stays in English on all checkout pages, even though it is translated in WPML.

Could you please check why this specific string is not being applied on the front-end?

Thank you very much!

Kind regards,
Youssef

Hi Bobby,
Thank you very much for your detailed follow-up and for checking this with both the WPML compatibility team and MailPoet’s support. I really appreciate the effort and clarity.

It’s clear now that the remaining string is caused by MailPoet not being fully compatible with WPML.

Thank you for pointing me to the related threads and official notices — this helps a lot.

I will look into an alternative solution on my side (either replacing the field or using another opt-in method).

Thanks again for all your help, your video and your fast support.
You solved everything perfectly except for this MailPoet limitation, so I really appreciate it. 🙏😊

Best regards,
Youssef
GetVitaCore