Problem: You are working on a staging site with the new Divi 5 theme. The page managed through Divi > Theme Builder does not appear in the Pages section. When you open the page from WPML, you only see some elements, but not the main content that is present in the Theme Builder. Solution: We recommend trying to translate the template from WPML → Translation Dashboard. If you cannot see all the elements, it might be due to an issue related to Divi 5 and WPML compatibility while new features are being released. You can check this issue here: Divi 5 WPML Compatibility Issue.
If this solution does not apply to your case, or if it seems outdated, 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.
Problem: After upgrading from Divi 4 to Divi 5, the client is experiencing multiple issues on their site, including changes in page layouts and background colors, and some pages not displaying at all. Solution: We recommended the client to check if the issue persists with WPML deactivated to determine if it's a WPML-related issue or a problem with Divi itself. We advised editing the affected pages to check if the layout settings such as 'Fullwidth' have been altered. Additionally, we highlighted an ongoing compatibility issue between Divi 5 and WPML, as Divi 5 is still in its alpha phase and undergoing updates. We provided a link to our errata page for more details and possible workarounds: https://wpml.org/errata/divi-5-wpml-compatibility-while-new-features-are-being-released/
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. If further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are using the 'Twenty Twenty-four' block theme on your WordPress site and are unable to include the language selector in the top main menu or change menu items for translated pages, as the Appearance > Menus link is unavailable due to the block editor theme. Solution: 1. The Appearance > Menus section is not available with Block Themes, and the settings under WPML > Languages > Menu language switcher do not work with these themes. Instead, use the WPML Language Switcher Block, which can be placed in the header or footer templates. 2. To translate Block Theme Templates, Template Parts, and Navigation Menus, navigate to WPML > Translation Dashboard, create a translation job for each content, assign the jobs to yourself, and then access them at WPML > Translations to complete the translations using the WPML Translation Editor. If these steps did not resolve your issue, it might be helpful to send us the WPML troubleshooting information. More information can be found here: https://wpml.org/de/faq/provide-debug-information-faster-support/
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.
Problem: The client translated all product attribute terms into every language using WPML but found that the term thumbnail images did not automatically display for all translated terms.
Solution: 1. Identify the custom field name used for term thumbnails. This can vary depending on the theme or plugins used. 2. Set the translation preference for this custom field in WPML to 'Copy'. This ensures that the thumbnail images display correctly across all languages. 3. If the field is set to 'Don't translate', change it to 'Copy' in WPML -> Settings -> Custom Term Meta Translation, then save the changes. 4. Update the translation of the term to reflect these changes.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, we recommend opening a new support ticket. Additionally, 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. For further assistance, please visit our support forum at WPML Support Forum.
Problem: You are trying to use the 'Preview' feature for a page or post to see the latest updates, but the preview shows old content instead of reflecting the most recent changes. Solution: We recommend trying the workaround described in the following link: Large Amount of Revisions Can Affect the Last Change Being Displayed. Please ensure to back up your database before making any changes. Additionally, defining a constant in your site's configuration can help limit the number of revisions, which might prevent this issue in the future.
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 needed, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is facing an issue where a checkbox is not appearing at checkout in Greek on their WooCommerce site, although it appears in English. Solution: We have identified that the issue is not caused by WPML. The problem arises because WooCommerce blocks rely on JavaScript translation files (.json files), which are not fully supported by WPML String Translation. Consequently, the site loads the native WooCommerce translations. In this case, the Greek translation for that string is incomplete. To address this, you can contribute to completing the translation at WordPress translation project.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also highly recommend checking related known issues at WPML Known Issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins.
Problem: You are experiencing a PHP Fatal error on your website when using the WPML plugin's language switcher, specifically when switching back to the Dutch version from a category page. Despite increasing the zend.max_allowed_stack_size, the issue persists. Solution: We recommend the following steps to address the issue: 1. Save and remove the existing debug.log file from your server if it's too large, as it can affect performance. 2. Temporarily deactivate all plugins except for WPML and WPML String Translation to check if the issue still occurs. 3. Attempt to reproduce the error by switching between languages multiple times. If the error does not reoccur, it might have been caused by a conflict with another plugin. 4. If the issue persists, please provide specific steps or conditions under which the error occurs to help us further diagnose the problem.
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 further assistance is needed, please open a new support ticket at WPML support forum.
