Problem: The client is using the 'WooCommerce Product Tabs' plugin and is unable to find the new string for product tab titles in WPML > String Translation. Additionally, many 'WooCommerce Product Tabs' strings are marked as 'pending with the hourglass' and are not appearing elsewhere. Solution: We recommend following these steps to resolve the issue: 1- Go to Products -> Product Tabs and access the trash (or click the link to your trash directory). 2- Delete the French product tabs. 3- Open the file .../wp-content/plugins/woocommerce-product-tabs/src/Product_Tabs.php. 4- Locate line 60 and replace the code:
5- Go to WPML > String Translation, enable the option 'look for strings while pages are rendered' at the bottom of the page, and visit a product with the tabs so WPML includes the new strings. 6- Go to WPML > String Translation, search for the tabs titles, and translate them.
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 the problem persists, please open a new support ticket.
Problem: You are trying to update the WPML plugin, but the WordPress updater shows an error message that the zip file is corrupt. Additionally, when attempting to download the plugin manually from your account, you receive an HTML file stating 'Error: you are not allowed to download this file'. Solution: 1. Temporarily remove your website here: https://wpml.org/account/sites/. This action won't affect your translation credits or translation memory but will force WPML to refresh the license status. 2. Add your website again and copy the newly generated key. Ensure you use the exact same format as shown in your wp-admin under Settings > General (e.g., http or https, www or non-www). 3. Navigate to Plugins -> Add New -> Commercial in your WordPress dashboard. 4. If visible, click on 'Unregister WPML'. 5. Click on 'Register WPML' and enter the new key. 6. Click on the 'Check for updates' button in the WPML section. 7. Select every plugin marked in red and click on 'Download' at the bottom of the grid. If these steps do not resolve the issue, our Systems can investigate to see if there could be an internal issue. If the solution provided here becomes irrelevant due to updates or does not apply 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. Should you need further assistance, please open a new support ticket at WPML support forum.
Problem: The client is experiencing an issue where unrelated SEO meta fields are appearing in the Advanced Translation Editor (ATE) when translating Elementor Templates. This happens specifically when a template is created from a section within a page or post, where SEO meta fields are included. Solution: 1. If you're experiencing this issue, first check if the SEO meta fields are necessary for your translation. If they are not, you can set them to 'Don't Translate' by following these steps: - Go to WPML > Settings and scroll to the Custom Field Translation section. - Click on Show System Fields. - Search for 'seopress' in the search box. - Set the translation preference for the fields you don’t want to see in the Translation Editor to 'Don’t Translate' and save the changes. 2. If the fields are appearing because they were included in a template created from a page or post, you can remove them directly in the Elementor editor before translating. For guidance on removing these fields, please refer to this guide.
If the solution provided here does not resolve your issue or seems irrelevant due to updates or differences in 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.
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 our support forum.
Problem: The client needs to set a transparent or semi-transparent background color for the language switcher button in WPML but found no documentation on how to achieve this. Solution: We recommend applying custom CSS to achieve the desired transparency effect. Here is the CSS code you can use:
Please test the changes on a staging site before applying them to your live site. If you need further assistance, consider hiring a professional from our contractors' page.
This 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 this does not resolve your issue, please open a new support ticket.
Problem: You are unable to save a new or update an existing post in WordPress when it includes emojis, receiving an error message: 'Updating failed.'
Solution: This issue might be due to a known bug in WordPress that affects saving strings with emojis when using WPML. To resolve this, follow these steps: 1. Ensure you have a complete backup of your database. 2. Check the collation of the columns in the
wp_icl_strings
table in your database. All columns should have the same collation, preferably
utf8mb4
. 3. If you're not comfortable making these changes, contact your hosting provider or developer for assistance.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, we recommend opening a new support ticket. Additionally, check the related known issues and ensure you have the latest versions of themes and plugins installed. For further assistance, please visit our support forum.
Problem: You are trying to set 'Set prices in other currencies manually' as the default choice on the product page for variations, but the WooCommerce Multilingual plugin defaults to 'Calculate prices in other currencies automatically', causing manually set prices to be ignored. Solution: Since there is no central feature in the WooCommerce Multilingual plugin to switch to the manual price option for variations, you need to use custom coding. Add the following code to the functions.php file of your theme to set 'Set prices in other currencies manually' as the default for new product variations:
function set_default_manual_currency_pricing($post_id) {<br /> if (get_post_type($post_id) === 'product_variation') {<br /> update_post_meta($post_id, '_wcml_custom_prices_status', '1');<br /> }<br />}<br />add_action('save_post', 'set_default_manual_currency_pricing', 20, 1);
To apply this change to existing product variations, add this code, run it once, and then remove or comment it out:
If you need further assistance with custom coding, consider hiring a professional developer. You can find one experienced in customizing WPML and its add-ons at https://wpml.org/contractors/.
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 this does not resolve your issue, please open a new support ticket.
Problem: You are using the Timeline Block For Gutenberg to present timelines on your site. When translating the page, everything including dates can be translated, but the dates still appear in French on the English page. This issue arises because the date is not from the core blocks and is not supported for string translation. Solution: We recommend using a custom XML configuration code to register the date for translation. After translating, the date should display correctly in the frontend. Here is an example code:
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 our support forum.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client has translated all identified strings using the Translation Editor on an Elementor page, but only a few words are displayed as translated, with about 90% not reflecting the changes. Solution: We suggested checking if there are global templates in Elementor that might not be visible in the Translation Editor and need translating separately. Additionally, we identified that the theme used ('Tastyc') is not officially compatible with WPML. We recommended contacting the theme developers to encourage them to join our Go Global program. As a workaround, we advised the client to: 1. Edit the page in the default language. 2. Switch to the secondary language using the language switcher. 3. Edit with Elementor and manually adjust translations directly in Elementor.
If this solution does not resolve the issue or seems outdated, please check our related known issues and ensure you have the latest versions of themes and plugins. If problems persist, we highly recommend opening a new support ticket here.
Problem: The client finds the media translation settings in WPML confusing and wants to use the same images across different translations without duplicating them. Solution: If you're experiencing confusion with WPML's media translation settings and wish to use the same images across various translations, we recommend keeping the current settings unchanged. When you translate your pages or posts, the media will not be physically duplicated on your server. Instead, an additional database entry will be created, linking the translation to the same image as the original. We suggest testing this setup on a few pages with images to see how it functions.
Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking for related 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 unable to translate specific text appearing on your website. Solution: We recommend following these steps to ensure the text is properly registered for translation: 1. Navigate to WPML → String Translation. 2. Enable the Look for strings while pages are rendered option. 3. Visit the page where the untranslated text appears. 4. Return to WPML → String Translation and verify if the new text has been registered. 5. Proceed to translate the newly registered text. For more detailed guidance, please refer to our documentation on Finding Strings that Don’t Appear on the String Translation Page.
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. Additionally, you can open a new support ticket for further assistance at WPML support forum.
Problem: You are experiencing inconsistent translations and sometimes missing text blocks when translating product descriptions using WPML String Translation. Solution: We recommend not using WPML → String Translation for translating product descriptions directly. Instead, navigate to WooCommerce → WooCommerce Multilingual & Multicurrency, and click on the translation icon. This will open the translation editor, where you can make translations directly in the editor.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, 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: You are trying to change the Japanese URL on your website to https://navagis.com/jp/. Solution: Modifying an existing language code is impossible, but you can create a custom language and specify the code as /jp/ For detailed instructions on how to add a custom language, please visit Editing WPML's Languages Table.
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 at WPML support forum.
Problem: The client needs the ES menu links to point to the corresponding WPML-translated ES pages, but they are pointing to the EN pages instead. This issue is occurring in the ES Footer menu, and changes in the ES theme Appearance > Editor affect the EN pattern as well. The client wants to fix this issue and learn how to prevent it in the future. Solution: 1. Delete the existing header and footer navigation menus and templates. 2. Create new navigation menus and templates in the primary language. 3. Use WPML Translation Management to create second language instances of these menus and templates. 4. Switch to the second language in the WP Admin console. 5. Open the second language instances of each element via Appearance > Editor > Template etc. 6. Remove each page link from the second language navigation menu, and replace it with a link to the corresponding page in the second language. This process ensures that both the primary and second language navigation menus have the correct labels and page links. Additionally, ensure you have translated your Menu template from WPML > Translation Management.
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.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
