Problem: You want the translation column to always be visible on the WooCommerce product list in the admin area, but even after using a code snippet to unhide the column, no data is displayed in it. Solution: We recommend implementing a custom function to ensure the 'icl_translations' column is always visible and contains data. Here's a step-by-step guide: 1. Add the following function to your theme's functions.php file or a custom plugin:
Please test this solution in a staging environment before applying it to your live site, as this custom code is a courtesy and not officially supported by us.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is using a custom script to update stock and prices of products via the WooCommerce API. This script updates only the main language, and while the stock and prices reflect correctly across all languages, the translations for product names and descriptions are reset to match the main language. Solution: 1. We recommend checking if the 'save_post' hook is being executed after updates. This hook helps ensure that changes are properly synchronized across translations. 2. Verify if the WPML translation editor is disabled for the products. If it's not, any save in the default language might reset manually added translations. For more details on using different translation editors, visit Using Different Translation Editors for Different Pages. 3. If products were duplicated using WPML's 'Translation Management', check the post meta table for 'icl_duplicate_of' and delete if any entries are found. This can prevent content from syncing/duplicating incorrectly on save.
If these steps do not resolve the 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.
Problem: The client is developing a site using a Blocksy child theme and has implemented custom code for WooCommerce warnings in a file named 'ufi-warnings.php'. This code adds a product tab for UFI warnings and allows selection of UFI numbers for products. The client used WPML to translate the product tab into Slovenian and scanned the child theme for custom code translations from Croatian to Slovenian. However, the client encountered issues with the text domain in localization functions. Solution: We advised the client to ensure that all hard-coded strings in their PHP code are wrapped in WordPress localization functions like
__()
and
_e()
, and to specify the text domain as a string. This is crucial for the parsing tools to correctly distinguish between different text domains. The client was incorrectly using a variable for the text domain, represented as
If this solution does not resolve your issue or seems irrelevant due to updates or differences in your case, 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.
Problem: The client needed the Finnish, Latvian, and Lithuanian flags in their WPML language switcher to link to external partner sites instead of internal translations, but the existing jQuery code was not functioning. Solution: We recommended adding a custom function to the
functions.php
file of the client's theme. This function modifies the language switcher to include external links for the specified languages. Here is the code to implement:
Please ensure to back up your site fully before implementing this solution. If this solution does not resolve your issue or seems outdated, we 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 open a new support ticket.
Problema: Nella pagina delle stanze del sito, i contenuti sono duplicati e visualizzati sia in italiano che in inglese. Soluzione: Questo accade perché il tipo di contenuto 'eagle_rooms' non era impostato come traducibile.
Se questa soluzione non risolve il problema o sembra non essere più attuale, ti invitiamo a verificare i problemi noti e a confermare che hai installato le versioni più recenti dei temi e dei plugin. Se necessario, apri un nuovo ticket di supporto.
Problem: The client is developing a site and needs a separate payment gateway for each currency. The gateway is custom coded, and the client wants to make it compatible with WPML's multicurrency feature. Solution: We explained that any payment gateways set up in the Payments section of WooCommerce → Settings will be available for all site’s currencies. If the client wants to use different gateways with different settings for each currency, this is only compatible with a few gateways. For a custom-coded gateway, ensuring compatibility with WPML's multicurrency feature is not straightforward and requires complex compatibility collaboration with our developers. We recommend that if the client's plugin will be publicly available, they should consider joining our Go Global program to collaborate with our compatibility developers.
For more details on setting up payment gateways for each currency, please visit this documentation.
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.