This integration renders a language switcher in the theme's style, instead of the one TranslatePress draws itself.
In practice, the switcher looks like part of the header rather than an insert from elsewhere, and it behaves the same way on every screen size. Flags and language names come from the plugin.
#What we actually provide
Native support for TranslatePress inside our own markup.
TranslatePress translates the page as it is rendered: it matches the strings a theme printed and swaps them on the way out. That means it works against markup somebody else wrote, and anything a theme draws late or in an unusual place is where a translation layer normally goes wrong.
So the integration does two things:
- puts the switcher where the theme controls it, drawn with the theme's own components, in the header slot the theme declares
- removes the plugin's own switcher stylesheets, so they cannot fight the theme's
#What it does not do
The integration does not translate, and it does not change how translation happens or how translated content is displayed.
All of the multilingual work stays with TranslatePress and is configured there. Our part is exactly one thing: the switcher.
#What you need
The official TranslatePress plugin from wordpress.org, published by the TranslatePress team. Our integration expects that plugin specifically, and another plugin doing a similar job is not a substitute.
The order: install TranslatePress first and configure your languages there, then enable our integration.
The free plugin covers one extra language, and more than that is a paid add-on.
Unlike the hosted translation services, TranslatePress can be used for free, but the ceiling is low: one language beside your original. Additional languages, automatic translation credits and SEO features come from their paid packs, bought from them and licensed by them. That side is between you and TranslatePress, and it is not part of any theme license.
Languages are defined in TranslatePress, and the switcher shows exactly that set.
You add a language in the plugin, and their own documentation covers the setup. Nothing in the theme can add a language the plugin does not know about.
#Where it is configured
This integration has no settings page of its own, because there is nothing in it to configure.
Every switcher setting lives where the switcher is rendered, in the theme's navigation settings: the switcher source, the provider, and its position in the header.
The connection to the plugin is identical across all our themes. Where the switcher sits is different in each one.
The TranslatePress plugin itself is theirs. If a translation is wrong, missing or slow, that is a question for their support. If the switcher is in the wrong place or looks wrong, that is ours.
This integration is licensed with the theme, not on its own.
Integrations are premium functionality for customers running a Pro license of one of our themes. They are written against our themes and expect them, and we cannot support or take responsibility for what one does inside somebody else's theme. See how theme integrations work.
#Common questions
A language is missing from the switcher
Add it in TranslatePress. The switcher reflects that plugin's language list and has no list of its own to edit. On the free plugin, the list stops at one extra language.
Can I use the plugin's switcher instead?
Yes. Deactivate this integration and TranslatePress draws its own switcher again, with the stylesheets we were removing.
Do I need the paid version of TranslatePress?
Only past two languages, or for automatic translation and the multilingual SEO features. That makes it a question for their pricing, not for the theme.
Will the switcher work with the visual translation editor?
Yes. The switcher is a front end element and the translation editor is a TranslatePress screen, so the two do not interfere with each other.
The switcher does not appear at all
Check that TranslatePress is active and holds more than one language. Then check the navigation settings where the switcher is enabled and positioned. If both look right, clear any page cache: a cached header hides a correctly configured switcher more often than anything else does.
#Still stuck
Open a support ticket and say what you tried and where it stopped. Your product, your domain, a screenshot and the exact message you saw are usually enough to settle it in one reply.
Last updated
