Problem: If you're experiencing issues with the message 'This site is registered on wpml.org as a development site. Switch to a production site key to remove this banner' after migrating your site to a new domain, we can help you resolve this. Solution: First, visit WPML.org > Account > Sites and remove the old key (dev key) that you were using on the other domain. Then, generate a new key for the new domain (production key) and select the appropriate site type during this process. Next, go to your website's backend, navigate to Plugins > Add New > Commercial, and register WPML with the new key. You might need to click "Unregister" first if the old key is still active. If you still see the notice after these steps, it could be due to caching on your site or server/CDN. Please contact your hosting support to clear the server cache and ensure you clear any site cache through any caching plugin installed on your 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 issues persist, please open a new support ticket.
Problem: You received an email indicating a medium severity problem with the WPML SEO plugin, suggesting that the plugin appears to be abandoned as it was last updated on 5 September 2022 and tested up to WP 6.6.1. You are concerned about the implications for your site and receive frequent notifications about this issue. Solution: If you're experiencing similar notifications, we recommend not to worry as these messages are generally false positives. The WPML SEO plugin is not abandoned. We are planning to release an update soon which should resolve these notifications. This update will ensure compatibility with the latest WordPress versions and address the concerns raised by security plugins like WordFence.
Please note that this solution might be irrelevant if it's 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 for further assistance.
Problem: The client was unable to see the updated logos for different languages on their website, despite having added the French and Romanian versions in WPML Media Translation. The logos were not updating on the front-end of the website. Solution: We identified that the issue was because the logo is not part of the WordPress content but is managed through the theme functions. We searched for the URL of the English logo under WPML > String Translation. We found four instances of the URL and added the French and Romanian URLs as translations for these instances. After this adjustment, the logos displayed correctly in the respective languages.
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 do not hesitate to open a new support ticket at WPML support forum.
Problem: You are experiencing issues with automatic translations not working when using WPML AI on your site. Additionally, the options to use Google or DeepL for translations are not appearing. Solution: We have resolved the issue from our server side, ensuring that WPML AI should now function correctly for automatic translations in English and German. To activate Google and DeepL translation options in WPML, please ensure that these services are correctly configured in your WPML translation management settings. If you continue to face difficulties or find that the solution is outdated or not applicable to your case, we recommend opening a new support ticket. We also advise 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 https://wpml.org/forums/forum/english-support/.
Problem: The client is unsure about the 2000 Complementary credits that appeared in their account upon linking a new website. They are concerned about how these credits are used, whether they are added automatically, and if they will incur any additional charges. Solution: If you're seeing Complementary credits in your account after linking a new website, we can confirm that these credits are added automatically to give you a start with the automatic translation process. You will not be charged for these credits; they are provided at no cost to assist you.
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 do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is unable to translate the content of an entry using WPML, although they can translate the title. Solution: We reviewed the client's post and confirmed that the content is visible in the editor. We recommend the client to verify if they can see the content in their editor as well. If the content is still not visible or translatable, it might be due to a configuration issue or a compatibility problem with the theme or another plugin.
Please ensure that you have the latest versions of WPML and any other installed themes and plugins. You can also check for any known issues that might be affecting content translation at https://wpml.org/known-issues/. If the problem persists, we suggest opening a new support ticket for further assistance.
Problem: If you're trying to create a manual order in a different language than the default and find that no products can be added when you change the order language, this is because products for manual adding are only found in the default language.
Solution: We recommend the following steps as a temporary workaround: 1. Navigate to WooCommerce -> Orders. 2. Switch to the secondary language from the top admin bar (the language in which you want to create an order). 3. Click the "Add Order" button. 4. Before entering any product or other details, scroll down to the "Custom Fields" section. 5. Select the "wpml_language" custom field and set it to the value of the currently selected language code (e.g., 'de' for German). 6. Add this custom field. 7. Save the order. 8. After reloading the page, confirm that it has been added as expected. 9. You can now add the product, and while searching, find the translated products in that language, provided that the products have already been translated.
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 at WPML support forum.
Problem: The client is trying to customize the language switcher to use an icon and display languages below the icon but is unable to add the image/icon in CSS. Solution: We recommend using the CSS background property to display the icon in the language switcher. Here is an example of CSS that can be used:
If this solution does not resolve your issue, please provide a debug report in the Debug Information box. You can find instructions on how to do this here: Provide Debug Information for Faster Support.
If the solution provided here is not relevant 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 issues persist, please open a new support ticket at WPML Support Forum.
Problem: You are trying to add translations to an Elementor template, which previously existed but now are missing. Although the editor shows them as 100% translated, they disappear after saving. Additionally, you encounter a fatal error when attempting to add translations through the WordPress editor, specifically a TypeError related to the
in_array()
function. Solution: We recommend the following steps to resolve the issue: 1. Access your database. 2. Navigate to the
wp_options
table. 3. Delete the option that might be causing the issue. This step is crucial as it seems related to the fatal error you are experiencing. For more detailed guidance, you can refer to a similar issue discussed in our forum: WPML forum topic on fatal error when adding a translation.
Please note that this solution might be outdated or not applicable to your specific case. If the problem persists, 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 necessary, do not hesitate to open a new support ticket for further assistance.
Problem: If you're experiencing issues where the translated version of your page does not match the front-end display, showing an old template homepage with outdated themes and texts, despite correct strings in both Italian and English in the editor. Solution: We recommend duplicating the page from the primary language and translating it again. After this, edit the translated version with your page builder and save it. This approach resolved similar issues related to icons and styling. Additionally, ensure that your WordPress memory is sufficient, as insufficient memory can prevent page options from being saved correctly in translations. You can check and address WordPress memory issues here: WordPress Memory Issue.
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 with us for further assistance.
Problem: The client is experiencing issues with both automatic and manual translations not working on their WordPress site after installing the WPML plugin. They have completed translations on a staging site and are now looking to apply these to the live site without purchasing additional credits. Solution: First, ensure that the WPML plugin is properly installed and activated on your live site. You can follow the installation guide here: WPML Installation Guide. Next, to transfer completed translations from the staging to the live site, use the WPML's Translation Management tools. Detailed steps can be found here: Translating Your Content. Regarding the WPML license for the live site, you do not need to purchase additional credits if you have already done so for the staging site. Simply log in to your WPML account and follow the instructions to activate the license on your live site.
If these steps do not resolve your issues or if the information provided 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 you still face problems, please open a new support ticket.
Problem: If you're trying to translate a global element created with Bricks Builder and are encountering issues where the translation does not appear correctly on the frontend.
Solution: We recommend following these steps: 1. Apply the fix from the WPML errata page for Bricks Builder issues. You can find it here: Bricks translated content not showing on frontend. 2. Edit the home page in the default language using Bricks Builder and make necessary text changes. 3. Save your changes and exit to WordPress. 4. Update the translations in the Advanced Translation Editor (ATE), ensuring all text is present and translated. 5. If some elements still don't display correctly, go to WPML -> String Translation. Search for the strings that are not showing correctly, correct their language if necessary, and translate them. For guidance on changing the language of a string, visit: How to change the source language of strings. 6. Note that if you are using plugins like 'Max Addons for Bricks' which are not compatible with WPML, you might need to manually translate some elements using the WP Editor. For more information on using different translation editors, see: Using different translation editors for different pages.
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 experiencing a fatal error on the cart page and other pages when WPML String Translation is activated in the Arabic version. Solution: We have removed the incorrect string translations which resolved the issue. Please check if the error persists. Additionally, we recommend reviewing the related known issue documented here: PHP 8 PHP Fatal Error Uncaught ValueError: Unknown format specifier in.
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 through the WPML support forum.
Problem: The client reported an issue where a product displayed a different sale price on the English version of their site compared to the German version. Despite resetting the price, the changes only applied to the German version, and the English price remained incorrect. Solution: We discovered that a specific plugin adding a Pre-Order tab was causing the discrepancy. The English product was set to "Set a fixed pre-order price" with an incorrect amount. We changed this setting to "Use the selling price" and updated the product, which resolved the issue. It was not a WPML issue.
If this solution does not resolve your issue, 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 the problem persists, please open a new support ticket.
Problem: You have added a fifth language, Hindi, to your multilingual website, but the language icon is not displaying in the menu. Solution: 1. Ensure that the page you are viewing on the frontend is translated into Hindi. 2. Verify that the status of the Hindi language pages is set as 'Published' and not 'Draft'. 3. Confirm that the Hindi language is not hidden on the WPML >> Languages page. If these steps do not resolve the issue, please add a debug report in the Debug Information box. We have enabled the debug info box for your next reply: https://wpml.org/faq/provide-debug-information-faster-support/
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. Additionally, 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.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
