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.
Problem: The client unintentionally translated their page builder, Beaver Builder, when adding new languages and is unsure about which settings to adjust to prevent or reverse this. Solution: We recommend checking the "WPML > Settings > Post Type Translation" section. Here, you can set the translation preference for Templates (identified as
fl-builder-templates
) and Layouts (
fl-theme-layout
) to "Translatable" if you wish to translate them. If you do not want these to be translated into new languages, you should set their translation setting to "Not Translatable" within the same section. If this does not resolve your issue or if the problem is different, please provide us with more details or screenshots to better understand the situation and assist you further.
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 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, do not hesitate to open a new support ticket. You can do so by visiting the WPML support forum.
Problem: The client was experiencing an issue where the language switcher was not redirecting to the Greek version of the site when selecting 'EL'. The language switcher was implemented as a shortcode in Woodmart's Header builder under 'Header Minimalism'. Solution: We identified that a block of code in the .htaccess file related to the GTranslate plugin was causing the issue. The code looked like this:
### BEGIN GTranslate config ###
...
### END GTranslate config ###
After removing this block of code from the .htaccess file, the language switcher started working correctly. If you're experiencing a similar issue, we recommend checking your .htaccess file for any remnants of the GTranslate plugin or similar configurations that might be interfering with the language switcher functionality.
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 need further assistance, please don't hesitate to open a new support ticket with us.
Problem: The client reported that despite having installed, activated, and licensed the WCFM Ultimate Plugin, the dashboard was still prompting to purchase the plugin. Solution: We first confirmed that there are no known compatibility issues with the WCFM Ultimate Plugin, except for the "Policy" page, which is documented here: https://docs.wclovers.com/wcfm-wpml/. We then suggested that the issue might be related to permalinks settings, which differed from those in our Sandbox environment. We recommended that the client contact WCFM support for further assistance, as the issue could not be reproduced from scratch, indicating that it might not be a general compatibility issue that we could address with a code patch.
If you're experiencing a similar issue, we recommend checking your permalinks settings and reaching out to WCFM support for help. 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 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 open a new support ticket with us: WPML support forum.
Problem: If you're experiencing performance issues when copying Advanced Custom Fields (ACF) to translations with WPML, such as slow operations or timeouts, this might be due to inefficiencies in the code handling the copy process.
Solution: We recommend modifying the
SitePress::copy_custom_fields
and
WPML_Copy_Once_Custom_Field::copy
methods to improve performance. Here are the steps to follow:
These changes should optimize the process by reducing the number of instances where the entire post meta is fetched and looped through, thus improving the performance when copying ACF fields to translations.
Problem: The client has migrated their database from pre-production to production and encountered an error message regarding the use of automatic translation credits on both environments. Solution: We recommend selecting the 'Yes (copy)' action to share credits between the sites. This will allow the client to manage the credits independently while ensuring that the translation memory is shared, regardless of whether the sites have different content. For more detailed guidance, we suggest consulting our documentation on Automatic Translation Subscription for Multiple Sites.
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 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 in our support forum.
Problem: The client reported that automatic translation was not starting on their website.
Solution: We found that the site UUID on the client's site did not match the one on our server. We corrected this issue, and now the automatic translation should work properly.
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 is unable to connect to the WPML Advanced Translation Editor.
Solution: For this issue, we recommend the following steps: 1. Navigate to Plugins > Add new > Commercial tab. 2. Un-register and then re-register your site with a new sitekey. 3. Go to WPML > Settings > Translation Editor. 4. Select Editor for new translations: Classic Translation Editor and save. 5. Reload the page and switch back to the Advanced Translation Editor. For detailed instructions, please refer to our documentation:
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 necessary, do not hesitate to open a new support ticket for further assistance. You can do so at the WPML support forum.
Problem: After installing WPML plugins, the WooCommerce default product page is not displayed correctly, with vertical text on the far right. Solution: If you're experiencing this issue, it's not caused by WPML or the WPML SEO plugin. The problem arises because the product table has many columns, which reduces the space for text, causing it to appear vertically. To resolve this, you can hide the unnecessary columns by using the "Screen Options" at the top right corner of the page. For more details, please check this article: https://jeswebdevelopment.com/vertical-text-when-viewing-posts-in-wordpress/.
Please note that this solution might be irrelevant if it's 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 the issue persists, please open a new support ticket with us.
Problem: The tools tab in the Translation Management section shows an error message "There is a problem connecting to automatic translation. Please check your internet connection and try again in a few minutes". Solution: The problem was caused by a known compatibility issue with the "Email Encoder" plugin. Please create a full backup of your site. Then, visit our errata page for the "Email Encoder" plugin at https://wpml.org/errata/email-encoder-protect-email-addresses-and-phone-numbers-there-is-a-problem-connecting-to-automatic-translation/ and try the workarounds provided there.
If you still need assistance, don't hesitate to open a new support ticket with us.
Problem: The client added custom code to the functions.php file in their child theme to display stock status in a WooCommerce product dropdown but was unable to translate the 'In Stock' and 'Out of Stock' text.
Solution: 1. We advised the client to wrap the hardcoded strings with the gettext function
__()
to make them translatable. Specifically, replace:
return $stock == 1 ? ' - (In Stock)' : ' - (Out of Stock)';
2. We instructed the client to scan the theme for strings from the WPML > Theme and plugins localization page. 3. We directed the client to go to WPML > String Translation, search for the 'In Stock' and 'Out of Stock' strings, and add the translations.
For more details, we provided documentation links:
Problem: The client was adding translations for various languages to a page built with Elementor. While most content translated correctly, the basic text editor widget in Elementor did not translate for the Indonesian language, displaying what appeared to be the widget's ID instead. The WPML translation editor showed the text as translated, but it was not reflected on the front end. Solution: We recommended the client to back up their website and deactivate any additional Elementor plugins one by one to identify which one was causing the issue with the text not displaying in the original language. Once identified, we asked the client to install the problematic plugin on a test site we provided (https://rustic-guitar.sandbox.otgs.work) where Elementor and WPML were already set up with English and Indonesian languages. The client was to create a sample page using the widget so that we could check and provide the proper XML code to make the widget translatable with WPML.
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 do not hesitate to open a new support ticket. For further assistance, visit our support forum.
Problem: The client is experiencing an issue where the accommodation pricing on their website is correctly displayed in English as "price for 2 nights" but incorrectly in Portuguese, showing "xx per night" even though the price is set for 2 nights. This issue occurs on both the accommodations page and the search availability results on the homepage.
Solution: We recommend the following steps to resolve the issue: 1) Go to WPML > Theme and plugins localization. 2) Scroll down to the *Strings in the plugins* section. 3) Select the *Hotel Booking* plugin. 4) Click to scan for strings and wait until the process is complete. 5) Navigate to WPML > String Translation. 6) Search for the string "for %d nights" or "%d nights". 7) Translate the string into Portuguese, as the original string is in English.
Please ensure to clear all types of caches after performing these steps and check if the issue is resolved.
If the solution provided here is not relevant to your case, possibly because it's outdated or not applicable, we highly recommend opening a new support ticket. Before doing so, please 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. For further assistance, you can reach out to us on the WPML support forum.
Problem:
After using the "Look for strings while pages are rendered" feature and translating custom strings, the client disabled the feature and encountered a fatal error that prevented access to both the admin area and the site. The error was caused by strings from the Kadence plugin with "%TEXTDOMAIN%" as a context in the
wp_icl_strings
table.
Solution:
We recommended changing the context of the problematic strings in the
wp_icl_strings
table from "%TEXTDOMAIN%" to "kadence" to resolve the issue. Additionally, we advised using the gettext functions
__()
or
_e()
according to WordPress standards for future string translations.
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 is experiencing an issue where the menu in the English dashboard does not match the menu on the website. Solution: We recommend using WPML's WP Menus Sync feature located in WPML → WP Menus Sync to synchronize menus across all languages. This will match the translated menus to the default language menu. After synchronization, use String Translation to translate URLs and labels for any custom links. For more information about the WP Menus Sync feature, please visit Translating Menus documentation.
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 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 in our 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
