{"id":131,"date":"2026-11-09T17:56:05","date_gmt":"2026-11-09T17:56:05","guid":{"rendered":"https:\/\/docs.latw.ai\/uncategorized\/translating-divi\/"},"modified":"2026-11-09T17:56:05","modified_gmt":"2026-11-09T17:56:05","slug":"translating-divi","status":"publish","type":"post","link":"https:\/\/docs.latw.ai\/pl\/latw-multilingual\/translating-divi\/","title":{"rendered":"Translating Divi"},"content":{"rendered":"<p><em>Translating Divi pages by hand in the Visual Builder is part of the free version (version 2.6.0 and<br \/>\nlater). Translating them automatically with AI requires <strong>PRO<\/strong> (version 2.5.0 and later). The<br \/>\ntexts of a Divi page are kept as segments with a translation memory in the free version (version<br \/>\n2.8.0 and later).<\/em><\/p>\n<p>A Divi site is more than its pages. The header and footer usually come from the <strong>Theme Builder<\/strong>,<br \/>\nand a promo box or a call to action that appears on many pages is often a <strong>global module<\/strong> kept in<br \/>\nthe <strong>Divi Library<\/strong>. Each of these is stored separately from the page that shows it, so each is<br \/>\ntranslated separately: translate the page, and its header, footer and global modules still need<br \/>\ntheir own translation.<\/p>\n<p>You translate all of them the way you build them &#8211; in the Divi <strong>Visual Builder<\/strong> &#8211; or, with PRO,<br \/>\nautomatically with AI.<\/p>\n<h2>Turning it on<\/h2>\n<ol>\n<li>Go to <strong>LATW Multilingual \u2192 Settings \u2192 Translation<\/strong>.<\/li>\n<li>Under <strong>Page builders<\/strong>, tick <strong>Divi<\/strong>.<\/li>\n<li>Under <strong>Content Types<\/strong>, tick what you want to translate besides pages and posts:\n<ul>\n<li><strong>Divi: Header Template<\/strong>, <strong>Divi: Body Template<\/strong> and <strong>Divi: Footer Template<\/strong> &#8211; the<br \/>\nlayouts of the Theme Builder;<\/li>\n<li><strong>Divi: Library (global modules and saved layouts)<\/strong> &#8211; the Divi Library, which is where global<br \/>\nmodules live.<\/li>\n<\/ul>\n<\/li>\n<li>Click <strong>Save changes<\/strong>.<\/li>\n<\/ol>\n<p>The Divi types appear only while the Divi theme is active.<\/p>\n<h2>Translating a page by hand<\/h2>\n<p>Go to <strong>LATW Multilingual \u2192 Posts<\/strong>, open the <strong>Pages<\/strong> tab, and click the pencil next to a language<br \/>\nin the <strong>Languages<\/strong> column. The page opens in the Divi Visual Builder, at its address in that<br \/>\nlanguage (for example <code>\/pl\/about\/<\/code>; with languages on subdomains or domains the visual builder opens on your main<br \/>\naddress and shows the page in that language), showing the original the first time and your translation every<br \/>\ntime after.<\/p>\n<p>Edit the texts in place, as you would when building the page, and click <strong>Save<\/strong>. The translation<br \/>\nis saved for that language only; the original page is not touched.<\/p>\n<p>You can also start from the page itself: open it in the translated language on the front end and<br \/>\nclick <strong>Enable Visual Builder<\/strong> in the admin bar. You are taken to the translation, not to the<br \/>\noriginal.<\/p>\n<p>A translation can also be styled differently from the original &#8211; a smaller font for a heading that<br \/>\nis longer in German, a different image for another market. Those changes stay in that language.<\/p>\n<p>The Visual Builder has no field for the page&#8217;s address. To give the translation its own URL slug,<br \/>\nopen the page&#8217;s segment editor (the list icon next to the language in the <strong>LATW Translations<\/strong><br \/>\nbox) and use the <strong>URL slug<\/strong> field at the top &#8211; see <em>Translating Elementor<\/em> for how it works.<\/p>\n<h2>Translating the header, footer and global modules<\/h2>\n<p>The Theme Builder layouts and the Divi Library have their own tabs on <strong>LATW Multilingual \u2192 Posts<\/strong>:<br \/>\n<strong>Header Templates<\/strong>, <strong>Body Templates<\/strong>, <strong>Footer Templates<\/strong> and <strong>Layouts<\/strong>. Translate them there,<br \/>\nwith the pencil next to a language, exactly like a page. The layout opens in the Visual Builder on<br \/>\nits own, without a page around it.<\/p>\n<p>Once saved, the translated header and footer are shown on every page of that language that uses<br \/>\nthem, and a translated global module appears on every page that contains it.<\/p>\n<p><strong>Why not straight from the page?<\/strong> When you translate a page, the Visual Builder still shows the<br \/>\nheader and footer around it &#8211; in the original language, because they are not part of that<br \/>\ntranslation. Changes made to them there are refused &#8211; Divi reports that the save failed &#8211; instead<br \/>\nof being saved over your original header. Translate them from their own tab.<\/p>\n<h2>Translating with AI<\/h2>\n<p><em>Requires <strong>PRO<\/strong>.<\/em><\/p>\n<p>Tick the pages or layouts on <strong>LATW Multilingual \u2192 Posts<\/strong> and click <strong>Translate Selected<\/strong>, or use<br \/>\nthe <strong>Translate<\/strong> button on a single row. The same works for the header, footer and Library tabs.<\/p>\n<p>Only the texts of each module are sent to the translation engine: headings, body text, button<br \/>\nlabels, image alt texts, testimonial names, form labels, drop-down options and similar. The layout,<br \/>\nthe design settings and the links never leave your site and cannot be damaged by the translation.<br \/>\nThe result is the same translation you would get by hand, so you can open it in the Visual Builder<br \/>\nafterwards and correct anything.<\/p>\n<p><strong>What it costs.<\/strong> Every translation is a request to your AI engine and is billed by it. A page is<br \/>\ncharged for the text of all of its modules. A global module is also stored as a copy inside every<br \/>\npage that uses it, so its text is translated with each of those pages as well as on its own in the<br \/>\n<strong>Layouts<\/strong> tab. The translation of the page&#8217;s copy is only shown if you ever unlink the module;<br \/>\nthe text you see comes from the translated Library item.<\/p>\n<p><strong>Translating again only translates what changed.<\/strong> The texts of a Divi page are segments, like the<br \/>\nparagraphs of any other page (see <em>Translation Memory and Segments<\/em>): a text that appears twice is<br \/>\ntranslated once, texts you corrected by hand are not replaced, and after you edit one module of the<br \/>\noriginal only that module&#8217;s text is translated again. If you add, remove or move modules in the<br \/>\noriginal, the translation follows the new layout.<\/p>\n<p>If you change the design of a module in a translation by hand &#8211; or add or remove a module there &#8211;<br \/>\nthat translation&#8217;s layout no longer matches the original. It is kept exactly as you made it and<br \/>\nis no longer updated automatically; click <strong>Rebuild from the original layout<\/strong> in the notice on the<br \/>\npage to go back.<\/p>\n<h2>What this does not do<\/h2>\n<ul>\n<li><strong>Divi 5<\/strong> is not supported. It stores pages in a different way; this page describes Divi 4.<\/li>\n<li><strong>Modules from third-party Divi add-ons<\/strong> are translated only if they use Divi&#8217;s own names for<br \/>\ntheir text settings. Texts in other settings stay in the original language when translated with<br \/>\nAI; you can still translate them by hand in the Visual Builder.<\/li>\n<li><strong>The Code module<\/strong> is never sent to AI. Its content stays as it is in every language unless you<br \/>\nchange it by hand.<\/li>\n<li><strong>Styles on translated pages are printed inside the page.<\/strong> Divi normally keeps a page&#8217;s styles in<br \/>\na cached file, one per page, shared by every language. Pages in a translated language print their<br \/>\nstyles inside the page instead (Divi&#8217;s own &#8220;Static CSS File Generation: off&#8221; mode), so a<br \/>\ntranslation with its own styling never changes the original, and the other way round. The<br \/>\noriginal language keeps using the cached file.<\/li>\n<\/ul>\n<h2>Troubleshooting<\/h2>\n<p><strong>The header or footer stays in the original language.<\/strong> Check that <strong>Divi: Header Template<\/strong> and<br \/>\n<strong>Divi: Footer Template<\/strong> are ticked under <strong>Content Types<\/strong>, and that the layout has a translation<br \/>\non its tab on the Posts screen.<\/p>\n<p><strong>A global module stays in the original language on every page.<\/strong> Translate it on the <strong>Layouts<\/strong><br \/>\ntab &#8211; the page&#8217;s own translation does not change it.<\/p>\n<p><strong>The pencil opens the block editor instead of the Visual Builder.<\/strong> <strong>Divi<\/strong> is not ticked under<br \/>\n<strong>Page builders<\/strong>.<\/p>\n<h2>Developer reference<\/h2>\n<ul>\n<li>Builder integration: <code>LATWM_Builder_Divi<\/code> (free plugin). Divi is a theme, so builder<br \/>\nintegrations that are not available on <code>plugins_loaded<\/code> register again on <code>after_setup_theme<\/code><br \/>\n(priority 100).<\/li>\n<li>The Visual Builder&#8217;s AJAX carries no Referer, so the session flags (<code>latwm_lang<\/code>, <code>latwm_post<\/code>)<br \/>\nare added to the URL of every <code>admin-ajax.php<\/code> request by an inline script on the builder page.<\/li>\n<li>Content: the translated page is the <code>post_content<\/code> overlay row. The builder loads it through<br \/>\n<code>et_fb_load_raw_post_content<\/code>; Theme Builder layouts are served through <code>et_builder_render_layout<\/code>.<\/li>\n<li>Filter <code>latwm_post_type_choices<\/code> (name =&gt; label) adds non-public types to <strong>Content Types<\/strong>.<\/li>\n<li>Segments: <code>includes\/segments\/divi-text.php<\/code> finds the module texts (attributes and module bodies)<br \/>\nand <code>LATWM_Builder_Segmenters::divi()<\/code> turns them into the segments of <code>post_content<\/code>.<br \/>\nFilters: <code>latwm_divi_text_attributes<\/code> (attribute names treated as text),<br \/>\n<code>latwm_divi_raw_content_modules<\/code> (modules whose content is never translated) and<br \/>\n<code>latwm_divi_module_prefixes<\/code> (shortcode prefixes of third-party modules, default <code>et_pb_<\/code>). With<br \/>\nPRO the older <code>latwmp_divi_text_attributes<\/code>, <code>latwmp_divi_raw_content_modules<\/code> and<br \/>\n<code>latwmp_divi_module_prefixes<\/code> keep working.<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>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\u2026<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_latwm_translated_slug":"","footnotes":""},"categories":[4],"tags":[],"class_list":["post-131","post","type-post","status-publish","format-standard","hentry","category-latw-multilingual"],"_links":{"self":[{"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/posts\/131","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/comments?post=131"}],"version-history":[{"count":2,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/posts\/131\/revisions"}],"predecessor-version":[{"id":191,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/posts\/131\/revisions\/191"}],"wp:attachment":[{"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/media?parent=131"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/categories?post=131"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/tags?post=131"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}