Problem: The client is unsure how to correctly import translated CSV files for WooCommerce products using WPML. They have questions about whether to include the original product in the CSV, whether to check the option to update existing products by SKU/ID, and whether to include SKU or ID in the CSV. Solution: To update products that already have translations, export both the original language products and their translations, make the required changes in the CSV files, and then re-import them. Import the original language CSV first using the option to update existing products by ID or SKU. Then, import the translated CSV, ensuring the correct language is selected in the importer and the update-by-ID or SKU option is enabled. After both imports, run WPML → Export and Import to reconnect the translations and synchronize the updated content. For links within product descriptions, WPML automatically translates internal WordPress links if the linked content has translations. External links need manual translation. For images set as “different per language” in Media Translation, leave the image column unchanged in the translated CSV; WPML will assign the correct language-specific image after the import and synchronization. WPML also offers an option to automate the Export & Import process, which can be helpful for regular updates. More details can be found here: Automate WPML Export and Import Process.
If this solution does not resolve your issue or seems outdated, 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 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.
