1. Home
  2. Knowledge Base
  3. Thrive Theme Builder
  4. Integrations & Third-Party Tools
  5. How to Use WPML and Translation Plugins with Thrive Theme Builder

How to Use WPML and Translation Plugins with Thrive Theme Builder

In this article, you’ll learn how to translate your Thrive Theme Builder website using WPML and TranslatePress, including how to handle template assignments, ThriveBox displays, and common translation issues.


Using WPML with Thrive Theme Builder

WPML (WordPress Multilingual Plugin) is one of the most popular translation plugins for WordPress. Thrive Theme Builder is compatible with WPML and includes specific integration points for breadcrumb translation.

How Translation Works with TTB

When you translate a page or post with WPML:

  1. WPML creates a separate WordPress post for each translation.
  2. Each translated post can have its own Thrive Architect content.
  3. Thrive Theme Builder applies templates to translated posts based on the same template matching rules as the original language.

Translating Pages and Posts

  1. Install and activate WPML and complete the WPML setup wizard.
  2. In the WordPress admin, go to the page or post you want to translate.
  3. Use the WPML language switcher (usually in the admin bar or post editor sidebar) to create a translation for the desired language.
  4. WPML creates a new post for the translation. Open it in the WordPress editor.
  5. Click Launch Thrive Architect to edit the translated content in the visual editor.
  6. Design the translated page content. You can use a completely different layout or recreate the original design with translated text.
  7. Save your changes.

Why a Translated Page May Load a Different Template

A common issue with WPML is that a translated page or post loads on a different template than the original.

This happens because Thrive Theme Builder’s template assignment system matches templates based on post attributes. When WPML creates a translated post, it may have different attributes (category, tag, post type settings) than the original.

To fix this:

  1. In the WordPress admin, open the translated page or post.
  2. Launch Thrive Architect.
  3. Access the page settings and check which template is assigned.
  4. If the wrong template is assigned, manually select the correct template—the same one used by the original-language version.
  5. Save your changes.

Tip: When creating translated versions of pages, always verify the template assignment matches the original language version.

Displaying ThriveBoxes on WPML-Translated Pages

ThriveBoxes (pop-ups created with Thrive Architect) may not display correctly on WPML-translated pages by default because WPML treats each language as a separate context.

To display a ThriveBox on translated pages:

  1. Create the ThriveBox in your default language as usual.
  2. In WPML, translate the ThriveBox the same way you translate pages—create a new language version.
  3. Design the translated ThriveBox content in Thrive Architect.
  4. On the translated page where you want the ThriveBox to appear, make sure the trigger (button, link, or automatic display rule) references the translated ThriveBox, not the original-language version.

Note: If you’re using Thrive Leads to display opt-in forms on translated pages, make sure the Thrive Leads display rules include the translated page or post.

Thrive Theme Builder automatically registers breadcrumb labels with WPML for translation. This means you can translate default breadcrumb text (such as “Home” and “Blog”) into your site’s other languages:

  1. In the WordPress admin, go to WPML > String Translation.
  2. Search for strings in the Breadcrumbs domain.
  3. Translate the breadcrumb labels (Home, Blog, etc.) into each language.
  4. Save your translations.

Using TranslatePress with Thrive Theme Builder

TranslatePress takes a different approach to translation—instead of creating separate posts for each language, it lets you translate directly from the front end of your site.

How TranslatePress Works with TTB

  1. Install and activate TranslatePress.
  2. Go to Settings > TranslatePress and configure your languages.
  3. Navigate to any page on your site’s front end.
  4. Click the Translate Page button in the WordPress admin bar.
  5. The TranslatePress visual editor opens, showing your page as visitors see it.
  6. Click on any text element to translate it. This includes:
    • Page content created in Thrive Architect.
    • Template elements from Thrive Theme Builder (header, footer, sidebar text).
    • Menu items and widget text.
  7. Type the translation in the side panel.
  8. Save your translations.

Key Differences from WPML

FeatureWPMLTranslatePress
Translation methodSeparate post per languageFront-end visual translation
Template assignmentEach translation can have different templateSame template, translated in place
Thrive Architect editingEdit each language separately in ArchitectTranslate from front end
ThriveBox handlingSeparate ThriveBox per languageTranslate ThriveBox text from front end

Limitations

  • TranslatePress translates visible text on the front end. If your Thrive Architect design includes content that’s conditionally hidden (display rules, responsive visibility), you may need to navigate to different states to translate all content.
  • Template-level content (headers, footers) is shared across pages, so translating it on one page applies the translation everywhere.

Best Practices

  • Choose one translation plugin — Don’t use WPML and TranslatePress simultaneously. Pick one and stick with it.
  • Verify template assignments after translating — With WPML, always check that translated pages use the correct Thrive Theme Builder template.
  • Translate template-level content — Don’t forget to translate header text, footer text, menu items, and breadcrumb labels in addition to page content.
  • Test the language switcher — After setting up translations, test the language switcher on the front end to verify all pages load with the correct content and template.
  • Translate ThriveBoxes separately — With WPML, each ThriveBox needs its own translated version. Make sure triggers on translated pages point to the translated ThriveBox.
Was this article helpful?

Related Articles

>