Problem: After moving the site to a new domain, the client experienced issues with WPML settings and translation mappings. They were unable to select translations on the mapping page, and some Advanced Custom Fields (ACF) were not displaying after changing the language. Solution: We first confirmed the details of the previous domain and ensured that the site was properly migrated without active WPML subscriptions on the old site. We then checked the WPML configuration on the new domain. For the disappearing ACF fields, we noted that translating the Field Groups post type is not recommended as per our documentation, which can be found here: https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/.
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 problems persist, please do not hesitate to open a new support ticket at our support forum.
Problem: The client reported an issue where product links were not directing to their translated versions, causing significant navigation problems on a multilingual site. Solution: 1. We reviewed the client's previous support tickets and internal notes to avoid repeating steps and to understand the issue thoroughly. 2. We requested the client to create a backup and provide new access credentials for secure troubleshooting. 3. After gaining access, we conducted tests and discovered that while full URLs translated correctly in some instances (e.g., on the Spanish versions of the site), there were inconsistencies. 4. Further investigation revealed that the issue was due to a configuration in Rank Math and a mismatch in permalinks that matched one product category slug.
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 do not hesitate to open a new support ticket at WPML support forum.
Problem: When switching from English to Dutch on the website, the cart content is removed despite the 'synchronize cart content' setting being enabled in WooCommerce Multilingual & Multicurrency. Solution: If you're experiencing this issue, we recommend selecting the option Prompt for a confirmation and reset the cart. This setting helps manage the cart contents when changing languages. Additionally, you can display the list of items cleared from the cart by adding a widget we created for this purpose. For more details, please visit Clearing Cart Contents When Language or Currency Change.
Please note that this solution might be outdated or not applicable 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 the issue persists, please open a new support ticket at WPML support forum.
Problem: The client wants to create custom design buttons for the mobile navigation that change the language of the website. Solution: We recommend creating a custom language switcher. You can find detailed instructions on how to do this by visiting Custom Language Switcher. Please note that customization falls outside our standard support offerings.
If this solution does not apply to your situation, or if it seems outdated, we encourage you to open 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 WPML Support Forum.
Problem: You are trying to translate the page 'Find your local offices' using WPML and encounter several issues: 'Unable to retrieve job details' error, 'File Size Limit exceeded' message, and Custom Posts for countries and cities/ports not displaying after translation. Solution: If you're experiencing these issues, we recommend removing the HTML widget that contains the SVG image from your Elementor page. This issue often occurs when the translation job exceeds 1MB of text due to the SVG image in the HTML widget. After removing the widget, save the page and attempt to re-translate it. This should resolve the error messages and display issues with the Custom Posts.
If this solution does not apply to your case, or if it seems outdated, please check the related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If issues persist, we highly recommend opening a new support ticket at WPML support forum for further assistance.
Problem: The client is experiencing an issue where YOAST SEO special pages are displayed in French instead of the native language, Dutch. Solution: If you're encountering this issue, we recommend you follow these steps: 1. Navigate to String Translation. 2. Search for the strings and delete them. 3. Go to Yoast -> Settings. 4. Change the strings to be Dutch. 5. Translate the strings into Dutch.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, 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 are encountering a WordPress database error indicating a deadlock during a transaction. This issue occurred after a recent update and appears when trying to insert values into the
wp_options
table. Solution: We recommend you try clearing your site's cache as a first step to resolve the deadlock issue. If the problem persists after clearing the cache, it might be necessary to further investigate the specific conditions causing the deadlock or to consult with a database expert.
Please note that this solution might be outdated or not applicable 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 the issue continues, please open a new support ticket at WPML support forum for further assistance.
Problem: If you're experiencing issues with ACF fields not displaying when you change the language on your profile page, it might be because the content is created directly inside the theme's template file. This setup can prevent the profile page from being translated using the WPML Translation Editor or the WordPress Editor. Solution: We recommend setting the ACF Field Groups to
Translatable
within WPML > Settings > Post Type Translation. After this adjustment, translate the field group used for the profile page and edit the fields in the translated field group.
Please note that this solution might be outdated or not applicable 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 the issue persists, please open a new support ticket.
Problem: If you're experiencing an issue where your cart is showing multiple entries of the same item from separate purchases, it might seem confusing. Solution: We have tested this scenario on our test site and found that this behavior occurs even without WPML when using the "WooCommerce Product Options" plugin. If you add the same product with different options, such as varying prices, it will create a separate cart entry for each set of options. This indicates that the issue is related to the WooCommerce plugin itself and not WPML.
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 WPML support forum.
Problem: You are trying to translate product reviews on your WooCommerce site and have followed the standard procedure, but you're unable to see all 400 reviews, and old deleted reviews are still visible. Solution: First, ensure you have registered the reviews for translation by following these steps: 1. Navigate to WooCommerce > WooCommerce Multilingual & Multicurrency and select the Status tab. 2. Click the Troubleshooting link at the bottom right corner. 3. In the Troubleshooting tab, check the box next to 'Register product reviews for translation' and click the Start button. 4. Proceed to WPML > String Translation to translate the reviews. If issues persist, our second-tier support can apply a specific SQL query to adjust database tables, which has resolved the issue on a staging site:
ALTER TABLE `rqcv_icl_strings`
CHANGE `language` `language` varchar(7) COLLATE 'utf8mb4_unicode_ci' NOT NULL AFTER `id`,
CHANGE `context` `context` varchar(160) COLLATE 'utf8mb4_unicode_ci' NULL AFTER `language`,
CHANGE `name` `name` varchar(160) COLLATE 'utf8mb4_unicode_ci' NULL AFTER `context`,
CHANGE `value` `value` longtext COLLATE 'utf8mb4_unicode_ci' NOT NULL AFTER `name`,
CHANGE `wrap_tag` `wrap_tag` varchar(16) COLLATE 'utf8mb4_unicode_ci' NOT NULL AFTER `location`,
CHANGE `type` `type` varchar(40) COLLATE 'utf8mb4_unicode_ci' NOT NULL DEFAULT 'LINE' AFTER `wrap_tag`,
CHANGE `title` `title` varchar(160) COLLATE 'utf8mb4_unicode_ci' NULL AFTER `type`,
CHANGE `gettext_context` `gettext_context` text COLLATE 'utf8mb4_unicode_ci' NOT NULL AFTER `status`,
CHANGE `domain_name_context_md5` `domain_name_context_md5` varchar(32) COLLATE 'utf8mb4_unicode_ci' NULL AFTER `gettext_context`,
CHANGE `translation_priority` `translation_priority` varchar(160) COLLATE 'utf8mb4_unicode_ci' NOT NULL AFTER `word_count`,
COLLATE 'utf8mb4_unicode_ci';
Ensure you have a full backup before applying this solution to your production site.
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 need further assistance, please open a new support ticket at WPML support forum.
Problem: You need to automatically translate only the public pages on your site and are unsure how to configure WPML to exclude private pages from automatic translation. Solution: We recommend switching to the "Translate What You Choose" mode in WPML. You can do this by navigating to WPML -> Settings -> Translation mode. Once you have switched modes, you can manually select which pages you want to translate automatically. For detailed instructions on how to send pages for automatic translation, please visit Translating Individual Pages, Posts, and Other Content Automatically.
Please note that this solution might be outdated or not applicable 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 this does not resolve your issue, please open a new support ticket at WPML support forum.
Problem: You are experiencing an 'aggiornamento fallito: undefined' error when attempting to update the WPML, WPML String Translation, and Advanced Custom Fields Multilingual plugins. Solution: We recommend following the steps outlined in the support forum to resolve this issue. Please visit the following link for detailed instructions: https://wpml.org/forums/topic/update-failed-undefined-12/
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 the problem persist, please do not hesitate to open a new support ticket for further assistance. You can do so here: WPML Support Forum.
Problem: The client is experiencing issues with incorrect hreflang tags for languages on their website, specifically with the Norwegian language code, which is incorrectly set as 'nb-nb' instead of the standard 'no'. This issue affects the website's SEO as hreflang tags are crucial for multilingual websites to signal the language and regional URL variations to search engines. Solution: We reviewed the source code of the client's website and identified that all languages except Norwegian were using the correct hreflang tags. The Norwegian language should use the standard 'no' code instead of 'nb-nb'. If the client has created a custom Norwegian language, we recommend switching to the default language settings provided by WPML, as the custom setting conflicts with the standard language codes. To update the language codes in WPML: 1. Navigate to the WPML > Languages page. 2. Under the 'Edit Languages' section, find the incorrect 'nb-nb' entry. 3. Replace 'nb-nb' with 'no' and save the changes.
If this solution does not resolve the issue or seems outdated, or if it does not apply to your specific case, please visit our support forum to open 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.
Problem: If you're experiencing issues where translations disappear and the translated page becomes a duplicate of the original after editing the original page in Beaver Builder, this might be due to a specific setting. Solution: We recommend checking the settings related to the 'duplicate' feature in WPML. Specifically, you might need to adjust how WPML handles translations when the original content is modified. A useful guide can be found here: Using Different Translation Editors for Different Pages.
If this solution does not apply to your case, or if it seems outdated, we highly recommend opening a new support ticket. Also, please check related known issues at https://wpml.org/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 contact us directly at WPML support forum.
Problem: The client was experiencing issues with hreflang tags not pointing to the correct URLs on their multilingual website using the WPML plugin. The hreflang tag for Spanish was incorrect on the English page, and the hreflang tags for English and x-default included the /es/ subdirectory on the Spanish page. Solution: We recommended the following steps to troubleshoot and potentially resolve the hreflang tag issues: 1. Edit the page in English (original language). 2. Make a small change to the content (such as adding or removing a point). 3. Save the changes. 4. Update the translation. 5. Go to Settings -> Permalinks and re-save the permalinks. 6. Flush any cache memory that might exist. 7. Double-check if the issue disappeared. Additionally, we asked the client to temporarily remove the custom rewrite rules for custom post types to see if that resolves the issue. After disabling the custom rewrite, the hreflang tags were generated correctly.
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 issues persist, please open a new support ticket.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
