Skip Navigation

This thread is resolved. Here is a description of the problem and solution.

Problem:
You are experiencing an issue where the frontend adminbar and the Elementor interface change languages when switching to a secondary language on your site's frontend.
Solution:
To prevent the adminbar from changing languages on the frontend and to keep the Elementor interface in the primary language, follow these steps:
1. Navigate to your profile by going to Users > Profile in your WordPress dashboard.
2. Change the admin language setting to English (United States) instead of 'Site default'. This adjustment ensures that Elementor uses your preferred language rather than switching to the selected frontend language.
If you have already set this or if the issue persists after making this change, we recommend opening a new support ticket for further assistance. Additionally, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins.

If this solution does not resolve your issue or seems outdated, please contact us through our support forum for further assistance: WPML Support Forum.

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.

This topic contains 5 replies, has 0 voices.

Last updated by Pieter 2 months, 4 weeks ago.

Assisted by: Lucas Vidal de Andrade.

Author Posts
March 5, 2025 at 12:11 pm #16778362

Pieter

Background of the issue:
I am trying to prevent the frontend adminbar from changing language when switching to a secondary language on the site's frontend. This issue is not limited to the adminbar; sites with Elementor, for example, have the entire Elementor interface changing into secondary languages.

Symptoms:
When switching language on the site's frontend, texts in the adminbar and Elementor interface change to secondary languages, which is problematic when we cannot read those languages.

Questions:
How can I prevent the adminbar from changing language on the frontend, just like there is on the backend?
Is there a way to keep the Elementor interface in the primary language on the frontend?

March 5, 2025 at 1:28 pm #16778945

Lucas Vidal de Andrade
WPML Supporter since 11/2023

Languages: English (English ) Spanish (Español ) German (Deutsch ) Portuguese (Brazil) (Português )

Timezone: America/Sao_Paulo (GMT-03:00)

Hey there,

The admin panel's language is set on the user level. That means that each user can have its own, independent, display language in the back end.

To achieve what you want, please go to Users > Profile and choose the display language. Make sure to uncheck "Set admin language as editing language". Let me know if that solves it for you.

You can find more details here:
https://wpml.org/documentation/getting-started-guide/language-setup/#admin-language

March 5, 2025 at 1:34 pm #16779064

Pieter

Hi Lucas,

Please very carefully read my message again!

I am talking about FRONTEND not the backend for which your solution works.

Screenshots for if you're more visually inclined:

hidden link">English (primary language) frontend

hidden link">Portuguese (secondary language) frontend

March 5, 2025 at 2:29 pm #16779418

Lucas Vidal de Andrade
WPML Supporter since 11/2023

Languages: English (English ) Spanish (Español ) German (Deutsch ) Portuguese (Brazil) (Português )

Timezone: America/Sao_Paulo (GMT-03:00)

Thank you for the screenshots. I apologize for not understanding the issue correctly from your first message.

That's the expected behavior from WPML. The admin-bar language will always match the front-end language. Unfortunately, we don't have a workaround or a quick solution to that.

If you wish, I can create a feature request. Please note that we don't have other requests for that same feature, so I cannot provide a dead-line on its implementation, or promise if it will actually be implemented, as feature requests go through a thorough analysis before being considered to be implemented.

Let me know if you have any other questions.

March 5, 2025 at 3:38 pm #16779731

Pieter

I would not call it expected behaviour, but I understand from your answer that nobody ever brought it up as being an issue.

I have tried forcing the frontend adminbar language to the primary language, but that seems something much easier said than done, so let's not waste time on that.

And for me the issue lies not so much in the adminbar language itself, but much more that in Elementor more than 50% of the interface switches to the editing language.

Here hidden link">another screenshot of a staging site running Elementor (default language English, which is also my admin language), secondary language French (among others).

Now this is definitely backend and is therewith unexpected behaviour according to what you initially thought my issue was.

Any ideas on how to force Elementor to adhere to the WPML user preference?

March 5, 2025 at 5:16 pm #16780070

Lucas Vidal de Andrade
WPML Supporter since 11/2023

Languages: English (English ) Spanish (Español ) German (Deutsch ) Portuguese (Brazil) (Português )

Timezone: America/Sao_Paulo (GMT-03:00)

Hey there,

Thank you for sharing the details. I ran some tests on a fresh installation of WordPress, Elementor and WPML, to verify what the expected behavior is. Please note that “expected”, in this context, refers to how WPML is intended to work, and not to the individual expectation of the user.

To force Elementor to use your preferred language, please go to your profile (Users > Profile) and change the admin language to English (United States). I'm recommending that because I noticed that when using “Site default” as admin language, Elementor will use the selected front end language, instead of the display one.

In case you already had this setting, or still have the issue after changing it, please let me know.

March 5, 2025 at 5:53 pm #16780210

Pieter

Interesting that using English (United States) instead of "Site default" indeed seems to do the trick.

Perhaps an idea to add that to the info page you linked to earlier?

Anyways, thanks for your attention and thinking along.