Problem: If you're experiencing an issue where a newly added language, such as Dutch, is not appearing in the Translation Management menu of the WPML plugin, it might be due to certain settings or configurations. Solution: First, ensure that the language has been correctly added in the WPML Languages menu. If it appears to be added but still doesn't show up in Translation Management, check if you have Object cache enabled. We recommend disabling Object cache temporarily while working with WPML, as it can sometimes prevent changes from being saved properly. After making these adjustments, the new language should display correctly in the Translation Management menu.
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 problems persist, please open a new support ticket.
Problem: You have a custom 'options' page created with Advanced Custom Fields (ACF) and the options are not rendering in other languages when the language is changed. You've set the mode to 'Expert' and chose 'Don't translate' because the contents of the option page don't need to be translated (e.g., phone number). However, when you switch languages, the content is missing. Solution: Currently, the functionality to disable translation for ACF option pages and ensure they render correctly in all languages regardless of the translation settings is not available. This issue has been escalated internally as a feature request. As of now, there are no plans to implement this due to limited demand, but it remains open in our internal tracker for future consideration.
If this solution does not apply to your case, or if it becomes 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 contact us through the WPML support forum.
Problem: You are trying to translate the slug for a custom post type (CPT) called 'book'. The slug should be 'book' for the single template and 'books' for the archive template. You have followed the instructions from the WPML documentation but cannot find the option in WPML settings to translate the archive slug, as the settings only provide a field for the singular slug. Solution: We currently do not support the direct translation of archive slugs for custom post types due to technical limitations. However, we recommend a workaround which you can find detailed in our forum: https://wpml.org/forums/topic/custom-post-type-via-acf-archive-translation/#post-16830228.
If this solution does not apply to your case, or if it seems outdated, please 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, you can contact us directly through our support forum.
Problem: If you're experiencing issues with WPML where translations of posts or products are incorrectly opening in the WordPress editor instead of the WPML Translation Editor, and you receive warnings about potential data loss, we have identified a solution. Solution: First, ensure you create a full backup of your database. Then, perform the following SQL queries via phpMyAdmin:
DELETE pm FROM wp_postmeta pm JOIN wp_posts p ON pm.post_id = p.ID WHERE p.post_type = 'product' AND pm.meta_key = '_wpml_post_translation_editor_native' AND pm.meta_value = 'yes'
DELETE pm FROM wp_postmeta pm JOIN wp_posts p ON pm.post_id = p.ID WHERE p.post_type = 'product' AND pm.meta_key = '_last_translation_edit_mode' AND pm.meta_value = 'native-editor'
UPDATE wp_icl_translate_job JOIN wp_posts ON wp_icl_translate_job.title = wp_posts.post_title SET wp_icl_translate_job.editor = 'wpml' WHERE wp_posts.post_type = 'product' AND wp_icl_translate_job.editor = 'wp'
After running these queries, verify by opening a few product translations at random to confirm that they now load in the WPML Translation Editor.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is experiencing an issue where the English version of the homepage is displayed instead of the Dutch version, despite having translations available for Dutch and French. Solution: We recommend checking and adjusting the settings in WPML > Settings > Custom Field Translation and WPML > Settings > Custom Term Meta Translation. Here are the steps you should follow: 1. If a field needs to be copied to the translation and you use the WPML Translation Editor, set the field to "Copy". 2. If a field needs to be copied to the translation and you use the WordPress Editor, set the field to "Copy once". 3. If the field should appear on the WPML Translation Editor, set it to "Translate". It's important to avoid using "Translate" for fields that should not be translated and ensure not to "Copy" fields that should be ignored. Although the exact field causing the issue is not identified, it is likely related to a field incorrectly set to "Copy" which should have been set to "Ignored".
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 problem persists, please open a new support ticket.
Problem: The client is experiencing an error with the [esi wpml_language_selector_widget] in the Bricks editor for the secondary language, and issues with currency not updating correctly in the cart when using ESI blocks. Solution: For the Bricks editor issue, we recommend wrapping the shortcode in a conditional to differentiate between the Bricks editor and the frontend. Use the following code:
Remember, WPML does not control how LiteSpeed parses or caches ESI blocks, and issues might arise if ESI is not enabled correctly or if the theme or builder does not support ESI context.
If these solutions do not resolve your issues or seem outdated, please check 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 if problems persist.
Problem: The client was experiencing an issue where translated images were not appearing on the product pages of their website after using WPML to translate the products. Solution: We discovered that the issue was due to duplicated image names in both the English and Spanish media libraries. We resolved this by deleting the duplicate images and keeping only the correct ones. After making a small change to the default language product and re-translating it, the images displayed correctly. We recommended the client to check this solution on a staging site and then make a backup of their production website. If the issue persists, we suggested re-translating the products automatically without making any changes, hoping this would resolve the issue.
If this solution does not apply to your case, or if it seems outdated, 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. Should you need further assistance, please open a new support ticket.
Problem: The client was unable to save new thumbnails for product categories when WPML plugins were active. This issue occurred for both default and translated categories. Solution: We recommended the client to disable all WPML plugins temporarily to verify if the issue persists. If the thumbnails are correctly updated and saved with the plugins disabled, this suggests a potential conflict between WPML and the theme or another plugin. In such cases, we advise: 1. Ensure that all themes and plugins are updated to their latest versions. 2. Re-enable the WPML plugins one by one to identify which specific plugin might be causing the conflict. 3. Check the known issues on our website and verify if there's a permanent fix available for the version you are using.
If these steps do not resolve the issue or if the solution provided here is outdated or not applicable to your case, please open a new support ticket. 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.
Problem: The client was experiencing issues with custom image links not redirecting to the correct language-specific pages on their multilingual site using WPML and Elementor. The links were always redirecting to the default language page instead of the intended language-specific pages.
Solution: We advised the client to ensure that the pages are properly linked as translations in WPML to maintain the integrity of the URLs across different languages. Here’s a step-by-step guide on how to achieve this: 1. Edit each translated page in WordPress. 2. In the right sidebar, expand the Language section. 3. Set the correct language for each version if not already set. 4. Click Switch to WordPress Editor and then click Apply in the popup. 5. Click Connect with translations and link the pages across languages. 6. Copy the direct URL of each translated page and use it for the image links in Elementor.
We also recommended using full URLs (including the language prefix) for manual links and double-checking the WPML translation relationships to prevent issues with links not working or being overwritten.
If this solution does not resolve the issue or seems outdated, or if it does not apply 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 do not hesitate to open a new support ticket at WPML support forum.
Problem: You are using WPML with WP-Event Manager Plugin and its Registrations Addon to set a Registration Limit. The site's default language is German, with an English translation. You've encountered an issue where the Registration Limit does not copy for the English translation. After applying a fix from WPML's errata page, it incorrectly combines all different registrations of all events into one in the English translation, causing the registration count to decrease incorrectly.
Solution: We recommend applying a specific workaround from the WPML errata page for the WP-Event Manager Registrations Addon issue with registration limit not being synchronized between languages. You can find the workaround here.
For the code replacements at lines 497 and 595, use the following custom functions:
If this solution does not resolve your issue or seems outdated, 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. If the problem persists, we highly recommend opening a new support ticket for further assistance.
Problem: The client launched their store in two languages using WPML and performed a 301 redirect from a previous domain. Despite being indexed by Google, the site is not visible on google.pl under its proper name 'kavotti'. The client questioned if WPML could be causing the visibility issue on Google and why the site is not visible on google.pl despite being indexed. Solution: We reviewed the client's website configuration and sitemap, confirming that everything appears correct from the WPML side. We recommend that the client double-checks their sitemap for accuracy and initiates a new indexing request through Google Search Console. It's important to note that WPML does not influence Google's ranking decisions or indexing outside of providing multilingual support.
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. If the problem persists, please open a new support ticket.
Problem: You are experiencing an issue where the Dutch homepage of your website is incorrectly redirecting to a product page instead of the expected homepage. Solution: We recommend you try clearing your browser cache as a first step to resolve this issue. If the problem persists, it might be due to a temporary glitch. In such cases, we suggest checking for any specific settings or plugins that might be causing this redirection.
If these steps do not resolve the issue, the solution might be 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 would like to lower the amount of HTTP requests, due to each language flag being loaded as an individual SVG file. This results in multiple HTTP requests, which increase Time To First Byte (TTFB) and initial rendering time, particularly affecting visitors on slower networks.
Solution: We have forwarded a feature request to load SVGs programatically instead of using SVG files, which is currently under revision. You can find a custom solution approach for the issue inside the comments of this ticket.
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 at WPML support forum.
Problem: When WPML is enabled, previously uploaded images are not visible in the media library and are replaced by random images in posts. This issue does not occur when WPML is disabled. The problem affects specific posts created on August 23 and involves around 313 images. Solution: 1. Disable WPML and delete the old 313 images that are affected and possibly corrupted. 2. Re-enable WPML and upload new images. 3. Manually set these new images to the respective posts. 4. If the default language image still appears incorrect, upload the correct images again in the default language, ensuring they are properly set. 5. Optionally, translate the post into German (DE) if needed, using the WPML Media Addon to ensure images display correctly when WPML is enabled.
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 is experiencing an issue where Swedish product category URLs on their WooCommerce site are incorrectly using the English category base '/collections/' instead of the Swedish '/product-category/' base after updating the WooCommerce Shop page. This resulted in 404 errors for Swedish URLs while English URLs under '/en/collections/' were unaffected. Solution: We recommended that the client updates their WPML Multilingual CMS to the latest version along with all its add-ons, particularly WPML Multilingual & Multicurrency for WooCommerce, and also update WooCommerce itself. This can be done via the WPML admin panel by navigating to wp-admin/plugin-install.php?tab=commercial, clicking on "Check for updates", and following the update prompts. After updating, the client should remove any .htaccess workarounds, resave permalinks, and clear the site cache to see if the issue persists.
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. If the problem continues, please open a new support ticket at 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
