Problem: The client wanted to use the PHP language switcher from the main site on one of the subsites in a multisite setup, but it was not appearing. Solution: We explained that sub-sites are considered separate sites and therefore cannot display the language switcher from the main site. To add a language switcher to a sub-site, the client needs to: 1. Install WPML on the sub-site. 2. Translate the pages on the sub-site. 3. Add the language switcher in WPML → Languages.
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 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.
Problem: The client is experiencing issues with registering their site on WPML due to a discrepancy between the SiteURL and HomeURL. The site is built on the Bedrock platform, which causes the URLs to differ, and the client's developer is unable to make them the same without breaking the site.
Solution: We recommend updating all WPML plugins and WordPress to the latest versions to ensure compatibility and to benefit from the latest bug fixes and improvements. This may not resolve the issue, but it is a necessary step for troubleshooting.
1. Backup the database. 2. Update the WPML plugin to the latest version, currently 4.6.9, and all add-ons. 3. Update WordPress to the latest version. 4. After updating, attempt to register the site again and provide a screenshot of any errors, along with the URL used for registration.
If the problem persists after following these steps, or if this solution 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 necessary, please open a new support ticket for further assistance: WPML support forum.
If the solution provided here is not relevant to your case, either because it's outdated or it doesn't apply to your specific situation, 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 don't hesitate to open a new support ticket with us.
Problem: The client was experiencing an issue with the order of product attributes when switching languages. Although the colors were translated correctly, the attribute 'black' was not appearing first in both languages as expected. Solution: We explained that by default, attributes are ordered by their ID, which is the number visible before them, and this ordering is consistent across all languages. To arrange the attributes in a specific order, we advised the client to go to Products > Attributes and adjust the order there. This should be done in the second language by switching the language using the top admin bar.
If this solution does not apply to your case, or if it seems outdated, we recommend opening 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 is trying to automatically translate pages from English to German on their website, but encounters issues when reviewing the translations. Some pages work fine in English, but not when translated.
Solution: 1. We recommended clearing all types of caches to ensure that the issue is not related to cached content. 2. We asked the client to confirm if the problem persists after clearing the cache. 3. We informed the client that the 'Top-rated Hedges' page is visible in the WPML>>Translations queue and that the 'floraintermediair' page's translation is completed and in 'Translation needs update' status.
If you're experiencing similar issues, we recommend you try the following steps: - Clear all types of caches on your website. - Check if the issue still exists. - Review the translation status in the WPML>>Translations queue.
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, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If you need further assistance, please open a new support ticket.
Problem: The client is experiencing an issue where both the staging site and the main website are asking for an activation code after creating a staging environment. Additionally, the client mentioned that Elementor Beta is needed. Solution: We recommend deactivating third-party plugins to identify the source of the issue. In this case, deactivating the 'Elementor Beta (Developer Edition)' plugin resolved the problem with the footer not working correctly in Chinese. If you're experiencing this issue, try deactivating the Elementor Beta plugin and check if that resolves the problem.
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.
Problem: The client's homepage is showing as not translated ("+" icon) for the English language, despite having been translated previously. After marking the translation as complete, the pencil icon appears, but the translation does not display on the actual page. Upon refreshing the page list, the homepage reverts to showing as not translated.
Solution: We recommend the client to first create a full backup of their database and website. Then, navigate to WPML > Support > Troubleshooting and perform the following steps:
Clear the Cache in WPML
Remove ghost entries from the translation tables
Fix element_type collation
Fix WPML table collation
Set language information
Fix post type assignment for translations
After completing these steps, resave the translation and check 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 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 do not hesitate to open a new support ticket in the WPML support forum.
Problem:
I'm seeking assistance with loading header menu and footer from external files and ensuring their text content is automatically translated. Additionally, CSS styling for the translation switcher on index.php is not being applied.
Solution:
For the header menu, if it's a WordPress menu, you can follow WPML documentation for translating menus: https://wpml.org/documentation/getting-started-guide/translating-menus/. If it's not a standard WordPress menu, you'll need to wrap all text inside PHP code with the gettext method and then translate them using WPML String Translation.
For the footer, if it's widget-based, follow steps for translating widgets: https://wpml.org/documentation/getting-started-guide/translating-widgets/. If it's directly added to the theme, wrap text in PHP code with the gettext method, scan the theme for strings, and translate them using WPML String Translation.
To apply CSS to the translation switcher on index.php, wrap all direct text in PHP code with functions like __() and then scan the theme for strings. Translate them using WPML String Translation, and the CSS should apply automatically.
Problem: The client was experiencing an issue with the splitting of Arabic letters in titles on their slider. Solution: We informed the client that the issue with the splitting of Arabic letters seems to be related to the slider itself and not WPML. To confirm this, we suggested the following steps: 1. Deactivate WPML. 2. Create a new page and add the slider. 3. Insert Arabic words into the slider. 4. Observe if the same issue occurs with WPML deactivated. If the issue persists, it confirms that it is not related to WPML and the client may need to check the slider settings or contact the slider's support team for further assistance.
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 help, please open a new support ticket with us.
Problem: The client needed assistance with two issues: first, the European Union logo on their site was not changing to display "European Union" in the international versions of the site. Second, they were experiencing problems with having different contact forms for each language version of the site using UX Builder, as translations would revert to the default Polish version. Additionally, they inquired about handling forms from Pipedrive and Contact Form 7 plugin for different language versions.
Solution: For the logo issue, we did not receive information about the solution provided. Regarding the contact forms, we suggested two steps: 1. To translate the Webform URL, search for "HTTP" using the provided search form and replace the URL with the correct language form URL. 2. To have separate forms for each language, create a distinct form for each language. This approach is necessary because translating the form using WPML's contact option will not create separate versions for secondary languages. For more information on using Contact Form 7 with WPML, visit this documentation.
Please note that the solution provided 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 here.
Problem: The client is experiencing an issue where emails sent from the translated Contact Form 7 are not being delivered to the intended recipient's email address, but instead to a different one. Solution: If you're experiencing this issue, we recommend following our guide on Using Contact Form 7 with WPML. To check the email notification settings of the translated form, please follow these steps: 1. Edit the original form. 2. Switch to the translated form using the top admin bar. 3. Check the email settings under the "Mail" tab.
Please note that the solution provided 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.
Problem: The client's website went down after updating WPML, and they encountered an error list from the debug.
Solution: 1) We suggested that the issue might be due to an incorrect update process, resulting in missing files. We recommended manually downloading and installing the necessary files from the provided links:
Additionally, we recommended creating a full website backup before proceeding with any changes to ensure there is a recovery option available.
The client later confirmed that updating the translation and multilingual components resolved the issue, and they disabled auto-updates to prevent similar problems in the future.
Please note that the solution provided 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.
Problem: The client was experiencing issues with translating individual links in the menu. While the pages were translating correctly, custom links such as "Unterkünfte" or "Über uns" were not translating and were directing to the wrong language version.
Next, we suggested the client to adjust the links to point to the correct language version by: 1. Going to WPML -> Settings. 2. Clicking on "Translate Link Targets". 3. Clicking the "Scan now and adjust links" button.
Finally, for links within Elementor templates, we instructed the client to: 1. Switch to the desired language. 2. Edit the page with Elementor. 3. Click on the element that contains the link. 4. Change the link address in the element settings.
We advised the client to follow these steps for each link that needed translation and to check if the issue was resolved.
If the provided solution does not apply or is outdated, or if further assistance is needed, 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 the latest versions of themes and plugins are installed.
Problem: The client is experiencing issues with the Affirm payment gateway on their bilingual English and French Canadian WooCommerce site. When trying to checkout in French, the Affirm checkout flows remain in English. The client suspects this might be due to the default locale values being set to "en_US" and "fr_FR" instead of "fr_CA" for the Canadian locale.
Solution: We confirmed that default locales are editable and that the client correctly changed the locale to "fr_CA". However, changing the locale can cause issues with WooCommerce translations because they are tied to the default locale. To address this, the client can either translate the missing strings themselves or install the French Canadian language pack. For the Affirm issue, we suggested checking if the Affirm WooCommerce plugin integration can be translated via String Translation. Additionally, we pointed out that the Affirm documentation requires adding a script with specific locale and country code parameters. Since WPML requires two locales for bilingual sites, the client might need to load a different script for French pages. We acknowledged that this is a complex issue that may require the cooperation of the Affirm author and suggested that the client contact one of our contractors for further assistance.
Please note that this solution might be irrelevant due to being outdated or not applicable to your case. If so, 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. If you need further assistance, please contact us on the WPML support forum.
Problem: The client needed to migrate or change the language of multiple posts from the default language to another language within a custom post type created using ACF multilingual. Solution: We informed the client that WPML Export and Import can be used to export and import posts into different languages. However, it is necessary to import the posts in the default language first and then import the translations to establish the correct connections between them. We provided the client with documentation links for detailed instructions:
If the provided solution is not relevant due to being outdated or not applicable to your case, we recommend opening a new support ticket. We also highly suggest 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 through the 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
