Skip to content

Translating Divi

On this page

Translating Divi pages by hand in the Visual Builder is part of the free version (version 2.6.0 and
later). Translating them automatically with AI requires PRO (version 2.5.0 and later). The
texts of a Divi page are kept as segments with a translation memory in the free version (version
2.8.0 and later).

A Divi site is more than its pages. The header and footer usually come from the Theme Builder,
and a promo box or a call to action that appears on many pages is often a global module kept in
the Divi Library. Each of these is stored separately from the page that shows it, so each is
translated separately: translate the page, and its header, footer and global modules still need
their own translation.

You translate all of them the way you build them – in the Divi Visual Builder – or, with PRO,
automatically with AI.

#Turning it on

  1. Go to LATW Multilingual → Settings → Translation.
  2. Under Page builders, tick Divi.
  3. Under Content Types, tick what you want to translate besides pages and posts:
    • Divi: Header Template, Divi: Body Template and Divi: Footer Template – the
      layouts of the Theme Builder;
    • Divi: Library (global modules and saved layouts) – the Divi Library, which is where global
      modules live.
  4. Click Save changes.

The Divi types appear only while the Divi theme is active.

#Translating a page by hand

Go to LATW Multilingual → Posts, open the Pages tab, and click the pencil next to a language
in the Languages column. The page opens in the Divi Visual Builder, at its address in that
language (for example /pl/about/; with languages on subdomains or domains the visual builder opens on your main
address and shows the page in that language), showing the original the first time and your translation every
time after.

Edit the texts in place, as you would when building the page, and click Save. The translation
is saved for that language only; the original page is not touched.

You can also start from the page itself: open it in the translated language on the front end and
click Enable Visual Builder in the admin bar. You are taken to the translation, not to the
original.

A translation can also be styled differently from the original – a smaller font for a heading that
is longer in German, a different image for another market. Those changes stay in that language.

The Visual Builder has no field for the page’s address. To give the translation its own URL slug,
open the page’s segment editor (the list icon next to the language in the LATW Translations
box) and use the URL slug field at the top – see Translating Elementor for how it works.

The Theme Builder layouts and the Divi Library have their own tabs on LATW Multilingual → Posts:
Header Templates, Body Templates, Footer Templates and Layouts. Translate them there,
with the pencil next to a language, exactly like a page. The layout opens in the Visual Builder on
its own, without a page around it.

Once saved, the translated header and footer are shown on every page of that language that uses
them, and a translated global module appears on every page that contains it.

Why not straight from the page? When you translate a page, the Visual Builder still shows the
header and footer around it – in the original language, because they are not part of that
translation. Changes made to them there are refused – Divi reports that the save failed – instead
of being saved over your original header. Translate them from their own tab.

#Translating with AI

Requires PRO.

Tick the pages or layouts on LATW Multilingual → Posts and click Translate Selected, or use
the Translate button on a single row. The same works for the header, footer and Library tabs.

Only the texts of each module are sent to the translation engine: headings, body text, button
labels, image alt texts, testimonial names, form labels, drop-down options and similar. The layout,
the design settings and the links never leave your site and cannot be damaged by the translation.
The result is the same translation you would get by hand, so you can open it in the Visual Builder
afterwards and correct anything.

What it costs. Every translation is a request to your AI engine and is billed by it. A page is
charged for the text of all of its modules. A global module is also stored as a copy inside every
page that uses it, so its text is translated with each of those pages as well as on its own in the
Layouts tab. The translation of the page’s copy is only shown if you ever unlink the module;
the text you see comes from the translated Library item.

Translating again only translates what changed. The texts of a Divi page are segments, like the
paragraphs of any other page (see Translation Memory and Segments): a text that appears twice is
translated once, texts you corrected by hand are not replaced, and after you edit one module of the
original only that module’s text is translated again. If you add, remove or move modules in the
original, the translation follows the new layout.

If you change the design of a module in a translation by hand – or add or remove a module there –
that translation’s layout no longer matches the original. It is kept exactly as you made it and
is no longer updated automatically; click Rebuild from the original layout in the notice on the
page to go back.

#What this does not do

  • Divi 5 is not supported. It stores pages in a different way; this page describes Divi 4.
  • Modules from third-party Divi add-ons are translated only if they use Divi’s own names for
    their text settings. Texts in other settings stay in the original language when translated with
    AI; you can still translate them by hand in the Visual Builder.
  • The Code module is never sent to AI. Its content stays as it is in every language unless you
    change it by hand.
  • Styles on translated pages are printed inside the page. Divi normally keeps a page’s styles in
    a cached file, one per page, shared by every language. Pages in a translated language print their
    styles inside the page instead (Divi’s own “Static CSS File Generation: off” mode), so a
    translation with its own styling never changes the original, and the other way round. The
    original language keeps using the cached file.

#Troubleshooting

The header or footer stays in the original language. Check that Divi: Header Template and
Divi: Footer Template are ticked under Content Types, and that the layout has a translation
on its tab on the Posts screen.

A global module stays in the original language on every page. Translate it on the Layouts
tab – the page’s own translation does not change it.

The pencil opens the block editor instead of the Visual Builder. Divi is not ticked under
Page builders.

#Developer reference

  • Builder integration: LATWM_Builder_Divi (free plugin). Divi is a theme, so builder
    integrations that are not available on plugins_loaded register again on after_setup_theme
    (priority 100).
  • The Visual Builder’s AJAX carries no Referer, so the session flags (latwm_lang, latwm_post)
    are added to the URL of every admin-ajax.php request by an inline script on the builder page.
  • Content: the translated page is the post_content overlay row. The builder loads it through
    et_fb_load_raw_post_content; Theme Builder layouts are served through et_builder_render_layout.
  • Filter latwm_post_type_choices (name => label) adds non-public types to Content Types.
  • Segments: includes/segments/divi-text.php finds the module texts (attributes and module bodies)
    and LATWM_Builder_Segmenters::divi() turns them into the segments of post_content.
    Filters: latwm_divi_text_attributes (attribute names treated as text),
    latwm_divi_raw_content_modules (modules whose content is never translated) and
    latwm_divi_module_prefixes (shortcode prefixes of third-party modules, default et_pb_). With
    PRO the older latwmp_divi_text_attributes, latwmp_divi_raw_content_modules and
    latwmp_divi_module_prefixes keep working.