Problem: You are working on a Russian translation for a website using WPML and have encountered an issue where all string translations for Divi footer widgets do not work, except for one. You have tried translating strings that you previously added from "Translate texts in admin screens" but most translations are not effective. Solution: We recommend using the method of "Creating Widgets in Each Language" to ensure all your footer widget strings are translated effectively. This approach involves setting up separate widgets for each language. You can find detailed instructions on how to implement this method on our documentation page: Translating Widgets.
If this solution does not resolve your issue or 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 further assistance is needed, please do not hesitate to open a new support ticket at WPML support forum.
Problem: After updating WordPress and WPML, texts including standard paragraph blocks are missing on the translation page for patterns. Solution: We identified that the Arabic pattern was broken after the update. We have fixed the issue. Please verify if the texts are now appearing correctly on your translation page.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we recommend opening a new support ticket. We also 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 have installed a plugin to translate your German website into English, but the product category is missing on the English translation page. Solution: We recommend checking the English language portfolios to see if the custom field "id_field" exists. This issue might be due to the "Order By" custom field condition not working correctly on the English language page. If the field is missing, adding it should resolve the problem.
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.
Problem: The client is experiencing issues with a 3rd party plugin widget not translating correctly. Specifically, the titles on product filters and the 'Search Products...' placeholder are not appearing in the correct language. Additionally, the client mentioned that posts set to publish when the original is published are being published prematurely. Solution: For the translation issues with the widget, we recommend duplicating the category filter and assigning the appropriate language to each duplicate. This method should help ensure that the widget displays correctly in each language. For the issue of posts being published prematurely, ensure that the 'Publish the translated post when the original is also published' option is correctly configured to match your scheduling needs.
If these solutions do not resolve your issues or if they seem 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. Should further assistance be needed, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is trying to translate customized fields using WPML but encounters an issue where the translations do not appear on the frontend. The client used a custom hook and registered labels to WPML, translating them successfully. However, despite following documentation and using code examples, the translations are not visible on the frontend. Solution: 1. Ensure the text domain is correct. According to WordPress documentation, the text domain must use dashes, be lowercase, and have no spaces. 2. When using variables in translated strings, use the
printf()
function instead of echoing the variable directly. For example, change:
<p id="popup-title"><?= $popuptitle ?></p>
to:
<p id="popup-title"><?php echo __('Subscribe Now, Save 10%', 'storefront') ?></p>
After making these changes, re-scan the strings in the child theme, translate the string, and check if the translation displays on the frontend. 3. If using a custom text domain like "popup", register it with the following function in your theme's
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.
Problem: You are experiencing an issue where WPML is not translating the WPBakery Page Builder templates correctly, and the translations are not appearing on the live website despite following the documentation at https://wpml.org/documentation/plugins-compatibility/how-to-build-multilingual-sites-with-wpbakery-page-builder-and-wpml/. Solution: 1. Ensure that you are using the WPML Translation Editor to translate your content. Post types such as pages, posts, and page builder content cannot be translated directly at WPML > String Translation. 2. Go to WPML > Settings > Post Type Translation and set the WPBakery Templates to "Translatable - only show translated items". 3. Translate the templates using the WPML Translation Editor, similar to how you would translate pages and posts. 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, you can open a new support ticket for further assistance at WPML support forum.
