Problem: You are working on a site and trying to translate a test blog post using WPML. The post is in Dutch ('NL'), but the English ('EN') translation is incorrect with several elements or texts missing. Solution: First, ensure that the language switcher is visible on your page. If it's not, this might be part of the issue. Check if the page was created using Elementor, as specific steps are required for translating Elementor pages with WPML. We recommend following these guides:
Additionally, we have enabled debug information for this support ticket. Please follow the instructions here to retrieve this information from your site and share it with us: Provide debug information for faster support.
If this solution does not resolve your 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 you still need assistance, please open a new support ticket at WPML support forum.
Problem: The client is developing a site in three languages (Italian, English, and French) with Italian set as the main language in WPML. However, WordPress recognizes English as the main system language, affecting both the admin and frontend language settings. Solution: We recommend taking a backup of your site first. Then, navigate to Users>>Profile in your WordPress dashboard and set Italian as the language for Language. After this, clear all types of caches to ensure the changes take effect. It's important to note that the frontend language and dashboard language settings are different. For more detailed guidance, please refer to our documentation on setting the WordPress administration language: Setting the WordPress Administration Language.
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 you need further assistance, please do not hesitate to open a new support ticket at WPML Support Forum.
Problem: The client activated WPML Multilingual CMS on their site, but did not complete the setup wizard due to unavailable subdomains. This caused the Elementor Header/Footer to disappear and revert to the Astra default. Additionally, the client encountered an error stating 'You do not have sufficient rights to access' when trying to access the setup wizard. Solution: We reset the capabilities for the client, allowing them to finish the WPML setup. After completing the setup, the Elementor Header/Footer issue was resolved, and the headers and footers returned to normal functionality.
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 our support forum for further assistance.
Problem: You are using the xstore theme and want to translate the 'Description after content' field in WooCommerce categories, but only the 'Description' appears after translation. Solution: The field you are trying to translate is a custom term meta. Here’s what you should do: 1. Navigate to WPML > Settings > Custom Term Meta Translation. 2. Change the translation preference for _et_second_description from 'Don't translate' to 'Translate'. 3. You can now translate this second description while translating your categories in WPML > Taxonomy 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 at WPML support forum.
Problem: You are trying to use the automatic translation feature in WPML for your website, but it fails to continue after initially working. Additionally, the 'fix it' pop-up disappears quickly without resolving the issue. Solution: The issue with the automatic translation not continuing might be due to the first invoice's safety feature that limits your credits. To resolve this, go to Pages and click the title of the page you want to translate as if to edit it. Then, click the cog icon next to the language you are translating to, for example, Spanish. At the top of this page, you should see a message about not having enough translation credits. Click this message, and it will direct you to a page where you can pay the $100 safety limit. After this payment, you should be able to continue translating with more credits. If this solution does not resolve your issue, 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 at WPML support forum for further assistance.
Problem: When attempting to translate a product using WPML, two issues occur: 1) slug translation is not available, and 2) every other attempt results in only code translation being available, not visual. Solution: The issue is identified in the file
. It involves a function that loads translation jobs, which interacts with another process in WPML, causing the problem. A temporary workaround involves commenting out specific lines in the mentioned file to prevent the issue. However, our developers have currently decided not to permanently fix this issue due to past complications with the wpautop function. If more reports arise, they may reconsider.
If this solution does not resolve your issue or seems outdated, 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. We highly recommend opening a new support ticket for further assistance at WPML support forum.
Problem: The client is developing a site and wants to translate country names in product listings using WPML, while also looking to save credits. Solution: Currently, WPML does not support direct import of content for translation that is stored outside of the database. However, we recommend using WPML's translation memory feature, which can automatically translate strings that have been previously translated, thus helping to save credits. We are also actively working on adding functionality to better support your needs.
If this solution does not fully address your issue, 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 further assistance is needed, please open a new support ticket.
Problem: You are currently using GTranslate TDN for translations on your WordPress site and are planning to migrate to WPML. You are concerned about losing translations and potential negative impacts on SEO during the migration. Solution: If you can extract the content from the GTranslate TDN cloud servers, you can import it into WPML using various workflows. We recommend using tools like the native WordPress importer or WP All Import, which are integrated with WPML for importing translations. You can explore these options here: Supported Export and Import Plugins and Tools. For the format of the exports, using CSV, XML, or other formats is suitable, and you do not need to manually map to the database as the import tools handle this process. More details on how WPML handles translations in the database can be found here: WPML Database Tables.
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 was experiencing an issue where the attributes' dropdown in the vendor's panel was not displaying in the correct language (French) consistently, depending on the language setting of the admin panel. Despite updating plugins and previously using a custom snippet code to handle translations, the problem persisted. Solution: We identified that the Litespeed cache was causing the issue, specifically the 'Cache WP Admin' setting. By deactivating this setting, the language display issue in the vendor's panel was resolved. Additionally, it was recommended to clear all cache and transients after deactivating the custom code to ensure that the attributes' dropdown displays 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. If problems persist, please open a new support ticket at WPML support forum for further assistance.
Problem: You are configuring links for your site using WooCommerce/WooCommerce Multilingual & Multicurrency/Shop URL and have translated the slug of the shop, category, and product. However, the product SLUG shows the default language SLUG in every language, despite the settings, while the shop and category SLUGs work correctly in any language. Solution: 1. Go to WPML → String Translation and delete the product slug from the String Translation. 2. Navigate to Settings → Permalinks and resave the page. 3. Return to WPML → String Translation and translate the product slug again. If the issue persists, try deactivating all plugins except WPML, WooCommerce Multilingual, and WooCommerce to check for any conflicts. Additionally, switch between the options
Translatable—only show translated items
and
Translatable—use translation if available or fallback to default language
for Products in WPML → Settings → Post Types Translation to see if it resolves the issue.
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 problems persist, please open a new support ticket at WPML support forum for further assistance.
Problem: If you're trying to translate a page using WPML's translation management and find that the translation option is empty and you cannot translate the selected page or post, this might be due to insufficient WP memory limit or a compatibility issue with other plugins or themes. Solution: First, we recommend increasing the WP memory limit. You can do this by adding the following lines to your wp-config.php file:
Please check with your hosting provider if these settings can be modified on their end. After updating, verify the settings on the WPML >> Support page. Next, ensure all WPML plugins are updated by going to your site's backend > Plugins > Add new > Commercial > click "check for updates". If the problem persists, it might be due to a compatibility issue. Please follow these steps: 1. Create a full website backup. 2. Disable all plugins except for WPML and its add-ons. 3. Check if the issue still occurs. 4. If not, reactivate your plugins one by one to identify the problematic plugin. 5. If the issue persists with only WPML plugins active, switch to a default WordPress theme like TwentySeventeen and check again. It's best to perform these tests in a staging environment if possible.
If these steps do not resolve your issue or if the solution 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 needed, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is unable to find a specific string from the Contact Form 7 plugin to translate it into Spanish using WPML, despite having indexed everything in the plugin. Solution: If you're experiencing this issue, we recommend trying the following methods to locate and translate the missing string: Method 1: Navigate to WPML > String Translation and at the bottom of the page, check the option "Look for strings while pages are rendered." Then, visit the front end of the page where the string is displayed, and return to WPML > String Translation to search for the string. Method 2: If the string is not found in WPML > String Translation, it might be categorized as an admin text string. You can find more details on how to locate and translate admin text strings here: Translate Admin and Settings Strings Additional related documentation can be found here: Finding Strings that Don't Appear on the String Translation Page Please note, if the strings originate from outside of WordPress, WPML will not be able to detect or translate them.
If this solution does not resolve your issue or seems outdated, we highly recommend checking related known issues at WPML 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: You are trying to change the status of WPML from development to live on your site but it still shows 'Development' in the top right corner even after trying to register the live site on your account. Solution: You are currently using a dev/staging WPML key. To resolve this, follow these steps: 1. Visit https://wpml.org/account/sites and generate a new PRODUCTION key. During the creation, you will have the option to choose between a dev key or a production key. 2. Copy the newly generated production key. 3. Go to your site's backend, navigate to Plugins > Add New > Commercial. 4. You may need to first unregister from the old WPML key and then register WPML with the new production key. 5. If you notice any message on the front-end, particularly in the footer area, indicating that "this is a staging/development site", ensure that you also clear the website cache (local/server/CDN caching).
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 further assistance is needed, please open a new support ticket.
Problem: The client is experiencing very slow performance on their website. A PHP X-Ray report identified WPML as the root cause. Despite updating WPML from version 4.6.12 to 4.6.13, the issue persisted. Solution: We discovered that the slow performance was due to specific theme code in
. The problematic code is a function designed to update the focus keyword for all posts of a certain type on every page load. Here is the code:
// Function to automatically update the focus keyword for all: sights<br />function update_focus_keywords_sights()<br />{<br /> $posts = get_posts(array(<br /> 'posts_per_page' => -1,<br /> 'post_type' => 'sights' //replace post with the name of your post type<br /> ));<br /> foreach ($posts as $p) {<br /> update_post_meta($p->ID, 'rank_math_focus_keyword', strtolower(get_the_title($p->ID)));<br /> }<br />}<br />add_action('init', 'update_focus_keywords_sights');
Removing this code reduced the site's load time from approximately 17 seconds to 4.5 seconds. We recommend removing or optimizing this function to improve performance.
If this solution does not apply to your case, or if it seems outdated, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket at WPML support forum.
Problem: The client was unable to see images translated into other languages on their WordPress site, despite following the WPML documentation for media translation.
Solution: We resolved the issue by taking the following steps: 1. Installed and activated the WCML (WooCommerce Multilingual) plugin, which enhances product translations on WooCommerce-based sites. 2. Navigated to WooCommerce -> WooCommerce Multilingual & Multicurrency -> Settings. 3. Scrolled to the "Troubleshooting" link and clicked to load the Troubleshooting page. 4. On the Troubleshooting page, unchecked all options except for "Sync products categories (display type, thumbnail)". 5. Clicked the "Start" button to sync product thumbnails across translations.
Please note that gallery images are not translated by default, but you can sync them using the steps above after translating the categories.
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 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
