Skip Navigation

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 7:00 – 12:00 7:00 – 12:00 7:00 – 12:00 7:00 – 12:00 7:00 – 12:00 -
- 13:00 – 15:00 13:00 – 15:00 13:00 – 15:00 13:00 – 15:00 13:00 – 15:00 -

Supporter timezone: Europe/Madrid (GMT+02:00)

Tagged: 

This topic contains 18 replies, has 1 voice.

Last updated by Carlos Rojas 3 days, 4 hours ago.

Assisted by: Carlos Rojas.

Author Posts
June 6, 2025 at 9:22 pm #17114965

Yves Vandeuren

Background of the issue:
I am trying to get French translations to be used for Ninja Forms admin notifications when sending from a French page. Translations are correctly set for this specific form ('ninja-forms-1' domain in String Translation). Everything is up to date, including WordPress, theme, and plugins. The issue persists when using the default WordPress theme and only enabling the following plugins: Ninja Forms, Ninja Forms Multilingual, WP Mail Logging, WP Mail SMTP, WPML Multilingual CMS, and WPML String Translation. I already tried the fixes mentioned in these forum posts: https://wpml.org/forums/topic/ninja-forms-confirmation-email-not-translated-when-logged-out/ and https://wpml.org/forums/topic/i-have-problem-with-translating-ninja-forms-to-croatian/. This is a staging website. The issue doesn't seem to appear on the live site hidden link. I also tried sending the form with the exact same plugin versions as the live site, but the issue persists. Link to a page where the issue can be seen: hidden link.

Symptoms:
The client email (sent to the visitor) is correctly translated, but the admin notification email is sent using the English texts instead of French.

Questions:
Why is the admin notification email not being translated to French?
What steps can I take to resolve the translation issue for admin notifications?

June 9, 2025 at 6:47 am #17117026

Christopher Amirian
WPML Supporter since 07/2020

Languages: English (English )

Timezone: Asia/Yerevan (GMT+04:00)

Hi,

Welcome to WPML support. I will answer this ticket before it is assigned to one of my colleagues.

Please consider that there is a distinction between the two types of emails and the source of generation.

If an email is generated while on the front end of the website it takes the language that the page is currently in in the front end.

But WordPress does not allow the same thing on the admin side. If the email is generated from the admin, it will take the profile language of the admin user that the email generates from.

For testing you can go to WP Dashboarad > Users > Profile and change the admin language there and see if the generated email now takes the language you selected there.

Thanks.

June 10, 2025 at 12:32 pm #17121838

Yves Vandeuren

Hello Christopher,

Thanks for the answer.

I think I understand the distinction you're talking about, but the issue I'm experiencing occurs on the frontend, not the backend/admin side.
When you mention the "admin side", does that simply mean being logged in as admin on the frontend ? Or being on an admin page (like /wp-admin or so) ?

I did my form submission tests while being logged in as admin, and indeed I confirm the admin email notification is using my profile language in this case (if I switch my profile from EN to FR, the admin email is sent in FR).
While that's not much of an issue in my specific case, I don't consider it being the "admin side". I'm still submitting the form from the frontend like any visitor.

The real issue is, if I submit the form in private browsing (so not logged in), both EN and FR versions of the page will send the admin email notification in EN, instead of the page language...
My client (the website owner) asked me to put "[EN]" or "[FR]" at the end of the email subject, for the form submissions, depending if the form is sent from the EN or FR version of the website.
That's something he needs to correctly sort the emails on his end.
I configured the forms that way back in January and I don't see this issue on the live site. Each time a form is sent from the EN version of the website, the email admin notification is sent in EN, and for FR version, it's always sent in FR as well.

At least, that's what I see in the email logs... (each time we have a form submission, the admin email notification has the same language as the page and the visitor email notification)
While testing (on the live environment) by duplicating a form and setting up the translations then submitting the form (private browsing, not logged in), I also get the admin notification in EN no matter if I'm on the FR or EN page.

Is there something I'm missing here ?
How to make sure the admin email is sent in the language of the page the form has been sent from ?
What about visitors that are not logged in and so don't have a "profile language" ?
I supposed the logic here would be to take the page language instead, but it doesn't seem to be the case as explained above.

Thanks in advance for the help.

June 13, 2025 at 9:06 am #17132352

Yves Vandeuren

Hello,

It's been a few days since my last reply.
Any news about my issue ?

Thanks in advance.

June 13, 2025 at 11:15 am #17133047

Carlos Rojas
WPML Supporter since 03/2017

Languages: English (English ) Spanish (Español )

Timezone: Europe/Madrid (GMT+02:00)

Hello,
My name is Carlos, and I will continue working on this ticket.

Please check if the issue you are experiencing is the same described in this erratum page: https://wpml.org/errata/ninja-forms-merge-tags-in-emails-actions-not-translated/

June 13, 2025 at 7:03 pm #17134554

Yves Vandeuren

Hello Carlos,

This doesn't seem to be the case.
For example, I don't use any merge tag in the email subject, and as described above, I still have translation issues.
So I'd say no.

June 16, 2025 at 9:23 am #17137685

Carlos Rojas
WPML Supporter since 03/2017

Languages: English (English ) Spanish (Español )

Timezone: Europe/Madrid (GMT+02:00)

Thank you very much for your feedback.

1.- Please share some screenshots or a link to a video where the untranslated texts can be seen.

2.- Also, share the access credentials to the site in your next message, which I have set private. That way, I can take a deeper look.

Confirm you have created a full site backup that you can restore if necessary.

June 17, 2025 at 9:29 am #17141486

Yves Vandeuren

For some reason I can't edit my reply.
Just in case... The admin email is actually written in French for both languages (my client is French so no point in translating the body).
But the subject should contain [EN] or [FR] at the end depending on the language of the page from which the form has been submitted.
And in this case, the subject has always [EN] at the end, even for the French page.

June 17, 2025 at 9:41 am #17141557

Carlos Rojas
WPML Supporter since 03/2017

Languages: English (English ) Spanish (Español )

Timezone: Europe/Madrid (GMT+02:00)

Thank you for your message.

The Ninja Forms must be translated via WPML -> Translation Management and not via String Translation as described in this guide: https://wpml.org/documentation/related-projects/creating-multilingual-forms-using-ninja-forms-and-wpml/

I kindly ask you to translate the forms following the steps described in the link I shared and double-check if the issue has disappeared.

June 17, 2025 at 10:28 am #17141844

Yves Vandeuren

Thank you Carlos.

I'm checking that right now.

May I already ask if the translations I've already done of the different strings of the forms, on the String Translation screen, could be source of conflict with the translations I'm about to do in the Translation Management screen ?
Or can I just translate the forms in Translation Management and leave it that way in the String Translation ?

Thanks.

June 17, 2025 at 10:37 am #17141889

Carlos Rojas
WPML Supporter since 03/2017

Languages: English (English ) Spanish (Español )

Timezone: Europe/Madrid (GMT+02:00)

Hi,

You can leave the translations in String Translation and translate the forms in Translation Management 🙂

June 17, 2025 at 10:55 am #17141958

Yves Vandeuren

I translated the form using the Translation Management feature but the issue persists.

One thing which is fixed is the client email - I receive the client email in the correct language depending if I submit the form on the EN or FR page. It was not the case before.

But the admin email is again always sent in EN, even if the form has been submitted on the FR page.
I tried on both stagings, in private browsing without being logged in.

June 17, 2025 at 11:26 am #17142078

Carlos Rojas
WPML Supporter since 03/2017

Languages: English (English ) Spanish (Español )

Timezone: Europe/Madrid (GMT+02:00)

Hi,

I searched for 'Form submitted successfully.' in WPML -> String Translation and I found that there were a few untranslated strings under other domains. I translated them all except for one that is different: hidden link

Please make sure you have translated all the strings from the emails and share a URL where one of these strings can be edited in the original language.

June 17, 2025 at 12:35 pm #17142388

Yves Vandeuren

Using your link, I see that you translated the success message of forms 4 and 6.
(domains : "ninja-forms-4" / "ninja-forms-6")
The form I'm testing is ID 1.
If you didn't know, the domain contains the form ID at the end, so for my test form, the domain is "ninja-forms-1", which was already translated.

But, to be honest, I don't even understand what's your point here.
My issue isn't about Success messages.
It's about email actions.

Also, you told me earlier to translate using Translation Management and not to use String Translation.

In Translation Management, I already translated all strings of my form ID 1 in FR. (default language is EN)

Anyway, I've translated the last success message in the link you provided (domain "ninja-forms-3") but it obviously doesn't change anything to my issue described above.
I tested again my form, same issue.
FYI I cleared the website cache before and tested in private browsing again.

If that can help you understanding my issue, I joined an image of my inbox.

You can see :
- 11 emails "Nouvelle demande de contact [EN]"
- 7 emails "Merci pour votre message"
- 4 emails "Thank you for your message"

What I should have received :
- 7 emails "Nouvelle demande de contact [FR]"
- 7 emails "Merci pour votre message"
- 4 emails "Nouvelle demande de contact [EN]"
- 4 emails "Thank you for your message"

(I configured the form so I receive both client and admin email notifications, for testing purposes)

Lastly, I don't really understand what you're asking exactly here :
"share a URL where one of these strings can be edited in the original language"

If you want to edit a string of this form (ID 1) in the original language (EN), here it is :
hidden link

To be more specific, my issue is with the Email Action "Email Notification".
That's the one we send to the website admin ("Nouvelle demande de contact" in my attached screenshot).
That's the one always sending the string from EN language.
Here the original EN string for the subject of this email action :
"Nouvelle demande de contact [EN]"
And here's the translation I've set up and that should be used when the form is submitted on a FR page :
"Nouvelle demande de contact [FR]"
But as you can see, it's always using the original string and never the translated.

Thanks.

inbox.png
June 17, 2025 at 1:20 pm #17142650

Carlos Rojas
WPML Supporter since 03/2017

Languages: English (English ) Spanish (Español )

Timezone: Europe/Madrid (GMT+02:00)

Thank you very much for your message.

I suspect we might be facing a compatibility issue; for that reason, I have created a fresh new WordPress installation with the WPML plugins and Ninja Forms.

I kindly ask you to access the sandbox site using this link: hidden link and create/translate a test form.

I have already installed a Mail log plugin to access the emails sent.

There is no need to add real information, just test information that allows to check if the issue persists or disappears in this sandbox scenario.