Problem: If you're experiencing issues with ATE where it opens but gets stuck loading, and eventually displays an 'Execution Expired' error, this might be due to specific translation units containing large sections of encoded data. This problem was identified when the ATE failed to load the homepage, despite other pages working correctly. Solution: We recommend checking any content-heavy sections on your page for encoded data. For instance, if you have custom CSS in blocks like sliders where images are embedded directly as encoded (base64) data, update this to use a standard image URL from your Media Library. This change should reduce the size of the translation unit, allowing the page to be sent to ATE without issues. After making these adjustments, please attempt to send the page to translation again.
If this solution does not resolve your issue or seems outdated, we highly recommend checking related 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 open a new support ticket.
Problem: If you're experiencing issues where Divi-specific UI elements (e.g., backend menu items and labels in the Visual Builder) are displayed in English instead of German, despite both user language and site language being set to German, and the Divi .mo files being present, the issue might be related to how Divi translations are loaded with WPML enabled. Solution: We recommend checking the following settings in your WordPress User Profile: 1. Ensure your User Language is set to German (de_DE). 2. Disable the checkbox that sets the admin language as the editing language. If these settings are correct and the issue persists, it might be necessary to rescan the Divi theme to ensure all translatable strings are correctly detected and registered. This can be done under WPML's theme and plugin localization settings.
Please note that this solution might be irrelevant if it's 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 continues, please open a new support ticket at WPML support forum.
If you're experiencing issues with translations not displaying correctly on the frontend when they include Unicode characters like the '📷' (U+1F4F7) camera icon, and the translation only shows the source language text with the icon, this might be due to database collation settings.
Solution:
We recommend updating the collation of your database tables and their columns to
utf8mb4_unicode_520_ci
. After updating, modify and save the page in the original language and update the translation. This should allow the correct display of Unicode characters in translations. If you encounter styling issues in translated text blocks post-update, try the following steps:
1. Open the original language page for editing. 2. Make a small change (like adding a space or a word) and save it. 3. Update the translation. 4. Clear all caches and check if the styling issue persists.
If these steps do not resolve your issue or if the solution 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 problems persist, please open a new support ticket.
Problem: The client is working on a site under development and needs to ensure compatibility with WPML. They are concerned about the compatibility of WPML with the 'Secure Custom Fields' plugin and whether to manually install the Advanced Custom Fields version 6.3.9 provided by WPEngine. Solution: We confirm that WPML is compatible with both the 'Secure Custom Fields' and the Advanced Custom Fields version 6.3.9. You are free to choose either of these plugins for your website as both are compatible with WPML. If you have any further questions or need more specific advice, 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 this solution does not apply to your case, or if it seems outdated, please do not hesitate to open a new support ticket at our support forum.
Problem: You are trying to translate content generated by the 'Divi Modules Table Maker' plugin using WPML. Previously, you used an XML config to enable translation, which worked on an older site but has stopped functioning on a new site and a dev/testing environment. The content includes line breaks that are not being preserved in translation. Solution: This issue appears to be related to a known problem where line breaks are ignored when using the Advanced Translation Editor. Here’s what we recommend you try: - Look at the top right corner of the Translation Editor. - Click on the gear icon. - Disable the option 'I prefer larger segments'. - Close the editor and resend the page for translation via WPML > Translation Management.
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. Additionally, if you need further assistance, please open a new support ticket at WPML support forum.
