Problem: The client was unable to translate certain custom fields using Advanced Custom Fields (ACF) and WPML's Advanced Translation Editor (ATE), despite setting the fields as translatable. The issue was due to multiple fields having the same name across different field groups, which caused WPML to apply the same translation settings to all similarly named fields. Solution: 1. Verify that the field groups in ACF are set to 'translatable' under ACF -> Fields groups. 2. Ensure that in WPML -> Settings, the field groups for ACF are set to 'untranslatable' if they should not be translated. 3. For fields that need to be translated, ensure each field name is unique across all field groups to avoid conflicts in translation settings. 4. If the issue persists with existing content, make a minor edit in the default language and update the page. Then, access the translation editor where the field should now be available for translation.
Please note that this solution might be outdated or not applicable to your specific 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 needed, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is using Avada Builder for their website and wants to automatically translate German pages into English using WPML and DeepL. However, not all texts on the pages are being translated. Solution: We identified that the Rank Math SEO plugin is causing issues with redirection that might affect the translation process. We recommend checking the redirection rules set in Rank Math SEO -> Redirection and consider disabling unnecessary redirections that could interfere with WPML's translation capabilities. Additionally, it's important to ensure that the homepage is translated into all required languages (Czech, Dutch, French, Italian, and Russian) to enable proper functioning of the Language Switcher and other links.
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. Should further assistance be needed, please open a new support ticket at WPML support forum.
Problem: The client was unable to see the contact forms in the translation managers for auto-translation, despite following the documentation on using Contact Form 7 with WPML. Solution: We installed a local copy of the client's site to identify the issue and discovered a corrupted database record. After repairing this record, the contact forms became visible in the Translation Management. We applied the same fix to the client's site, resolving the issue. The client should now be able to translate the contact forms as expected.
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 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 https://wpml.org/forums/forum/english-support/.
Problem: The client reported that after translating elements, the shop page on their website appeared broken, displaying a PHP Fatal error related to an unknown format specifier in a theme file. Solution: We identified the error in the file
on line 41. The issue was due to an incorrectly translated string. We removed the incorrect translation and re-translated it correctly. We recommend checking the translated shop page to ensure the issue is resolved.
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. If the problem persists, please open a new support ticket.
Problem: You are trying to translate an email template using WPML, but the plugin used for the email templates is not compatible with WPML. Solution: We recommend contacting the plugin author to encourage them to join our Go Global program. Meanwhile, you can try the following workaround:
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 WPML support forum.
Problem: After migrating the site to a new server, the client noticed that the translated menus were not connected with the menus of the default language, English. Solution: We reconnected the menus for the client. If you're experiencing this issue, we recommend you go to Appearance-> Menus, switch the language to the one you need (e.g., German), and edit each menu to translate the custom link menu items or menu item labels to the respective language. Afterward, check the menus on the front end to ensure they are displaying correctly.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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. Additionally, you can open a new support ticket for further assistance at WPML support forum.
Problem: If you're experiencing a fatal error stating 'Uncaught Error: Call to undefined function mb_ereg_replace_callback()', it indicates that your server is missing the Multibyte String Extension, which is crucial for the WPML plugin to function correctly. Solution: We recommend installing the Multibyte String Extension on your server to resolve this issue. Additionally, ensure that your server meets all the minimum requirements specified by WPML.
If this solution does not apply to your case, or if it seems outdated, please open 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. For further assistance, you can also visit our support forum at WPML Support Forum.
Problem: You need to translate the Customer Consent Text field in the Customer Reviews for WooCommerce plugin using WPML. Solution: 1. Go to WPML-> Theme and plugins localization, select your theme/plugin, and scan. 2. Navigate 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 details on translating texts in admin screens, visit our guide: Translating texts in admin screens guide.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also highly suggest 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: WPML support forum.
Problem: The client is experiencing an issue where string translations are not showing on the front-end when the string checker is disabled. They have tried solutions from other tickets without success. Solution: 1. We recommended updating WordPress and all plugins to ensure compatibility and resolve any potential conflicts. 2. We advised the client to check the WPML -> String Translation section to ensure that strings related to the theme are correctly translated and that no multiple text domains are causing conflicts. 3. We suggested installing the Contact Form 7 Multilanguage addon to help with translating contact forms.
4. The issue was resolved by adding the correct text domain to the styles.css file of the theme (as it was showing two different ones on WPML -> String translation).
If this solution does not resolve your issue or seems outdated, 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 the problem persists, please open a new support ticket.
Problem: The client wanted to translate the 'SIGN UP BUTTON' in the Buddyboss theme and change its URL redirection for the French version but couldn't find the button in the string translations. Solution: 1. Go to WPML > String Translation. 2. Enter the button link in the search box and click on the search button. 3. If the link appears in the results, click on the "+" icon and add the translated link for the French language. 4. If the link doesn’t appear correctly in French, scroll down to the bottom of the String Translation page and click on Translate texts in admin screens. 5. Enter the link in the search box. 6. If the link appears there, select it and add it to String Translation. 7. Return to WPML > String Translation and translate the link.
If this solution does not resolve your issue or seems outdated, 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client has successfully translated all pages and set them as published, but the translated menu is not displaying in the Polish version. Additionally, the HOME button in the Polish homepage redirects to the English homepage instead of the Polish one, despite running 'Translate Link Targets' and 'Menu Synch'. Solution: We translated the header template, which should now correctly display the navigation menu on the Polish page. We recommend the client to check if the navigation menu is appearing correctly in Polish. If the HOME button still redirects incorrectly, it might require further adjustments in the settings or additional translation of the link targets.
If this solution does not resolve the 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. Should the problem persist, please do not hesitate to open a new support ticket at WPML support forum for further assistance.
Problem: The client installed WPML and selected automatic translation with the option to review before publishing. However, they were not satisfied with the quality of some translations and attempted to manually edit them. Despite saving changes, an orange bar appeared indicating the translation was not finished. Various troubleshooting steps, including restarting the plugin and deleting translated pages, did not resolve the issue. After reconfiguring WPML in manual mode, only one page was successfully translated, and others were not editable. Solution: We advised the client to reinstall the WPML plugin and activate it. They should then proceed with the WPML setup at their WPML account dashboard and generate a sitekey to activate the plugin. For issues with saving edited translations, we provided a screen recording demonstrating how to properly save changes. If automatic translation does not fully cover sections created with third-party modules in Elementor, it is necessary to register these modules for translation as explained in our documentation: Registering Custom Elementor Widgets for Translation.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client reported that texts in the fields for the English language on an Advanced Custom Fields options page changed to Russian unexpectedly. Other languages displayed correctly.
Solution: We attempted to reproduce the issue by: 1. Opening the options page in the default English language. 2. Changing some section texts back to English and saving. 3. Switching to Russian to check if the changes were overwritten and then saving. 4. Switching back to English to confirm if the changes persisted.
Since the issue could not be reproduced, we suggested that the client monitor the site closely and isolate the issue on a staging site if it occurs again. It's important to note any special activities or workflows that might influence the language settings.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 move a multisite subdomain with translations to a new single domain and want to know if you can export and import WPML settings to another domain. Solution: We cannot export or import WPML settings directly. However, you can export and import translations. We recommend using tools like WP Import Export or WP ALL Import along with our addon, WPML Import Export. For more detailed guidance, please refer to our documentation on how to use these tools.
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. If you still need assistance, please open a new support ticket at WPML support forum.
Problem: The client is unable to register a site key for their WordPress site and receives an error message: 'Unable to parse data from service response.' They have confirmed that their server hosting is not blocking any relevant domains. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Ensure you have a backup of your site. 2. Disable all other plugins, leaving only WPML plugins active. 3. Switch to the WordPress default theme. 4. Check if the issue still occurs. 5. If the problem persists: - Go to Plugins -> Add New -> Commercial on your website. - Unregister WPML by clicking the unregister link. - Visit https://wpml.org/account/sites/ and delete the existing site key. - Return to Plugins -> Add New -> Commercial on your website. - Click the register link and use the new site key to register.
If this solution does not resolve the 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 further assistance is needed, please open 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
