Problem: The client is unable to translate default sections of a paid theme using WPML, as these sections are not appearing in the string translation. Solution: 1. Navigate to WPML >> Translation Management. 2. Scroll down to the Other texts (Strings) section. 3. Click “Modify” and ensure the option “Untranslated strings that I encounter on the front-end while logged in” is selected, and click the “Save settings” button. 4. Visit the frontend page in the secondary language where this section appears. 5. Search for the required strings one by one, add translations, and use the search filters if needed.
This solution might be irrelevant if it's 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 this does not resolve your issue, please contact our support team for further assistance.
Problem: The client has completed translations for pages using the translation editor, and these are registered as completed in the Translations panel. However, the translations are not displaying on the frontend. The client recently switched from using Bakery builder to Elementor Pro and updated to the Hello Elementor child theme. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Edit the page in the default language. 2. Add "V2" to the title and update the page. 3. Delete the "V2" from the title and update the page again. 4. Update the page's translation. After completing these steps, please check if the translated page is now visible on the frontend.
This solution might be irrelevant if it's 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 the issue persists, please open a new support ticket at WPML support forum.
Problem: The client has created a custom post type named 'Galleries' for their website to transition galleries from an old theme to a new one while maintaining permalinks and structure. However, the '+' icon that allows for translation in WPML is not appearing for this new custom post type, although it appears for 'Pages' and 'Posts'.
Solution: If you're experiencing this issue, we recommend that you make your post type translatable in WPML. You can do this by navigating to WPML -> Settings -> Post Type Translations. For detailed instructions, please visit Translating Custom Posts.
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 issue persists, please open a new support ticket for further assistance.
Problem: The client reported an issue with the Croatian version of a WooCommerce product page showing an ERR_TOO_MANY_REDIRECTS error and having a URL with double slashes. Additionally, the featured image and attribute images were not displaying on the translated product page.
Solution: We advised the client to first take a full backup of their site and database. The steps included: 1) Checking in String Translation for the problematic URL and correcting it for the Croatian translation. We also suggested running the process to scan and auto-adjust links under WPML -> Settings -> Translate link targets. 2) Deactivating all plugins except for WPML, String Translation, WooCommerce, and WCML to check if the issue persists. 3) Switching to a standard theme like 2024 or 2021 to rule out theme-related issues. 4) Re-activating plugins one by one to identify any conflicts, and then switching back to the original theme to check for issues.
Alternatively, client found that plugin SEO press was causing the url to look like this, resetting the plugin fixed the issue.
If these steps do not resolve the issue or if the solution seems outdated or irrelevant, 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 at WPML support forum for further assistance.
Problem: The client installed the new Buddyboss Glue addon and encountered issues with managing translations of profile types. They observed duplicated entries. Solution: 1. Set profile types as not translatable in the new BPML version. Instead, use WPML > String Translation to manage these translations. 2. Delete any duplicated profile type entries.
For further details on managing translations, visit the WPML documentation: Translating Your Contents.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. Also, check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum: WPML Support Forum.
Problem: The client is experiencing issues with translating the checkout and cart pages on their WooCommerce site using Elementor and WPML. Specifically, the checkout page redirects to the cart page, and there are difficulties in translating labels and fields within the checkout form. Solution: 1. We recommend using the String Translation module as explained in the WPML documentation. You can find the guide here: String Translation documentation. 2. Ensure that the WCML setup is completed as per the instructions, which could help in managing the translations for the checkout and cart pages effectively. The setup guide is available here: WCML setup instructions. 3. If the issue persists, consider checking and adjusting the permalink settings to 'postname' for better SEO and functionality, which might resolve some redirection issues. 4. For translating links and ensuring they point to the correct language version, follow the guide on translating links here: How to translate links.
If these steps do not resolve your issue, or if the solution seems outdated or irrelevant to your specific case, please open a new support ticket. We highly recommend checking related known issues at 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, you can also contact our support team directly at WPML support forum.
Problem: You are trying to translate Ninja Forms date picker string. While in one language it works in another it doesn't Solution: The issue might be related to known problems with several themes and plugins not loading translations correctly in WPML. Specifically, you can refer to these errata pages for more details:
To resolve the issue with Ninja Forms, please follow these steps: 1. Ensure you make a full backup of your website. 2. Navigate to
wp-content/plugins/ninja-forms/ninja-forms.php
and locate line 779. 3. Change the following line of code:
unload_textdomain('ninja-forms');
to:
unload_textdomain('ninja-forms', true);
This modification has been tested and should help resolve the translation issues.
If this solution does not apply to your case, or if it seems outdated, 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. Should you need further assistance, please open a new support ticket.
Problem: The client reported that the English version of their WooCommerce shop page was displaying fewer products compared to the Bulgarian version, despite both versions being set to automatically translate. Solution: We discovered that the issue was related to the WooCommerce Wholesale Prices Premium plugin. We recommended deactivating and then reactivating the plugin, which resolved the problem. Additionally, we advised the client to check and publish any English products that were still in draft status.
Please note that this solution might be outdated or not applicable to your specific case. If the issue persists, 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 needed, please open a new support ticket at WPML support forum for further assistance.
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. Should you need further assistance, please open a new support ticket at WPML support forum.
Problem: The client is using Elementor and WooCommerce to display carousels with links to product attributes (brands) that are set to 'not translatable'. The links should link to the current language version, but WPML is altering them to the default language. The client wants these specific links to remain unchanged in the translated pages. Solution: We recommended adding a custom filter to the theme's functions.php file to prevent WPML from altering these specific links. Here is the code snippet to add:
This code will add the specified brand to a blacklist, preventing WPML from translating the URL. For more information on managing sticky links in WPML, visit WPML Sticky Links documentation.
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 issues persist, please open a new support ticket.
Problem: The client is trying to use WPML's Advanced Translation Editor and Automatic Translations for translating content from English to French, but not from English to Canadian English. They are concerned that the Advanced Translation Editor might automatically translate English (Canada), which is mapped to the default language of the site and should not be auto-translated according to WPML documentation. Solution: We advised the client to manually control the translation process to avoid automatic translation for English (Canada). This can be achieved by: 1. Activating the option in WPML -> Settings to control which content is sent for automatic translation. 2. Using the WPML -> Translation Management to filter content by the original language (English) and manually sending it for automatic translation in French. For English (Canada), since automatic translation is not supported due to its mapping to the default site language, it is not necessary to map it for automatic translation unless desired by the client.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, 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 further assistance is needed, please open a new support ticket.
Problem: You are using WPML with Tutor LMS PRO and have translated email messages using a string, but the email notifications are not being sent in the user's language; they are only sent in the language of the template. Solution: We recommend following these steps to ensure email notifications are sent in the user's language: 1. Navigate to WPML-> Theme and plugins localization, select your theme/plugin, and scan. 2. Go to WPML-> String Translation. 3. Scroll down and click on the "Translate texts in admin screens »" link. 4. Search for the needed strings. 5. Select the strings. 6. Click on the "Add to String Translation" button. 7. Then click on the "« Return to String Translation" link. 8. Translate the strings, clear the cache, and check the front end. For more detailed guidance, please refer to our guide on translating texts in the admin texts screen: https://wpml.org/documentation/getting-started-guide/string-translation/finding-strings-that-dont-appear-on-the-string-translation-page/
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 you still need assistance, please open a new support ticket at https://wpml.org/forums/forum/english-support/.
Problem: The client was unable to translate their website products to Arabic using WPML. Solution: We checked the site and discovered that the products were not set as translatable. We then made the products translatable and updated the product in the default language along with its translation. Finally, we created a printing option for the Arabic product. We recommend checking if the product is now correctly translated and functioning as expected.
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 trying to translate the message 'No products in the cart.' displayed in the mini cart top menu icon when the cart is empty. Although the string is translated in String Translation, it still appears in English on the live site.
Solution: We recommend checking if the issue persists when only WPML, String Translation, and Elementor are active, and all other plugins are deactivated. This step helps in identifying if any other plugin is causing a conflict that prevents the translation from displaying correctly. Before proceeding, ensure to back up your website and database completely. It's advisable to perform these checks on a staging or development site to avoid affecting the live site.
If after these steps the translation still does not appear, or if this solution seems outdated or not applicable to your case, please visit our support forum to open a new 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.
Problem: You have updated site content on multiple pages and now need to refresh or update the translations using WPML without having to click multiple times for each page. Solution: We recommend you navigate to WPML > Translation Management > Dashboard. Here, check for the pages that require an update and select them. At the bottom of the page, send these pages for automatic translation, ensuring you choose the option to only update the translation and not retranslate the entire content. For detailed guidance, please refer to our documentation on translating your contents. Note that this guide reflects the new UI of WPML 4.7, which you can update to by going to Plugins > Add new > Commercial and clicking "Check for updates".
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. Should you need further assistance, please do not hesitate to open a new support ticket at our support forum.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
