Problem: The client was experiencing an error message indicating an undefined property related to WooCommerce and PayPal payment gateways.
Solution: 1. We acknowledged the issue and confirmed that our development team was able to reproduce it. The problem was specifically occurring when using the "WooCommerce Checkout Add-Ons" plugin alongside the PayPal plugin. 2. We informed the client that an Errata had been published for this issue, which can be found here: https://wpml.org/errata/woocommerce-checkout-add-ons-and-woocommerce-paypal-payments-fees-not-added-to-paypal-in-multicurrency-setup/ 3. We released an update for WooCommerce Multilingual (version 5.3.5) that should resolve the issue. We advised the client to update the plugin to the latest version. If the update was not visible in the Plugin dashboard, we provided instructions to download the latest version from the WPML account downloads page: https://wpml.org/account/downloads/
Please note that the solution provided might be irrelevant if it's outdated or not applicable to your case. If the issue persists after trying the recommended steps, 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 need further assistance, please open a new support ticket at our support forum.
Problem:
The client cannot find the term "Delivery" to translate it in WPML > String Translation. Solution:
1. We recommend enabling the “Look for strings while pages are rendered” option in WPML > String Translation, then visiting the page where the term appears and returning to WPML > String Translation to search for the term.
2. If the term still does not appear, it may be added as administrative text. Follow the normal process for finding and translating admin text strings here: https://wpml.org/documentation/getting-started-guide/string-translation/finding-strings-that-dont-appear-on-the -string-translation-page/
If the proposed solution does not solve your problem or if it seems outdated, we invite you to open a new support ticket. We also recommend that you review known issues at https://wpml.org/known-issues/ a>, to check the version of the permanent fix and to confirm that you have installed the latest versions of the themes and plugins. For further assistance, please contact our support forum: https://wpml.org/ fr/forums/forum/assistance-en-francais/.
Issue: The customer tries to switch from a development site to a production site, but continues to see a message saying that the switch is not happening, even though the new URL has been registered. < strong>Solution: If you have this problem, it may be due to an existing cache on the website or on the server/CDN even after you changed the key correctly. To To clear server cache, you should contact hosting support. To clear website cache, make sure to remove it from any existing caching plugin that may be installed on the website.
This solution may be irrelevant because it is outdated or does not apply to your problem. If this is the case, we recommend that you open a new support ticket. We also recommend that you check the known issues page to verify the permanent fix version and to confirm that you have the latest versions of themes and plugins installed.
If you need further assistance, please do not hesitate to contact us at WPML support forum.
Problem: The client is seeking a way to automatically translate updated content on their English page without overwriting previous manual edits made to automatic translations.
Solution: 1. We recommend reviewing the documentation on Translation Memory to understand how WPML tracks translations. Content edited in the Advanced Translation Editor (ATE) can be saved to Translation Memory, ensuring it won't be translated again unless the original content changes. However, changes made using the WordPress Editor instead of the WPML editor will not be stored in Translation Memory and will be overwritten by automatic translation. Translation Memory documentation.
2. If the client has manually corrected the content in the ATE and clicked "Complete", the edits are saved to the Translation Memory. There is no need to click "Save to translation memory" separately.
3. To avoid overwriting manual edits, it's best to make changes or edits to the automatic translation directly in the ATE, as these will then be saved in the Translation Memory for future use.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If so, we encourage you to 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. If you need further assistance, please contact us in the WPML support forum.
Problem: The client is trying to renew the license for the WPML plugin but is unsure where to enter the username and password. Solution: We informed the client that the WPML subscription was purchased on 21st February 2024. To renew the license, the client should generate the WPML key from the following link: https://wpml.org/account/sites. After obtaining the key, the client should navigate to the WordPress backend, go to
Plugins > Add New > Commercial
, and register WPML using the generated key.
If this solution does not apply because it is outdated or not relevant to your case, 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.
If further assistance is needed, please contact us on the WPML support forum.
Problem: The client has a Contact Form 7 form translated into 3 languages. The form submissions are being received when the form is filled out in the original language, but not when filled out in the translated languages.
Solution: We recommend adding a custom XML configuration to ensure that the email recipient field is translatable. This can be done by going to WPML > Settings > Custom XML Configuration and adding the following code:
After adding the custom XML, make a change in the original form and then translate it. For more information on using XML configurations with WPML, please refer to our documentation:
Please note that this solution might be outdated or not applicable to your case. If it doesn't resolve your issue, 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. If you still need assistance, please do not hesitate to open a new support ticket. You can reach our support forum here: WPML support forum.
Problem: The client was unable to display a translated version of the global footer created in DIVI Builder when switching languages on their website. The footer remained in German regardless of the language selected.
Solution: 1. We accessed the Divi >> Theme Builder page. 2. We edited the Global Footer to check its name. 3. We navigated to WPML >> Translation Management and discovered that the correct footer template was not fully translated. 4. We completed the translation and verified that the correct translation now appears on the frontend.
If you're experiencing a similar issue, we recommend you: - Check the name of your global footer in the Divi >> Theme Builder. - Ensure that the footer template is fully translated in WPML >> Translation Management.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, 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 you still need help, please open a new support ticket.
Problema: A) Os preços dos hotéis não aparecem na seção "Recomendado para você" nas versões em francês e português do site, mas aparecem na versão em inglês e na página 2 da seção. B) O conteúdo vinculado a "Logement" não aparece na versão em francês do site, embora esteja disponível e apareça nas versões em inglês e português. Solução: Já existe um ticket aberto para este problema. Continuaremos o suporte por lá.
Se você estiver enfrentando um problema semelhante, recomendamos verificar os problemas conhecidos relacionados, verificar a versão da correção permanente e confirmar que você instalou as versões mais recentes de temas e plugins. Se a solução fornecida aqui for irrelevante para o seu caso, seja porque está desatualizada ou porque não se aplica à sua situação, sugerimos que abra um novo ticket de suporte.
Problem: The client purchased 200,000 prepaid credits for automatic translation but their account still displayed 0 credits. Solution: It was an internal issue. We credited the client's account with the purchased amount. The client should now be able to see their prepaid credits.
If you're experiencing a similar issue, we recommend checking your WPML account to confirm that the credits have been properly applied. If the problem persists, please do not hesitate to open a new support ticket. We also 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 is experiencing issues with links not correctly translating to the appropriate language versions on their multilingual site. Some links in languages other than German revert to the German version. The client has attempted to fix this using the advanced translation editor but was unable to find the links there. Solution: We noticed that the client's website does not meet the minimum memory requirements for WPML to function properly. We recommend increasing the WordPress memory limit to at least 128MB, with 256MB being preferable. To do this, add the following code to the
Please note that this solution might be outdated or not applicable to your 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 you still need assistance, please open a new support ticket at our support forum.
Problem: An end-user client migrated their website to a new hosting provider and encountered issues with WPML plugin registration, receiving messages about using an unregistered version and being unable to connect to wpml.org. Despite whitelisting IPs as suggested, the problem persisted. Take note that end-user accounts are accounts that were migrated from another wpml.org account owner to an end-user and those accounts are limited to only one website. It is impossible to remove the site from the account or add new sites. Solution: 1. We recommended that the client visit their WPML account page and edit the URL of the site registered under their account. For guidance, we provided a link to the documentation on how to change the URL registered with WPML: Changing the URL Registered with WPML. 2. We suggested making a small edit to the URL, such as adding a blank space and saving it, or changing the URL to something else and then changing it back. 3. We informed the client that we forwarded the issue to our systems team for further investigation.
If the solution provided here is not relevant due to being outdated or not applicable to your case, 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. If further assistance is needed, please contact us through the WPML support forum.
Please note that the solution provided might be outdated or not applicable to your 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 at our support forum.
Problem: The client was experiencing a deprecation notice related to WPML when trying to update their website. The notice was as follows:
Deprecated: mb_convert_encoding(): Handling HTML entities via mbstring is deprecated; use htmlspecialchars, htmlentities, or mb_encode_numericentity/mb_decode_numericentity instead in /****/sitepress-multilingual-cms/addons/wpml-page-builders/classes/Integrations/Gutenberg/strings-in-block/dom-handler/dom-handle.php on line 32
Solution: We recommended that the client disable debug mode in WordPress to prevent these warnings from being displayed to visitors. This can be done by editing the wp-config.php file and ensuring it contains the following line:
define( 'WP_DEBUG_DISPLAY', false );
We advised the client to try this solution after taking a backup of their website and to share their feedback with us.
Please note that this solution might be irrelevant due to it being outdated or not applicable to your case. If this is the case, 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. If the issue persists, please open a new support ticket with us.
Problem: The client wants the map and contact details on their about us/contact page to reflect the nearest region based on the language set.
Solution: We recommend using manual translation to achieve this. By manually translating the about us and contact us pages, you can customize the content and design to match the desired region for each language. Here's a step-by-step guide on how to use manual translation:
Follow the instructions to set up manual translation for your pages.
Customize the translated pages to reflect the map and contact details for the respective regions.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If you're still experiencing issues, 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. If the problem persists, please open a new support ticket with us.
Problem: The client is unable to prevent page slugs from being translated following the documentation on translating page slugs. Solution: 1. Navigate to WPML → Settings and scroll to Translated documents options. 2. Under Page URL, choose one of the following options: - Autogenerate from the title: The slug will be created from the translated page title. - Translate: Allows translating the default language slug. - Copy: This will copy the slug from the default language, but it only works if the language uses encoded URLs, which can be set in WPML > Languages > Edit language settings (applicable for languages like Chinese or Russian). After changing these settings, re-translate the pages for the changes to take effect.
If the 'Translate' option is selected, make a small change to the default language page, save it, and resend it for translation to create a new translation job. For more information, refer to a related ticket.
Please note that the solution provided might be outdated or not applicable to your case. If the issue persists, 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 assistance, 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