Problem: If you're experiencing a white page on every sub-page including the home page after migrating from Divi 4 to Divi 5 with WPML active, this might be due to a known issue. During the migration, WPML's Gutenberg cleanup routine might interfere with Divi's conversion process, leading to the removal of necessary markup and resulting in white pages. Solution: We are currently aware of this issue and our developers are working on a fix. In the meantime, temporarily disabling WPML during the Divi migration process might prevent this problem. Once the migration is complete, you can re-enable WPML. We recommend checking for updates regularly and applying them to ensure compatibility.
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 issue persists, please open a new support ticket at WPML support forum for further assistance.
Problem: After migrating a website from one server to another, the layout is damaged, and a PHP fatal error related to the WPML plugin occurs. The error message indicates an issue with
DOMDocument::loadHTML()
being called with an empty argument. Solution: 1. Manually upload fresh copies of the WPML plugins from your account at https://wpml.org/account/downloads/. 2. Temporarily disable all plugins except for the WPML plugin to check if the issue still occurs. 3. If the problem persists, provide temporary access (wp-admin and FTP) to a staging or test site where the problem can be replicated. Include exact steps to replicate the issue for more efficient investigation.
If this solution does not resolve your issue or seems outdated, we 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 necessary, please open a new support ticket at WPML support forum for further assistance.
3) Make a small change in the default language page and then open the translated page in WPML's Translation Editor. The table title should now be available for translation.
4) Add the translation as needed, and it should work correctly.
If this solution does not resolve your issue or seems irrelevant due to being 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 issues persist, please open a new support ticket for further assistance.
Problem: The client created a custom code block inside the Divi Builder for WooCommerce product templates and translated the text using WPML's String Translation. However, the translations were not visible on the product pages when switching to English. Solution: 1. We recommended that the client create a shortcode to handle the custom code block. This involves adding the following code to the functions.php file of their theme:
2. Replace the custom code module with a text module in Divi and use the shortcode
[product_feature_box]
. 3. Go to WPML's String Translation and search for the texts of the code to find them for translation, or use the Domain select box and select the "your-text-domain" domain item to show all the text for translation in one place.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If you're still experiencing issues, we highly recommend checking the related 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.
