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.
Problem: The client is experiencing issues when trying to translate English pages into Arabic on their website. Specifically, when clicking the plus button to add translations, some pages appear as new instead of translations. Solution:
Client fount that the translator for those pages was set to use WordPress Editor instead of WPML, so changing it back to WPML editor fixed the issue.
If these steps do not resolve the issue, the 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 problems persist, please open a new support ticket at WPML support forum.
Problem: The client created a Gravity Form using the Gravity Forms Survey Add-On plugin and encountered an issue where the form sends all data correctly in English via email, but not in Arabic. When the form is submitted in Arabic, the data is not being sent in the emails.
Solution: We first verified that the issue was not related to email content being different between languages by using the "Log Emails" plugin. Both English and Arabic emails had the same content, and form entries were created correctly in both languages. We then identified that the Gravity Form had not been translated, and the notification emails were missing the
{all_fields}
tag. To resolve this: 1. We translated the Gravity Form and added the
{all_fields}
tag to the existing notifications. 2. We added another notification with the
{all_fields}
tag for testing. 3. We created a new test page, added the form, and translated this page as well. After these adjustments, the form submitted correctly in both languages, and the received emails contained all the information in the respective languages. However, there was a note that the HTML formatted email had a design problem, which is not related to WPML but may affect how content is displayed.
If this solution does not resolve your issue or seems outdated, we 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 problems persist, please open a new support ticket.
Problem: You need to change the footer content of your DIVI theme and cannot find the footer template in the translation management page after modifying the default English content. Solution: If you're experiencing this issue, we recommend checking the specific post types for your DIVI theme's footer, header, and body layouts directly in your WordPress admin area. You can access these areas using the following links:
Please visit the following URLs and check if you can translate the templates.
Footer: yourdomain/wp-admin/edit.php?post_type=et_footer_layout
Header: yourdomain/wp-admin/edit.php?post_type=et_header_layout
Body: yourdomain/wp-admin/edit.php?post_type=et_body_layout
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 open a new support ticket with us for further assistance.
Problem: The client reported a delay in the automatic translation updates for their product descriptions. The English version of the product description was not updated even after seven days since the original content was updated. Solution: 1. We identified that the translation might have gotten stuck. We made changes to the page title and retranslated the page, which resolved the issue. 2. We suggested checking for any plugin conflicts or server-related issues that might be causing the delay. 3. We recommended updating all WPML plugins to the latest version after ensuring a backup is in place. This can be done by navigating to WP > Plugins > Add New > Commercial Tab, selecting the WPML plugins, and updating them. 4. We provided steps to manually resync the translations: - Edit the primary language page and click on update. - Allow the system to resync the English translation and show a review translation option. - Review the English translations and click "Accept Translations". - Now, editing the English language page should be possible.
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 the problem persists, please open a new support ticket at WPML support forum.
Problem: You are trying to make the 'Links to translation of posts' text appear in Japanese on the English page of your site, but it currently only displays in English. Solution: 1) We recommend you go to WPML-> String Translation and search for this string to translate it into Japanese. 2) Please share your Debug information with us to better understand your site's configuration. You can find a detailed explanation on how to provide this information here.
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 here.
Problem: The client is experiencing issues with maintaining the page theme and formatting when translating pages from Spanish to English using the WPML Translation Editor. Specifically, elements like video embeds and text styles are not being correctly translated or displayed. Solution: The client was using an ACF text area field to embed a video into the content. The problem with this approach is, that HTML markup by default will not display on the Advanced Translation Editor, and sending the markup in this way made the field not translatable, as it included unsupported HTML tags. Consider using the ACF oEmbed field for embedding videos to simplify the process and ensure compatibility across translations. More information on this can be found at ACF oEmbed Documentation. Avoid including style markup directly in the content. Instead, add it to the PHP template, within your ACF Block, a stylesheet in your theme, or through WordPress's custom CSS options at Appearance > Customize > Additional CSS.
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 WPML 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: The client is unable to switch from the Dutch version to the French version on the homepage of their multilingual site using the WPML language switcher. The switcher works on other pages but not on the Dutch homepage. Solution: We recommend trying the following steps to identify and resolve the issue: 1. Deactivate all plugins except for WPML CMS. 2. Temporarily switch to a default WordPress theme, such as Twenty Twenty-One. 3. Check if the language switcher issue on the homepage is resolved. Please ensure to back up your database before performing these steps. The issue was caused by the cache in the "Object Cache Pro" plugin.
If this solution does not resolve your issue or seems outdated, please visit our known issues page and check for any related issues. Also, verify that you have the latest versions of themes and plugins installed. If the problem persists, we highly recommend opening a new support ticket with us for further assistance.
Problem: You are experiencing an issue where too many fields appear in the WPML Advanced Translator Editor after applying a solution from the forum. You want to manage which fields to translate and which to leave untranslated using a custom XML configuration. Solution: To address the issue of excessive fields in the WPML Advanced Translator Editor, follow these steps: 1. Navigate to Kadence -> Forms. 2. Create and translate a contact form. 3. Edit the Contact page in the default language. 4. Select the contact form and update the page. 5. Update the translation of the Contact page. 6. Check the changes on the front end.
If this solution does not apply to your case, or if it seems outdated, 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: The client was unable to find the 'Clear language information and repopulate languages' option on the WPML troubleshooting page and was experiencing issues with product translations not functioning correctly. Solution: We suggested that the 'Clear language information and repopulate languages' option should appear at the top of the troubleshooting page if WPML detects that the default data in the languages table has been altered or is missing. If the option is not visible, we recommended manually recreating the languages table by connecting to the database and running the following MySQL query:https://wpml.org/forums/topic/clear-language-information-and-repopulate-languages-cant-find/#post-16721505 This query drops the existing languages table if it exists, creates a new one, and populates it with default language data. If further assistance is needed, we advised the client to contact us.
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 for personalized assistance.
Problem: The client requested a refund due to dissatisfaction with WPML, stating it was not functioning as intended. Solution: If you're experiencing dissatisfaction with WPML and are considering a refund, we recommend visiting https://wpml.org/purchase/refunds/. Refunds are processed automatically and can be requested through your user account if you are within the 30-day refund period. Additionally, we would appreciate understanding more about the issues you faced with WPML to help improve our service.
If this solution is outdated or not applicable to your case, please check the 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. If issues persist, we highly recommend opening a new support ticket at WPML 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