Problem: If you're experiencing issues with words being cut off in the Advanced Translation Editor (ATE) instead of being grouped into paragraphs, the issue might be related to how the original HTML code is structured. Solution: We recommend cleaning up the HTML code on your original page. For instance, if your original code includes multiple tags breaking up sentences, you should consolidate these into fewer tags or use
tags to ensure content is grouped correctly. Here's an example of how you might adjust the HTML:
<div><p style="font-size: 18px;">Chaque expérience est construite sur base de recherches et de rencontres avec des <strong>acteurs locaux et des experts</strong> sur le(s) sujet(s) afin d'offrir une expérience <strong>" sur mesure "</strong>, ancrée dans la <strong>réalité du terrain</strong>. Le client/partenaire et/ou ses représentant·e·s sont partie prenante dans la <strong>co-construction</strong> et participent en tant que spectateurs (complices). L'approche et le scénario peuvent être <strong>adaptés à différents thèmes, secteurs, publics et environnements</strong>.</p></div>
This adjustment should help ensure that the content appears correctly in ATE.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. We highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket.
Problem: The client is trying to translate the header and footer of a Divi theme using WPML, but despite translating the content, the header and footer still display in the original language (English). Solution: We recommend the following steps to ensure the header and footer are translated correctly: 1. Navigate to WPML → Settings → Post Type Translations and verify that the header and footer are set to be translatable. 2. Go to WPML → Translation Management, select the header and footer, and send them for translation. 3. Finally, translate the header and footer under WPML → Translations. It's important to note that translating content directly from string translations will not effectively translate the Divi header/footer.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client was unable to see the translated Divi footer in Dutch and English on their website, despite translating it via WPML's String Translation. The footer remained in French, and the content appeared empty under WPML → Translation Management. Solution: We advised the client to increase the WP_MEMORY_LIMIT to at least 256M, as the initial setting was too low (40M). Instructions for increasing this limit can be found here: https://wpml.org/faq/checklist-before-opening-a-ticket-in-wpml-support/#how-to-increase-your-sites-memory-limit. Additionally, we located the specific footer template and directed the client to use the translation editor accessible via the plus sign in the WPML Translation Management dashboard. This allowed the client to manually translate the footer into Dutch and English.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we recommend opening a new support ticket. We also highly suggest checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum at https://wpml.org/forums/forum/english-support/.
