Problem: The client is using the Divi Builder to create a template for a custom post type called "chapters". Although they have translated the headers (Source, Language, Download) using String Translation, the dynamic content pulled by the Pods plugin and the headers are not being translated or displayed correctly in other languages. Solution: 1. We set the Lang field to be translated and instructed the client to update the chapter in the default language. This allows the Lang field to be visible and translatable when updating translations. 2. For translating links, we advised using the search field to find and translate them alongside the chapters. 3. To address untranslated labels on the front end, we recommended translating the body templates. The client should visit the templates page and ensure all templates are translated.
If this solution does not resolve your issue, or if it seems outdated, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket at WPML support forum.
Problem: You are experiencing issues with WPML not recognizing content built or modified in Divi. Changes made to the original language pages in Divi, such as adding a breadcrumbs module, are not reflected in the translations, resulting in a broken layout on the translated pages. Solution: We discovered that there were custom CSS applied to your page that were not compatible with WPML. We recommend removing these custom CSS and retranslating the page to fix the issue. This should help in correctly reflecting the changes made in the original language across the translated versions.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your current situation, 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 problems persist, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client was unable to make WPML recognize Divi Builder's custom fields in the backend, despite them being visible on the frontend. The custom fields were not appearing as translatable, and the layout was not updating correctly. Solution: We resolved the issue by fixing specific data in the client's database, which allowed the Divi content to be recognized by WPML. To ensure that the texts are registered correctly, we recommended that the client update the original pages on Divi by making a small edit to a text and saving it. This action should help in syncing the translations properly.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is unable to see the updated footer in the German and French versions of their website. The footer, which is a global Divi element, displays an outdated version with a light background instead of the new dark background version that appears on the English page. Solution: If you're experiencing issues with global Divi elements not updating on translated pages, we recommend translating these elements from the WPML > Translation Dashboard. Here's how you can do it: 1. Navigate to WPML > Translation Dashboard. 2. Select the global elements such as the footer and send them to translation. 3. Choose "Translate myself" and then proceed to WPML > Translations to complete the translations. This approach should ensure that all global elements display correctly in all languages.
Please note that this solution might be outdated or not applicable 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 the problem persists, please open a new support ticket at WPML support forum for further assistance.
