Problem: The client was experiencing issues with images not appearing in the Advanced Translation Editor (ATE) for translation and Glossary terms not applying correctly when using WPML with Divi 5, which is still in beta. The images were not loading in ATE, and the first 9 of 12 Glossary words were not visible or editable in the translation panel.
Solution: 1. We acknowledged that Divi 5 is still in beta and not all widgets are fully compatible with WPML, including some issues with translating images used as section, row, or column backgrounds. We recommended adding images directly in Divi in the second language as a workaround. 2. For the Glossary issue, it was suggested that there might be a conflict with another plugin or the theme. We advised purging all site caches and testing the site with a minimal setup by deactivating unrelated plugins and switching to a default theme like Twenty Twenty-One to check if the issue persists. 3. If the problem was resolved by the minimal setup, we recommended reactivating plugins individually to identify the problematic one. 4. We provided assistance in setting up a staging site using the WP Staging plugin (https://wordpress.org/plugins/wp-staging/) for further troubleshooting without affecting the live site. 5. We adjusted configurations and assigned content for translation to check if images appeared correctly in ATE on the staging site. 6. We shared a guide on how to handle different images per language (https://wpml.org/documentation/getting-started-guide/media-translation/). 7. We provided a file to import Glossary terms to resolve related issues.
If this solution does not resolve your issue or seems outdated, 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/.
Problem: If you're trying to translate your site using WPML using the Divi 5 alpha version and find that certain sections on each page do not get translated despite multiple attempts through the advanced editor, it might be due to compatibility issues with the Divi builder, particularly if you are using an alpha version of Divi which is not yet supported.
Solution: This issue until now only occurs when using the Divi 5 alpha version. We recommend adding a custom XML configuration to your WPML settings. Navigate to WPML > Settings > Custom XML Config and paste the provided XML markup. After adding the XML, make a minor edit to the original page, save it, and then open the WPML Translation Editor. This should allow most of the page builder's modules to be translated. However, be aware that modules like Blurb, Contact form, Contact Fields, Post Nav, and Button may still face issues as they do not include a background option anymore. Our compatilbity team will begin working on the Divi 5 integration once the beat for this theme is available.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, please check the related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket for further assistance at WPML support forum.
