Problem: The client is in the process of translating a large amount of content and is also planning to migrate their website to a new host. They are concerned about whether the in-progress translations will carry over and finish after the migration, or if they should complete the translations before migrating. Solution: We recommend either pausing or canceling the translations before migrating, or ideally, completing all translations to ensure that all content is safely transferred and that the migration proceeds smoothly.
If this solution does not apply to your situation because it might be outdated or not relevant to your case, we suggest opening 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. If you need further assistance, please contact us in the WPML support forum.
Problem: The client was having issues with an archive page created with Bricks builder, where they used a loop to display categories and dynamic data to call the featured image from an Advanced Custom Fields (ACF) field for custom taxonomy types. Solution: We recommended the client to manually edit the translated taxonomy that was causing the issue and simply click save. This action should resolve the problem with the display of the translated taxonomy.
If you're experiencing a similar issue, we recommend you try manually editing the translated taxonomy and saving it. However, this solution might be irrelevant if it's 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: If you're experiencing issues where untranslated products lead to a 404 page instead of redirecting to the main product page in the default language, this might be due to products with draft status appearing on the front end because of the translation preference settings.
Solution: Check the URLs of the products. They might have a format (with a parameter like ?p=1234) indicating that they are still in draft status. To address this: 1. Review the translated products with draft status and publish them to ensure they have the correct URLs. You can find guidance on reviewing automatic translations here.
Problem: The client was experiencing an issue where the URLs for pages like the cart and shop in Arabic were changing to 'cart-2' and 'shop-2', despite adding a language prefix '/ar/' to the URLs. Solution: We explained that this is expected behavior in WordPress when a page slug is auto-generated and another page with the same slug already exists, resulting in the second page having a '-2' suffix. To resolve this, we suggested two options: 1. Manually edit the page in Arabic, change the slug, and save the changes. 2. Use the Advanced Translation Editor to translate the page slug. We provided a link to the documentation for further guidance: Translating page slugs.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also highly suggest 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.
Problem:
If you're unable to translate the "Flat rate" shipping method on the checkout page in WooCommerce using WPML. Solution:
First, navigate to WooCommerce > Settings > Shipping > Edit the shipping zone > Edit the shipping method and re-save it. Then, go to WPML > String Translation and search for the string you wish to translate. Once you find it, you can proceed with the translation. For a visual guide, please refer to the screenshots provided in the support thread.
If this solution does not apply to your situation because it's outdated or not relevant to your case, we recommend opening a new support ticket. We also 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 further assistance is needed, please contact us in the WPML support forum.
Problem: The client needed to display the currency code as "AED" in English and "د.إ" in Arabic on their WooCommerce website. Solution: We recommended using the
wpml_current_language
filter hook to determine the current language and then display the appropriate currency code. Here is a step-by-step guide: 1. Add a filter to the
woocommerce_currency_symbol
. 2. Use the
wpml_current_language
filter to get the current language. 3. Depending on the language, set the currency symbol to "AED" for English or "د.إ" for Arabic. Here is the example code:
We also informed the client that custom code assistance is beyond the scope of WPML support and suggested contacting one of our certified partners if they need further help with the implementation.
Please note that this solution might be irrelevant due to being outdated or not applicable to your case. If this solution does not solve 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 open a new support ticket.
Problem: The client is trying to translate checkout fields using the free version of Checkout Field Editor for WooCommerce but is unable to see any fields in the string translation. Solution: We recommend the following steps to translate the checkout fields: 1. Navigate to WooCommerce > Checkout Form, then edit the field by making a small change to it and save the changes. 2. Proceed to WPML > String Translation and translate strings in the domain
"woo-checkout-field-editor-pro"
.
If this solution does not apply to your situation because it might be outdated or not relevant to your case, we suggest opening 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. If further assistance is needed, please contact us through the WPML support forum.
Problem: The client needs to hide the development notification without switching to the production site. Solution: If you're experiencing this issue and prefer not to switch to the production site at this time, we recommend using CSS to hide the notification. However, the recommended steps are: 1. Visit WPML.org > Account > Sites (https://wpml.org/account/sites) and remove the old key. 2. Generate a new key for the new domain. 3. In your WordPress backend, navigate to Plugins > Add new > Commercial and register WPML with the new key. You may need to click "Unregister" first. If the development notice persists, it could be due to caching. In that case: - Contact your hosting support to clear the server/CDN cache. - Clear the site cache from any caching plugin installed on your site.
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 necessary, please open a new support ticket for further assistance.
Problem:
The client is having difficulties with the language versions of their website. English is the main language and the page in this language is:
https://sortaider.lv/co2-calculator/
. Latvian is the secondary language and the corresponding translation can be found at:
https://sortaider.lv/lv/co2-kalkulators/
. The customer did not clearly specify the problem, so he was asked to provide more details. Solution:
If you are experiencing a similar problem, we recommend that you provide a detailed description of the problem so that we can better understand the situation and offer you an appropriate solution. Be sure to include specific links and describe what you expected to see versus what you're actually seeing.
If the solution we provide here turns out to be irrelevant, either because it is outdated or because it does not apply to your case, we suggest opening a new support ticket. We also strongly recommend that you review the known issues, check the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins.
If you need additional assistance, do not hesitate to contact us through the WPML support forum.
Problem: The client was unable to activate the WPML plugin and encountered a fatal error indicating a function redeclaration conflict with Polylang. Solution: 1. We advised the client to deactivate the Polylang plugin. 2. We explained that running multiple multilingual plugins simultaneously is not recommended due to potential conflicts. 3. After following our advice, the client successfully activated the WPML plugin.
If the solution provided here is not relevant to your case, because it might be outdated or not applicable, we encourage you to open a new support ticket. We also 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 further assistance is needed, please contact us in the WPML support forum.
Problem: The client was experiencing warning messages on the single product page after translating strings from English to Italian using Shopengine Pro. Solution: We recommended the client to: 1. Create a full backup of their website. 2. Disable the XML Sitemap Generator for Google plugin. 3. Resave the permalinks settings by going to Dashboard > Settings > Permalinks. 4. Enable the XML Sitemap Generator for Google plugin again.
If the solution provided here is not relevant to your case, perhaps because it's outdated or it doesn't match your situation, we encourage you to open a new support ticket. We also 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 further assistance is needed, please contact us through the WPML support forum.
Problem: The client needed to change the URL of a language site from "/nb" to "/no". Solution: We informed the client that it is not possible to directly change the language code in the URL. Instead, we recommended the following steps: 1. Create a full backup of the database and website. 2. Create a new language with the desired code. 3. Duplicate the content from the old language to the new one. We provided a guide to assist with this process: https://wpml.org/faq/how-can-i-assign-or-change-language-code-to-existing-content/ 4. Delete the language with the old language code
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If you encounter any issues or if the solution does not work for you, we highly recommend checking the 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 do not hesitate to open a new support ticket with us.
Problem: The client has set the URL of the domain they want to use for the page where the translation should be displayed. However, when trying to view the translations on the specified URL in the "language" settings, the original page is shown instead. Solution: 1. We asked the client to confirm if they had translated the page into the secondary language. For guidance on translating content, we recommended visiting Getting Started Guide. 2. We advised the client to ensure that their domain is set correctly by checking the instructions on How to use WPML with different domains per language.
If the solution provided here is not relevant due to being outdated or not applicable to your case, we suggest 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 in the WPML support forum.
Problem: The client wants to export content from WordPress that has been translated using WPML, regardless of whether the WPML Translation Editor or the WordPress Editor was used. The client wishes to back up this content externally, such as in a Google Doc or a spreadsheet. Solution: We recommend using the standard WordPress export functionality found under Tools → Export. This feature works irrespective of the translation method used. For a more flexible exporting tool, the client can use the WP All Export plugin. Detailed documentation on how to export multilingual websites using WP All Export and WPML can be found here:
Please note that the solution provided might be outdated or not applicable to your specific case. If the solution does not 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 is trying to add the Dutch language to their site and has used the automatic translation feature, but the content is still displaying in English. Solution: We recommend checking if all pages have been automatically translated and how these pages were created. It is important for the client to provide a detailed explanation of the issue, and in some cases, screenshots can be very helpful in resolving any confusion or miscommunication.
If the provided solution does not apply or is outdated, or if the issue persists, we encourage the client to open a new support ticket. We also highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that the latest versions of themes and plugins are installed. For further assistance, please visit our 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
