Problem: If you're experiencing an issue where ALT tag fields double in the translation editor when adding new images to a post, it might be due to adding an ALT value both in the media library and directly in the image block within the post editor. Solution: We have identified that this behavior is expected and not caused by WPML. When you add an ALT tag directly to an image block, this attribute is saved with the post content rather than in the media library. To avoid translating media library values along with each post, you can navigate to WPML > Settings > Media Translation and disable the last option in this section. This adjustment ensures that only the ALT text added to the block is used, preventing duplication in the translation editor.
If this solution does not apply to your situation, 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: If you're trying to translate strings from 'WooCommerce Subscriptions' and 'All Products for WooCommerce Subscriptions' using WPML and they are not appearing in WPML String Translation, even though they are visible in Loco Translate, this might be due to how strings are registered and rendered, especially when using Gutenberg blocks in themes like Twenty-Twenty Four. Solution: First, ensure you have scanned the plugins through WPML -> Themes and plugins localization. Also, check the Admin Texts section as described in our guide on Finding strings that don't appear on the String Translation page. If the issue persists, it might be related to a known problem with WooCommerce Multilingual cart page strings not being translated when using blocks. You can find the detailed solution on our errata page at WooCommerce Multilingual cart page strings not translated when using blocks.
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.
Problem: If you're experiencing issues with the WPML Translation Editor where clicking on a phrase to translate exits the page and displays a blank screen, this might be due to a cache problem. Solution: We recommend trying to open your site in an incognito tab to see if the issue persists. This approach helped confirm that the problem was related to the cache, as the Translation Editor functioned correctly in incognito mode.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please check the related known issues and verify that you have installed the latest versions of themes and plugins. If the problem continues, we highly recommend opening a new support ticket for further assistance. You can do so here: WPML support forum.
Problem: The client is unable to see the custom translate switcher dropdown in the Elementor header on the front end of their website, although it is visible on the back end. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Ensure that the status of the secondary language pages is set to "Published" and not "Draft". You can check this by going to Pages >> All Pages, switching to the secondary language using the admin language switcher, and confirming the status. If they are set as "Draft", navigate to WPML >> Translations and approve the translations to set them as "Published". More details can be found in this guide: Reviewing Automatic Translations. 2. Resave permalinks from the Settings >> Permalinks page by pressing the Save Changes button. 3. Clear all sorts of cache from your site/server/CDN. If the dropdown still does not appear, please temporarily disable the "Coming Soon" mode to allow further investigation of potential CSS or JavaScript conflicts.
Please note that this solution might be outdated or not applicable to your specific case. 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 the issue persists, please open a new support ticket.
Problem: You are seeing 2164 posts incorrectly identified as imported by the WPML Import and Export plugin, which were not actually imported. This issue persists even after trying recommended troubleshooting steps such as clearing cache, synchronizing posts, and updating plugins. Solution: If you're experiencing this issue, we recommend taking the following steps: 1. Ensure you have a backup of your site for safety. 2. Use a script or SQL queries to delete specific post meta related to WPML import. Here are the SQL commands you can run:
DELETE FROM `wp_postmeta` WHERE `meta_key` = '_wpml_import_language_code';<br />DELETE FROM `wp_postmeta` WHERE `meta_key` = '_wpml_import_source_language_code';<br />DELETE FROM `wp_postmeta` WHERE `meta_key` = '_wpml_import_translation_group';<br />DELETE FROM `wp_postmeta` WHERE `meta_key` = '_wpml_import_after_process_post_status';
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 at WPML support forum.
Problem: You are trying to switch the default language from English to French on your site and encounter a 'Error 404 Page Not Found' when you attempt to switch. Solution: If you're experiencing this issue, we recommend that after switching the default language, you should go to Settings -> Permalinks and resave the permalinks.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, 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. We highly recommend opening a new support ticket if the problem persists. You can do so at WPML support forum.
Problem: The client reported an issue where accessing a URL without a trailing slash redirects to the English version instead of the correct language version, potentially causing SEO problems, duplicate content issues, or confusing users. Solution: We have verified that the redirection to the correct language page with a trailing slash is functioning as expected. This behavior is typical of how WordPress and servers handle redirects and is not specifically related to WPML. If you're experiencing this issue, we recommend checking your server or WordPress settings for URL redirection behaviors. Additionally, ensure that all configurations are correctly set in WPML for handling different language URLs.
If this solution does not resolve your issue or seems outdated, please visit our known issues page at https://wpml.org/known-issues/ to check for any related updates. We also recommend confirming that you have installed the latest versions of themes and plugins. If the problem persists, do not hesitate to open a new support ticket for further assistance at our support forum.
Problem: You are trying to reconnect the automatic credit feature in WPML but find that it is currently not connected. Solution: First, ensure that WPML is properly registered on your site. Follow these steps: 1. Log in to your WPML.org account and navigate to the Sites page. 2. Delete the existing site key, if it exists. 3. Log in to your site, go to the Dashboard >> Plugins >> Add new >> Commercial tab and click the Unregister WPML from this site link if it appears. 4. Click the Register WPML link. 5. Click the Get a key for this site link. This will generate a new key for your site, and you can assign the credits using that popup. 6. Copy the key, paste it back into the input box, and press the Register button. If you need further assistance or if the issue persists, please provide a debug report in the Debug Information box. You can find instructions on how to do this here: Provide Debug Information.
If this solution does not apply to your situation, or if it seems outdated, we 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 help, please open a new support ticket.
Problem: The client wants the language menu to appear only on a specific page, despite setting it up, the language menu appears on all pages. Solution: If you're experiencing this issue, we recommend trying the following steps: 1. Add the following CSS to the custom CSS section of your theme to hide the language switcher on pages other than the specified one:
2. If you are using the Dropdown option from the Language menu items style section and want to disable the Current Language option, switch to the List of languages option instead. You can find this setting under WPML >> Languages > Menu Language Switcher. For more detailed instructions, please visit our documentation: How to display or hide the language switcher on specific pages
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: You are trying to translate field labels and form fields on WooCommerce cart and checkout pages using WPML, but the translated labels are not displaying on the frontend. Solution: If you're experiencing this issue, we recommend taking a backup of your site and applying the workaround provided in our errata. You can find the necessary steps and details here: WPML Errata for WooCommerce Multilingual Cart Page. Additionally, for more information on using WooCommerce shortcodes, please refer to WooCommerce Shortcodes Documentation.
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: The client is experiencing an issue where custom fields are not displaying on the front end of the English version of their website built with Oxygen and Meta Box, using WPML. However, these fields appear correctly when logged in as an administrator. Solution: We recommend setting up a staging environment to safely test without affecting the live site. Follow these steps: 1) Deactivate all plugins and switch to a default theme to check for any conflicts. 2) Examine the Apache configuration for any non-standard changes or extensions, especially in the .htaccess file. 3) Check the server logs for more detailed insights into the issue. 4) Deactivate WPML to see if the issue with the custom fields persists in the default language.
If these steps do not resolve the issue, or if the information provided here becomes 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.
Problem: You are experiencing an issue where switching languages on a WooCommerce product page results in too many redirects. This problem began after updating WooCommerce from version 9.4.3 to 9.5.2. Changing the permalink settings from 'Shop base with category' to 'Shop base' temporarily resolves the issue, but downgrading to WooCommerce 9.4.3 also fixes it. Solution: We have identified this as a known issue with the latest WooCommerce update. While our developers are working on a permanent fix, we recommend two workarounds: 1. Disable the "Auto adjust IDs" setting in WPML > Languages. 2. Insert the following code into your theme's functions.php file:
These steps should help mitigate the problem temporarily. If these solutions do not resolve your issue or if they become irrelevant due to future updates, please check our related known issues and ensure you have 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 was experiencing two issues on a production site using WPML: 1. The main navigation menu was missing on translated static pages. 2. Translated ACF 'Projects' posts were displaying a blank page on the front end. Solution: For the navigation menu issue, we recommended the following steps: - Navigate to Appearance -> Menus. - Translate the menu by following the steps in this guide: Translating Menus Guide. - Translate the string 'Projects' in String Translation. - Go to WPML -> Translation Management, filter by templates, and finish the translation of the header. For the 'Projects' ACF post type issue, the solution involved duplicating and updating the template that displays the projects, ensuring all strings were translated to the target language.
Please note that this solution might be outdated or not applicable to your specific case. 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 the issue persists, please open a new support ticket.
Problem: The client has translated the home page from English to Czech and wants the Czech home page to select the translated Taxonomies. However, they are unable to find the Taxonomies and have tried making them translatable from the WPML settings without success. Solution: If you're experiencing issues with Taxonomies not appearing after translation, we recommend the following steps: 1. Disable all WPML plugins. 2. Click to edit each category term. 3. Re-enable the WPML plugins. 4. On each category edit screen, click save/update. This process should resolve the issue with the translated Taxonomies not appearing on your Czech home page.
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 developing a site and wants to use the same content (products, posts, categories, menus, and static content) across multiple languages without duplicating it. However, when switching languages, the content disappears despite setting it as 'not translatable' in WPML settings. Solution: We explained that setting content as 'not translatable' results in it not appearing in secondary languages. To have the same content appear across different languages without translating it, the content needs to be either shown as translated or duplicated. Duplicating content in WPML is a cloning process that keeps the content in sync across languages, allowing changes in URLs and links while maintaining the original content. We recommend setting the content to 'translatable - Show translated items if they exist or the original otherwise' to achieve this. For further guidance, check the documentation on displaying untranslated content in secondary languages here: https://wpml.org/documentation/translating-your-contents/displaying-untranslated-content-on-pages-in-secondary-languages/.
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. Should you need further assistance, 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
