Problem: The client was experiencing several issues: 1. A translated contact form was showing an error. 2. The client was unable to change the link in the main menu "Home" option to redirect to the translated page. 3. FAQ question titles were "registered and locked" and couldn't be translated. 4. The "MAP LOCATION" on the home page was not available for translation in string translation or admin strings.
Solution: 1. We translated the contact form shortcode via String Translation. 2. & 4. We instructed the client to translate the custom URL menu items via String Translation for both the Main Menu and the Location Menu. 3. We located the FAQ items in String Translation for the client to translate.
Problem: The client was experiencing issues with missing replies in a Buddyboss forum when switching languages.
Solution: We found that the issue was due to missing translations for the discussion and the replies. We recommend translating the entire discussion and all replies within it to ensure they appear correctly when switching languages.
Problem: The client is trying to make the WPML plugin compatible with the MotoPress Hotel Booking Plugin and the Hotell Pro Theme by Good Looking Themes. The client is facing issues with translating fields controlled by the theme and is unsure if WPML automatically translates these or if manual translation is necessary. Solution: We recommend the following steps to ensure that your theme and plugins are fully compatible with WPML for translation: 1. Navigate to WPML -> Theme and plugins localization, select your theme/plugin, and perform a scan. 2. Go to WPML -> String Translation. 3. Scroll down and click on the "Translate texts in admin screens »" link. 4. Search for the strings you need to translate. 5. Select the strings you wish to translate. 6. Click on the "Add to String Translation" button. 7. Then click on the "« Return to String Translation" link. 8. Translate the selected strings, clear your site's cache, and check the front end to see the changes. For more detailed guidance, please refer to our documentation on translating texts in the admin texts screen.
If this solution doesn't look relevant to your issue, please don't hesitate to open a new support ticket with us.
Problem: The client reported that when a customer places an order for an item in Language 1 (Slovenian), the order confirmation email shows the item in Language 2 (Croatian). Solution: We identified that the client was using the incorrect slug for the checkout process. We provided the correct link to use, which includes the proper slug and parameters to clear the cart and add the item directly. Here is the corrected link format:
Problem: The client is unable to allocate prepaid credits to their site, specifically to a development site that has been changed to production. They also cannot see the option to allocate or transfer prepaid credits within the Translation Management tools, only the pay-as-you-go option is visible. Solution: 1. Unregister and re-register the site with a new sitekey. 2. Assign credits again to the development site. Refer to the documentation on how to unregister and register development sites:
To transfer credits back to your WPML.org account or add credits to your site: 1. On your site, use the option to transfer credits back to your WPML.org account. 2. On your WPML.org account, add credits to your site, or delete the sitekey to get credits back. Refer to the documentation on how to assign automatic translation credits: Assigning Automatic Translation Credits
Problem: The client was having difficulty setting up 'A different domain per language' using two domains, one for Czech and another for Slovak. Both domains were pointing to the same IP, but the second language domain could not be validated. Solution: We reviewed the settings and noticed that although the client had valid SSL certificates for both domains, the URL was being saved as http instead of https. We corrected this from the Settings -> General panel and refreshed the website. After this change, the second language domain was validated successfully.
If this solution doesn't seem relevant to your situation, please don't hesitate to open a new support ticket with us.
Problem: The client reported that after moving from a beta page to a live environment, some parts that were previously translated via string translation were not showing as translated on the front end. Solution: We recommended the client to first perform a full backup of their site. After that, we instructed them to access their server via FTP and navigate to the
wp-content/languages
folder. We then advised them to remove all language files, leaving only the three folders as shown in our provided screenshot. This action should resolve the issue.
If this solution does not seem relevant to your situation, please open a new support ticket with us.
Problem: The client is trying to use automatic translation but is facing an issue where the translation page shows that they don't have enough credits, despite having more than 60k credits in their account. Solution: If you're experiencing an issue where your translation credits are not showing up on your new site after duplicating from an older site, we recommend the following steps: 1. Unregister WPML from the new site by following this guide: Unregister WPML. 2. Generate a new site key from your WPML.ORG account and re-register WPML with that key. Instructions can be found here: Register WPML. 3. Remove the credits from the previous site using the guidelines here: Remove Credits from a Site. 4. Allocate credits to your newly registered site by following the instructions here: Assign Automatic Translation Credits. If after following these steps the problem persists, please open a new support ticket with us and we will be happy to assist you further.
Problem: The client is attempting to switch content from a custom taxonomy called
custom_tag
to the standard
post_tag
, with all custom tags translated into multiple languages. They encountered an issue where after using the Taxonomy Switcher plugin, all taxonomies were assigned to the English language, and troubleshooting did not resolve the issue. Solution: We have verified that the Taxonomy Switcher plugin is not yet compatible with WPML. We recommend the following steps: 1. Review the WPML compatibility list for plugins: - https://wpml.org/plugin/ - https://wpml.org/documentation/plugins-compatibility/ 2. Consult the documentation on how to import terms: - Importing multilingual terms with WP All Import and WPML 3. Check out related support tickets that might offer a solution:
Problem: The client needs to block the WPML language cookie "wp-wpml_current_language" by default and only allow it after user consent is obtained through a consent banner powered by OneTrust. They require the exact source URL or path from which this cookie is fired to configure OneTrust. Solution: We recommend trying the following URL:
that sets the language cookie for non-logged users via JavaScript to avoid issues with cached pages. For logged-in users, such as admins, the cookie is set via PHP. Additionally, you can check our documentation on browser cookies stored by WPML here:
Problem: The client was experiencing 500 errors with the ajax-based quick search bar in the Flatsome theme. The debug log indicated a fatal error with the
get_requested_lang()
function in the WPML plugin. Solution: We asked the client to confirm the version of the Flatsome theme they were using and suggested updating to the latest version if they were not on version 3.18.2. The client discovered that the issue was caused by the Query Monitor plugin, which nullified the
Problem: The client needed to change the default country codes for Malay, Simplified Chinese for China, and Traditional Chinese for Taiwan to /my, /cn, and /tw, respectively. They encountered an issue where the system indicated that the default locale already exists when trying to set the custom language settings. Solution: We recommended that the client should use a different language name and locale for the custom language. Specifically, for Malay, the client should use the locale
my_MY
. We provided guidance to follow our documentation on editing WPML's languages table, which can be found here:
These pages also contain several related FAQs that may be helpful.
3. When migrating the site from development to production, it's important to ensure that translations are available on the production site. For this, please see:
Problem: The client reinstalled WPML and set it to automatic translate, but the translations were not starting even though there were enough credits available. Solution: 1. We asked the client to check if they had enough credits for the Automatic Translation to run. 2. We requested the client to provide debug information by following these steps: - Navigate to WPML > Support > Debug Information - Copy the Debug Information. - Paste the information into the private field we activated for this purpose. You can find the instructions here: https://wpml.org/faq/provide-debug-information-faster-support/ 3. After reviewing the client's reply, we identified and fixed some misconfigurations on our end. 4. We advised the client to retry the automatic translation process.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
