Salta la navigazione

Your admin strings are untranslated in the site’s backend because WPML does not display translations of admin strings in your site’s backend. This means you will always see these strings in the default language, even if you have translated them and changed your user language. The translations will display on your site’s front-end or in AJAX requests.

Let’s say we want to translate our site’s tagline from our default language, English, into a secondary language, Spanish. The tagline is an example of a string that appears both in our site’s admin (by going to AppearanceCustomize and clicking Site Identity) and displays on the site’s front-end.

The tagline On the site’s backend

The Tagline on the site’s Front-End

We can translate this string by going to WPMLString Translation and searching for “tagline” in the text search. If you aren’t able to find a string you want to translate on the String Translation page, you can add it to the String Translation page.

Translate the string by clicking the plus icon under the appropriate flag.

Translating the tagline into a secondary language

Now, the new Spanish tagline will appear on the front-end when a client views the page in Spanish.

If your profile language is different from your site’s default language, this can be confusing. For example, let’s change our profile language to Spanish. You can do this by going to UsersProfile and choosing Español from the Language dropdown menu.

Changing our profile or admin language to Spanish

If we navigate to AppearanceCustomize and click Site Identity, we still see the tagline in English, the site’s default language, even though a Spanish translation exists.

The tagline still appears in the site’s default language in the backend

However, on the site’s front-end, we see the Spanish translation when we switch to Spanish, as expected.

The tagline still appears in the site’s default language in the backend

This is the expected behavior of such strings. The reason the string appears in the default language in the backend is to prevent conflicts between this text entry field and any translations that may exist.