Problem: The client is using Stripe to accept payments and has their store set up in USD. They need to use EUR to activate payment methods like Klarna. Although customers can switch to EUR, the client cannot accept payments using EUR with Stripe and Klarna because Klarna requires the store to be listed in EUR. Solution: We recommend setting the default currency of the store to EUR and the secondary currency to USD. This adjustment is necessary because Klarna requires EUR as the default currency to function properly. If you're experiencing this issue, we suggest making this change to enable Klarna payments through Stripe.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If further assistance is needed, we highly recommend opening a new support ticket with us here.
Problem: The client was setting up different domains for each language on their site using WPML but encountered issues where the different domain per language setup was not working. Solution: First, we recommended resaving the WPML>>Languages>>Language URL format settings and the Settings>>Permalinks. The client was also advised to clear all types of caches to see if the issue was resolved. Additionally, to verify the DNS settings, we suggested uploading a text file named WPMLTest.txt to the main domain's root directory and checking its accessibility from all the intended domains.WPML_LS_Menu_ItemUpon further investigation, it was discovered that the subdomain was not set to the actual document root (/public_html). Correcting this setting resolved the issue.
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: You are experiencing issues where you are asked to translate from French to French instead of from English to French. Additionally, you notice duplicate translations of image text in the translation editor. Solution: 1. If you are not using the Media Translation plugin, we recommend removing it from your plugins list. This action might require cleaning the media translations from the database. 2. Alternatively, disable the Media Text translation in the Advanced Translation Editor (ATE) and use Media Translation only for necessary cases. 3. To remove duplicate translations, follow these steps: - Search for the English title of the image in the Media Library. - Identify duplicates of the same image. - Keep the Media Library tab open, and open the concerned page with Elementor to check the date and file name of the image currently in use. - Return to the Media Library and delete all files that do not match the details on Elementor. - Make a small edit to the page, save, and update the translation.
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 is experiencing an issue where filters that appear in one language do not appear in the other language on their website. Solution: We recommend checking the compatibility and configuration of the Filter Everything PRO plugin with WPML. Although Filter Everything PRO has not been officially tested by our team, their team claims compatibility with WPML. Please review the following documentation to ensure everything is configured properly:
If after following these steps, the filters still do not appear correctly in both languages, the solution might be outdated or not applicable to your specific case. 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. If the issue persists, please open a new support ticket.
Problem: If you're experiencing issues where related posts in the API still appear in the original language despite having translations, and your code works locally but not on the live site. Solution: We recommend you follow these steps: 1. Navigate to WPML-> Languages. 2. Select 'Different languages in directories' in the Language URL Format section. 3. Save your changes. 4. Resave the permalinks. 5. Check the translated endpoint with '/en/'.
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 trying to translate the cart and mini cart on your website, but the changes do not appear on the live site despite the strings being translated. Solution: Manually edit the translated checkout page and translate the strings. Alternatively, you can edit the checkout page in the default language, replace the checkout block with the classic checkout, update it, and then update its 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 https://wpml.org/forums/.
Problem: The client is experiencing incorrect image text translations within the WPML editor. Solution: We identified a possible cause related to media files with similar filenames. For more details, see the errata page: Media Translation Issue with Images Having Similar Filenames. We applied a workaround by navigating to WPML > Settings > Media Translation > How to handle media library texts and disabling the option 'Translate media library texts with posts'. We then initiated a re-sync of the media library by clicking the 'Start' button. We recommend testing this solution on your staging site to confirm if the issue is resolved.
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 ensure you have installed the latest versions of themes and plugins. If the problem persists, we encourage you to open a new support ticket at WPML Support Forum for further assistance.
Problem: You are trying to move products from one domain to another using WPML and the WebToffee plugin. When opening an Excel file, the Armenian translation has an issue with utf-8 encoding.
Solution: We have identified that the issue arises because the free version of the "Product Import Export for WooCommerce" plugin does not support multilingual features fully. To resolve this, you need to upgrade to the premium version of the plugin. This version supports multilingual capabilities when used with WPML.
For more information on the plugin and its features, please visit:
If upgrading does not resolve the issue, or if this solution seems outdated or irrelevant to your case, 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. Additionally, feel free to open a new support ticket for further assistance at WPML Support Forum.
Problem: The client needed to translate 'updated on' and 'written by' in every blog post on their website.
Solution: We recommended the following steps to translate these elements: 1. Go to edit the element in the default language. 2. From the sidebar, in the Language section, under the Translations subsection, select WordPress Editor. 3. Click the + sign to add a translation (or the pencil to edit an existing translation). 4. If adding for the first time, select 'Copy content from English' to copy all content already designed in the default language. 5. If you prefer not to copy, you can design a new version (even using an entirely different design for the translated version). 6. When adding your element, for example, a 'Headline' block in this case to show the date or 'written by', remember to use translated text for the labels. 7. Save and publish the translated version. For more detailed information, you may check this guide: Using different translation editors for different pages.
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. Should you need further assistance, please open a new support ticket at WPML support forum.
Problem: The client reported a recurring 404 error due to the automatic modification of the .htaccess file by the WPML plugin, which incorrectly rewrites rules based on the language of the site, causing navigation issues. Solution: We identified this as a known issue not directly caused by WPML but related to its interaction with .htaccess configurations. We recommend following the workaround detailed in our FAQ to prevent .htaccess from being overwritten when the language changes. You can find the step-by-step guide here: https://wpml.org/faq/why-is-htaccess-getting-overwritten-with-the-language-folder-on-my-wpml-website/
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 encourage you to open a new support ticket for further assistance.
Problem: The client created a staging site using WPVivid and noticed that the translation settings for Forum/Topic/Reply defaulted to not translatable. They were curious why this happened and how to ensure these settings are retained during staging setups. Solution: We suspect that something might have gone wrong during the migration process, which should not normally occur if everything was correctly migrated. To avoid such issues in the future, we recommend using the Duplicator plugin for migrating your site. This plugin should handle the URL-replacing process effectively and migrate all data without issues. You can find the Duplicator plugin here: https://wordpress.org/plugins/duplicator/ For detailed documentation on how to use the Duplicator plugin, visit: https://snapcreek.com/duplicator/docs/ Here is a tutorial on how to use the Duplicator plugin: https://www.youtube.com/watch?v=3YDQ3Ey_2wY After migration, remember to register WPML on your new site and enter the new key. You can manage your sites and keys by logging into your WPML account and navigating to the "Sites" page at https://wpml.org/account/sites/
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 for further assistance.
Problem: If you're experiencing issues with translating custom block contents despite having wrapped them in localization tags, it might be because these are JavaScript strings. Solution: We recommend following our guide on adding gettext calls to JavaScript code, which you can find here: Translating JavaScript strings in WPML. However, be aware of a known issue where WPML might not currently translate JavaScript strings effectively. You can learn more about this problem here: Translating strings from JavaScript files issue. Additionally, strings like "Choose file" and "No file chosen" are dependent on the browser's language setting and may not be influenced by WPML.
If this solution does not apply to your case, or if it 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 issues persist, please open a new support ticket.
Problem: The client is experiencing issues with the Advanced Translation Editor (ATE) in WPML, where clicking 'COMPLETE TRANSLATION' redirects to WordPress but does not finalize the translation. This issue does not occur with the Classic Translation Editor, which works as expected. Solution: We recommend the following steps to resolve the issue: 1. Edit the primary language page using the backend editor. 2. Proceed to edit the translations and attempt to complete the translation again. 3. If the issue persists, install a specific plugin from this link and update the ATE ID with the provided credentials.
4. Additionally, go to 'Troubleshooting' in WPML and click on 'Refresh License Data'.
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 the problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: The client's development site lost contact with WPML after detecting a new link and could not reconnect to the WPML account. The site was unable to continue without declaring it a copy due to a change in the IP address being recognized as the main link. Solution: We identified two separate entries for the client's URL in our system, each with different credit amounts. We merged these entries, consolidating the credits into a single account. This action restored the connection to WPML, allowing the client to see a total of 48,330 credits available. If you're experiencing similar issues with your development site losing contact with WPML or issues related to credit allocation, we recommend checking your account for multiple entries and contacting us for consolidation.
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 at WPML support forum.
Problem: The client needed to implement a custom language switcher in their header, similar to the one on the WPML site, featuring a single flag that displays other languages on hover. The default WPML language switcher was too wide and did not meet their design requirements. Solution: First, we advised the client to adjust the settings in WPML -> Languages -> Custom Language Switcher by selecting 'Dropdown' from the Language Switcher Style and unchecking the 'Native Language Name' and 'Language Name In The Current Language' options. For further customization, we provided a CSS snippet:
If this solution does not apply to your case, or if it becomes 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. Should you need further assistance, please open a new support ticket or consider contacting one of our certified partners at https://wpml.org/contractors/.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
