Problem: The client needs to automatically translate over 100 product categories, menus, and other taxonomies without doing it manually. Solution: If you're experiencing the need to translate a large number of taxonomy terms, such as product categories, menus, and other taxonomies, we recommend creating a temporary product and assigning all the taxonomies you wish to translate to that product. Then, use the Advanced Translation Editor to translate the product automatically, which will also translate all the assigned taxonomies.
For detailed steps on how to translate all taxonomy terms at once, please refer to our documentation:
Regarding menus, WPML provides options to translate them automatically, manually, or synchronize their content between languages. For more information on translating menus, please visit: Translating Menus
If this solution doesn't look relevant to your situation, please open a new support ticket here.
Problem: The client wanted to add a separator like "|" between the languages in the WPML language switcher and needed help with the CSS code to properly position and style the separator. Additionally, the client required assistance with displaying the language switcher horizontally with the separator on mobile devices.
Solution: We recommended checking our documentation on creating a custom language switcher and fixing styling issues:
Please note that the solution provided might be 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: Client reported an issue where webhooks are WC Webhook is not triggered when a new product translated.
Solution: We have confirmed that this is a known issue and it will be addressed in a future update of WPML. However, this fix will take some time to be released. In the meantime, we recommend the following workaround: 1. Ensure you have a complete backup of your site files and database. 2. Add the following code to your theme's functions.php file:
Problem:
We have custom blocks such as the top banner block is a custom block. The content of it is not picked by the WPML editor and thus it is not getting translated. Hence we have to manually translate it which is double work.
Solution:
When you're using custom blocks on your website, you need to make them compatible with WPML by following the simple steps from the article below.
Problem: The client is experiencing an issue where images deleted from the Media Library in the default language (English) are not being removed from the Spanish Media Library on their multilingual website.
Solution: We explained that in WordPress, media is treated as a post type, which means that deleting an image in one language does not automatically delete its translation. To resolve this, we recommend the following steps: 1. Navigate to WPML > Settings > Posts and Pages synchronization. 2. Check the box labeled "When deleting a post, delete translations as well". 3. Scroll down and click the blue "Save" button to apply the changes.
It's important to note that this setting will only apply to new deletions and will not affect media that has already been deleted without a corresponding translation. For media that has been deleted prior to this setting change, the translations will need to be removed manually.
If this solution doesn't seem relevant to your situation, please feel free to open a new support ticket with us.
Problem: When hovering over the language flags, the code for the img tag is displayed. Solution: This issue usually happens when the theme doesn't support image in a menu and this can be fixed by using the following JavaScript code to remove the 'title' attribute from the language switcher links:
Problem: The client is facing an issue with setting different prices for product translations in a multilingual WooCommerce site. They are trying to import new prices for translated products, but the prices are locked and cannot be changed.
Solution: We explained that when using WooCommerce with WPML, product translations are managed under WooCommerce -> WooCommerce Multilingual -> Products. All product translations share the same details as the original product, and it is not possible to set different product details for translations within WPML.
To set custom prices in different currencies, the client should only do this on the original product. The price will then be copied to the translated product, and if using WPML's Multi-currency feature, the price will be converted automatically. However, the client will not be able to set completely different prices for the translations.
If the client needs different prices for translated products, they should not translate the original products. Instead, they should create individual products in each language independently. These products would not be linked and would not share any product details.
Problem: The client was unable to translate custom fields on their website using WPML with the Uncode theme. The custom fields were not appearing in the WPML Translation Editor, and they were not found in any translatable string lists. Additionally, they encountered a warning about the site being moved or copied.
Solution: 1. We scanned the Uncode Theme for new strings via WPML -> Theme and Plugin Localization. 2. We navigated to WPML -> String Translation and clicked on "Translate texts in admin screens" at the bottom of the page. 3. We located the detail field labels and added them to String Translation using the text-domain filter
admin_texts_uncode
. 4. We provided instructions to use the text-domain filter to find and translate the labels.
Problem: The client is unable to switch languages using the URL rewriting option in WPML. They receive an error message indicating that 'languages per directories will not function' due to potential issues with WordPress installation location, URL rewriting not being enabled on the web server, or the web server's inability to write to the .htaccess file.
Solution: We recommend the following steps to troubleshoot the issue: 1. Set the Language URL Format in WPML settings. 2. Visit the front end of your website to check if it displays correctly. - If the front end displays as expected, the error message is a false-positive, and you can continue using the URL Structure without any issues. - If you encounter an error 500, a blank page, or an error 503 on the front end, and it's resolved by changing the URL Structure, then further investigation is needed.
If this solution does not seem relevant to your situation, please open a new support ticket with us, and we'll be happy to assist you further.
Problem: You want to force WPML currencies to change on Checkout based on the shipping country. Specifically, you want Hungarians to pay in Forint when they choose Hungary as the shipping country, and others to pay in EUR when they choose the UK or any country other than Hungary. Solution: Currently, this functionality is not included in WPML. You will need a custom modification using our API. We recommend you get in touch with a certified WPML developer through our Go Global program. Additionally, you can use Hooks for custom modifications, which can be integrated into your WooCommerce templates. You can find these Hooks at WCML Hooks Reference.
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 WPML support forum.
Problem:
Message :
There is a problem with the String Translation table in your site. This problem is not causing a problem running the site right now, but can become a critical issue in the future. WPML support team knows how to fix it. Please add a message in the relevant support thread and we'll fix it for you.
Solution:
We've found some edge cases where this error is fixed following these instructions to recreate icl_tables:
- Make a full backup of your site (files and database)
- Please add this code to the bottom of the functions.php file in your theme's root folder
- Visit your site's homepage at least one time
- Remove the code
Once you complete these steps, then you have to remove the keys "wpml_string_table_ok_for_mo_import" and "wpml_notices" from the options table (by default wp_options, where "wp_" is your database prefix), and all errors should be gone.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
