Issue: If you are setting up a multilingual website on a subdomain and plan to move it to a main domain later, and you are concerned about the permalink structure when using WPML with directories in different languages. Solution: We can confirm that you can configure WPML on the subdomain without problems. For the default language, you can use something like
subdomain.domain.com
and for other languages, subfolders like
subdomain.domain.com/it
. When migrating your site from the subdomain to the main domain, we recommend using the Duplicator plugin, which will take care of the URL replacement process. After the migration, you must register WPML on your new site and enter the new key by following these steps : 1. Log in to your WPML account. 2. Go to the 'Sites' page (https://wpml.org/account/sites/). 3. Delete your old site/domain. 4. Add your new site to get a new WPML key, which you can add to your site under Plugins > Add New > Commercial. Also, make sure your future hosting package meets the minimum WPML requirements, which you can find here: https://wpml.org/home/minimum-requirements/. If you use Duplicator, you will see how changing URLs in the database works during the migration. The person in charge of migrating your site should be familiar with the WordPress migration procedure.
This solution may not be relevant if it is already outdated or does not apply to you. If so, we recommend opening a new support ticket. We also suggest that you review known issues at https://wpml.org/known-issues/, check the version of the permanent solution and confirm that you have installed the latest versions of themes and plugins. If you need further help, feel free to contact us on the WPML support forum.
Problem: The client wanted to delete a language and all its database entries, but the process was not completing. Solution: First, we recommended increasing the memory limit and ensuring that all components are up to date. We provided a link to a related support ticket for reference: https://wpml.org/forums/topic/cant-delete-languages-stuck-in-a-loop/
Please note that the solution might be irrelevant due to being outdated or not applicable to your case. If so, 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 issue persists, please open a new support ticket with us.
Problem: The client's website displays reviews in multiple languages, each with an associated flag representing the language of the original review. However, when a review is translated, the flag changes to that of the translation language instead of staying as the flag of the original language.
Solution: 1. We explained that the behavior observed by the client is expected and by design. When a review is translated, the flag of the currently displayed language is shown. This is explained in our documentation on Translating and Displaying Product Reviews.
2. If the client prefers not to display flags with reviews, they can disable the option by going to WooCommerce > WooCommerce Multilingual > Settings and unchecking 'By default the reviews should be displayed in all languages.' More information can be found in our documentation on Showing Product Reviews in All Languages.
Please note that the solution provided might be irrelevant if it's outdated or not applicable to your 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 you still need assistance, please open a new support ticket. You can do so by visiting the WPML support forum.
Problem: The client was unable to translate the word 'products' in the Product Categories Carousel on their homepage, even after translating all relevant strings in the string translation.
Solution: We found that the string in question was using the *%s Products* string from the *the7mk2* string domain. We translated the *%s Products* string to Chinese, which resolved the issue.
If you're experiencing a similar issue, we recommend trying to locate the exact string within your theme or plugin's string domain and translating it accordingly. If the solution provided here is not relevant to your case, perhaps because it's outdated or simply not applicable, we highly encourage you to open a new support ticket. Additionally, it's always a good idea to check the related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins.
If you need further assistance, please don't hesitate to contact us by opening a new ticket in the WPML support forum.
Problem: The client is trying to translate their site using WPML and Elementor but is facing issues with translating the slider and Elementor's saved templates. The translated pages are not being displayed correctly, and the site continues to show the English version despite the client's configuration. Solution: 1. We advised the client to check if they are using a custom Elementor Module for the slider feature and to add WPML language configuration for proper translation. 2. We provided documentation links to guide the client on how to register custom Elementor widgets for translation:
3. We recommended that the client update to the latest versions of Elementor and The7 theme, ensuring they perform a full site backup before doing so.
Please note that 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. If the issue persists, please do not hesitate to open a new support ticket with us. For further assistance, you can reach out to our support forum in your language.
Problem: The client was experiencing an issue where parts of a page were not translated, even after translating them in String Translation, as they still appeared in the default language. Solution: We resolved the issue by taking the following steps: 1. We created a
404.php
file in the child theme. 2. We made slight changes to the code. 3. We deleted the
wpml_st_upgrade_in_progress
key from the
wp_options
table. 4. We translated the strings again.
We then asked the client to check if the translated strings were displaying correctly.
Please note that this solution might be irrelevant due to it being outdated or not applicable to your case. If you're still facing issues, 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.
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 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 needed, do not hesitate to open a new support ticket for further assistance at our support forum.
Problem: The client is experiencing a conflict between WPML and their compare page, which stops functioning when WPML is active. Solution: We recommend making a backup of the website and then following these steps: 1. Navigate to Appearance > Theme File Editor. 2. Select the file
If the Theme File Editor is not available, the client can edit the file directly via FTP or in the hosting file manager. Additionally, we asked the client to install their theme in our Sandbox to investigate a potential compatibility issue between WPML and the Woodmart theme.
If this solution is not relevant due to being outdated or not applicable to your 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 the issue persists, please open a new support ticket with us.
Problem: Currency switcher is not showing in Products page Solution: We identified that the issue was due to an incorrect setting in WooCommerce Multilingual Currency settings. The client had selected the option *Show only products with custom prices in secondary currencies*, which should not be selected if the prices in secondary currencies are calculated automatically. We advised the client to disable this option, which resolved the issue and the currency switcher started to appear on the product pages.
If you're experiencing a similar issue with the currency switcher not appearing, we recommend checking your WooCommerce Multilingual Currency settings and ensuring that the option to show only products with custom prices in secondary currencies is disabled if you are using automatic price calculation for products in secondary currencies.
Please note that this solution might be irrelevant if it's outdated or not applicable to your 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 you still need assistance, please open a new support ticket with us.
Problem: The client needed to assign specific payment gateways and the 'cash on delivery' method to different currencies using WooCommerce Multilingual & Multicurrency. The built-in functionality was limited and did not support the client's payment gateways.
After further clarification and internal discussion, we acknowledged that there is no out-of-the-box solution for unsupported gateways. We suggested using the
woocommerce_payment_gateways
hook to add or remove gateways based on the selected currency. We provided an example code snippet to guide the client:
We also recommended that if the client requires further custom solutions, they should consider reaching out to our recommended third-party developers: https://wpml.org/contractors/.
Please note that this solution might be irrelevant due to being outdated or not applicable to your case. If so, 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 with us.
Problem: The client is experiencing error messages(WPML Plugin cannot connect to WPML.org) in the WordPress backend related to WPML. Solution: 1. Navigate to Plugins > Add New > Commercial tab. 2. Click on the "Check for updates" button to force a connection to wpml.org. If no errors occur, the notice should disappear or can be considered a false positive. 3. If the issue persists, it may be due to a conflict with firewalls. In this case, whitelisting WPML URLs is recommended. For more details, please refer to the following documentation:
Please note that this solution might be irrelevant 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 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 contact us in the WPML support forum.
Problem: The client is experiencing an issue where after translating a page to a second language, any subsequent edits to the original language page cause the translation to revert to the original language content. Solution: If you're experiencing this issue, it's important to ensure that you're translating content independently rather than syncing it from the default language. To do this correctly, follow the steps in our guide:
Make a small update to the default language page and then update the translation.
If these steps do not resolve your issue, the solution might be outdated or not applicable to your case. 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 you still need help, please open a new support ticket.
Problem: The client is trying to optimize an English website for a French-speaking audience using French keywords with the Yoast SEO plugin on English pages.
Solution: We explained that once the WPML SEO plugin is activated, it allows for the translation of various Yoast SEO plugin fields. This means that when translating content, the client also has the option to translate SEO-related information, which will be reflected in the translated post/page.
To include French keywords on English pages, the client can use the Yoast SEO plugin's meta box in the Editor to enter Meta titles, descriptions, keywords, and other SEO-related properties. The client can add French keywords in the meta fields to optimize English pages for a French-speaking audience without changing the content language.
When translating English content into French, the keywords entered in the meta fields will be available for translation in the Editor, allowing the client to translate them as needed.
We also recommended consulting the official documentation and support team of the Yoast SEO plugin for additional details on the Meta box and referred to a guide on optimizing page titles for SEO: https://yoast.com/page-titles-seo/.
If this solution is not relevant due to being outdated or not applicable to your case, we suggest opening a new support ticket. 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 contact us in the WPML support forum.
Problem: The client wants to integrate a function to convert Traditional Chinese to Simplified Chinese using the Autohan plugin, and incorporate this option under the WPML language switcher menu.
Solution: We do not provide support for custom coding. However, we recommend checking the following resources for guidance:
If you require additional custom work, we suggest contacting WPML Contractors.
Please note that the solution provided might be irrelevant due to being outdated or not applicable to your case. If so, 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.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
