Problem: The client is experiencing issues with translating a sidebar widget on his page using WPML. The translations are not visible on the page despite being found in WPML. Solution: We have identified that the 'Industroz' theme is not listed on the WPML compatibility list for themes, which suggests a potential compatibility issue. We recommend reaching out to the theme authors and encouraging them to join our Go Global program so we can collaborate to ensure full compatibility with WPML. As a workaround, we suggest creating a separate widget for each language. This method has been tested and confirmed to work.
If this solution does not apply or is outdated, or if further assistance is needed, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that the latest versions of themes and plugins are installed. If the issue persists, please do not hesitate to open a new support ticket with us.
Problem:
The placeholder text of WPForms address fields can't be found in the translation editor or string translation.
Solution:
Please make sure to have a full backup of your site then follow these steps:
1. Open …/wp-content/plugins/wpml-wpforms/wpml-forms-config.xml file.
2. Look for line 57
3. Replace the following line:
Problem: The client was unable to display shipping costs and provide shipping options to other countries on their multilingual sites. Solution: We asked the client to provide more details about their configuration with the Flexible Shipping plugin and to describe the results they were experiencing. We requested screenshots to better understand the issue. We also pointed out that there are known issues with the Flexible Shipping plugin, which can be found at https://wpml.org/errata/flexible-shipping-pro-shipping-methods-do-not-appear-on-translated-cart/.
We then provided a step-by-step guide: 1. Navigate to the Flexible Shipping PRO shipping settings. 2. Add the shipping rule. 3. Use the language switcher at the top of the admin area to switch to the desired language. 4. Add the shipping rule for the selected language.
We informed the client that this information should help resolve their issue and offered further assistance if needed.
Please note that the solution provided might be outdated or not applicable to your specific case. If the issue persists, we highly recommend checking the 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 help, please do not hesitate to open a new support ticket with us at our support forum.
Problem: The client is trying to create a bilingual homepage with Divi and WPML but encounters an issue where the 'Translations queue' shows 'No Data' after attempting to add a translation for the homepage. The client also wants to have an English page 'Home' and a corresponding French page with a different design.
Solution: 1. Ensure that the client's user account is added as a translator with the correct language pairs (English to French and French to English) in WPML > Translation Management > Translators tab. For more information, check the guide on how to set up local translators and language pairs. 2. If the client intends to create a different design for the second language and not just translate content, they should follow the guide on how to use manual translation to translate the page manually.
Please note that the solution provided might be irrelevant if it's outdated or not applicable to your case. If the issue persists, 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 you still need assistance, please don't hesitate to open a new support ticket. For further assistance, you can reach out to us on the WPML support forum.
Problem: The client is trying to build a French version of a page. The Portuguese version works, but the French version does not. Additionally, the French menu is missing an item that appears in other languages.
Solution: 1. We recommend disabling the cache for logged-in users in WP Rocket settings to see changes immediately. 2. The French page was found in the trash and set as a draft. We advised the client to manually restore it and publish it. 3. We suggested making a small change to the default page title and saving it. 4. The client should re-translate the French page and ensure it is 100% translated before saving. 5. To address the menu issue, we advised translating the page into all the correct languages by clicking the plus icon from Pages > All. 6. For translating the menu, the client can either do it manually and add items as desired or use the menu sync tool to have the same menu with translated items. We provided a link to the related documentation: Translating Menus documentation. 7. We provided a direct link to the French menu for convenience.
If the solution provided here is not relevant 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 you still need assistance, please open a new support ticket at WPML support forum.
Problem: There is an issue with the String Translation table on the client's site, which could potentially become a critical problem in the future. Solution: We recommend that the client activates WPML on their site, navigates to WPML-> Languages, and checks if the languages are selected correctly. If the languages are not correctly set, the client should select the appropriate language. This action may resolve the issue.
Please note that this solution might not be relevant if it's outdated or not applicable to your case. If the problem persists, we encourage you to open a new support ticket. We also 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 contact us in the WPML support forum.
Problem: The client was experiencing issues with Yoast Breadcrumbs not displaying the '/blog' path in the breadcrumbs on the Hestia Pro theme, even after disabling all plugins and resaving Yoast and Reading settings. Solution: We checked the blog page and noticed it was missing a title. We added a title to the blog page. We then asked the client to verify if the 'blog' string appeared correctly in the breadcrumbs.
If you're experiencing a similar issue with Yoast Breadcrumbs not showing the correct path, we recommend you: 1. Ensure that your blog page has a title set. 2. Check the breadcrumbs after adding the title to confirm if the issue is resolved.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the problem 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 you still need assistance, please open a new support ticket.
Problem: The client reported an issue where WooCommerce Subscriptions was not working correctly with WPML. The site's default language is English, but when attempting to edit a subscription, the backend would open in the user's language and display a blank page. Solution: 1. We asked the client to provide the error log. 2. After reviewing the log, we identified that the error originated from WooCommerce, specifically at
. 3. We advised the client to deactivate WPML plugins to check if the issue persists. 4. We then suggested that the client contact the WooCommerce support team and share the error log with them for further assistance.
Please note that the solution provided might be irrelevant due to being outdated or not applicable to your case. If the issue persists, 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 necessary, do not hesitate to open a new support ticket with us for further assistance.
Problem:
The client needed help translating a custom template in the WPML plugin and it was unclear if they were referring to a page template or a theme.
Solution:
If you are experiencing difficulties translating a custom template or theme in WPML, we recommend that you follow these steps:
1. Use the following custom searches we've created for you to find existing tickets with solutions recommended by our colleagues:
We hope this information is useful to you and saves you some time. Please let us know how it goes and if it has helped you.
If this isn't enough, try giving us a little more context and details about the exact situation on your site and what you're trying to do.
The solution provided may not be relevant to your case, either because it is outdated or simply does not apply to your situation. If that is the case, we recommend that you open a new support ticket. We also suggest that you review the related known issues, check the version of the permanent fix, and confirm that you have installed the latest versions of the themes and plugins.
Problem: The client is trying to translate strings using the WPML plugin, but some strings, particularly in the French language, are not displaying their translations. These strings are from the WPL PRO plugin used on the client's website.
Solution: We discovered a compatibility issue between the client's theme and WPML. Specifically, the problem lies within the
wpl_global::load_textdomain()
function of the Real Estate Listing plugin by Realtyna, which incorrectly unsets the MO file, leading to translations not being displayed. To resolve this, we recommend the following steps:
1. Ensure you make a backup of your website. 2. Edit the file
public static function load_textdomain($domain, $mofile)<br />{<br /> return load_textdomain($domain, $mofile);<br />}
After making these changes, check if the translations are now displaying correctly.
Please note that this solution might be outdated or not applicable to your case. If the issue persists, 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 you still need assistance, please open a new support ticket with us.
Problem: The client was trying to translate a post to other languages but encountered issues with specific posts not updating correctly in the database.
Solution: We resolved the issue by performing the following steps: 1. We used the WPML troubleshooting options as outlined in WPML Troubleshooting Options. 2. We cleared all caches. 3. We searched for the specific post IDs in the 'Delivery postcodes' post type and clicked '+' to add the translation. 4. We repeated the process for each affected post ID.
This process updated the existing translations without consuming additional translation credits.
Please note that this solution might not apply to your case if it's outdated or not relevant to your specific issue. 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 the problem persists, please open a new support ticket with us.
Problem: The client reported an issue where activating WPML Multilingual CMS resulted in a loss of functionality from the Dokan plugin, specifically affecting the ability for customers to add products to the marketplace.
Solution: We found that the site's default language was English, but the Dashboard Page was initially set up in Arabic and then translated into English. This discrepancy in the source language of the page might have led to the issue. We resolved the problem by deleting the original Dashboard page and recreating it via "Dokan > Tools > Create Page," which correctly applied the styling to the Dashboard page across all languages. We asked the client to check the Dashboard page and report back if further assistance was needed.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If you're experiencing a similar issue and the provided solution does not help, 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 the issue persists, please open a new support ticket with us.
Problem: Client experienced missing entries in the WPML admin menu and are unable to find the 'Languages' option necessary for setup.r/>Solution: We recommend disabling all plugins temporarily to see if this allows the WPML setup wizard to continue. Once the conflicting plugins are disabled, you should be able to complete the WPML setup wizard and configure your language options. After the setup is complete, you can then re-enable your plugins one by one to identify the one causing the conflict.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, we suggest opening a new support ticket. We also 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 further assistance is needed, please contact us in the WPML support forum.
Problem: The client is unable to start automatic translation from the dashboard and can only translate pages and taxonomies individually. They attempted to change the translation mode to automatic in the settings without success.
Solution: We reviewed the client's site and found that there were no items marked as "Not Translated", "Needs Update", or "In Progress", except for 78 translations awaiting review. Additionally, there were 10 items in the Translation Basket, presumably sent for manual translation. We advised the client to: 1. Review the translations that are awaiting review. 2. Remove the items from the Translation Basket. 3. Check for any pending content that they wish to translate automatically. We also clarified that automatic translation works by default in the following scenarios: - New content. - Changes to existing content. - Re-translation of existing content by selecting it from WPML -> Translation Management and choosing "Translate automatically". If there are no changes in the content, there will be nothing to translate. We suggested that the client test this by changing some content in the site's default language or adding a new page/post. Upon further inspection, we noticed that the translation mode was set to manual in WPML -> Settings. To resolve this, the client can send content for automatic translation through WPML -> Translation Management, as detailed in the sending content for automatic translation documentation. We also noted that the products had been translated and were awaiting the client's review.
Please note that the solution provided might be irrelevant if it is outdated or not applicable to your case. If the issue persists, 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 you still need assistance, please open a new support ticket.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
