Problem: The client reported an issue where the table displaying product variations was empty on the German version of a product page, despite having translated all attributes and product details. Solution: 1. We verified the use of a shortcode
[varianty id="4658"]
to display product variations and inquired about its origin, whether it was custom code or from a third-party plugin. 2. We made adjustments to the default language settings, saved them, and then re-translated the content to 100%, which resolved the issue of the missing data in the second language. 3. We recommended setting products, variations, and each created attribute to translatable via WPML > Settings. 4. The client was advised to update to WCML 5.5.2.2, translate attributes through WPML > Taxonomy Translation, and update products in the default language. 5. Products should be sent for translation via WPML > Translation Dashboard, and XLIFFs exported, re-translated, and then uploaded. 6. It was noted that the same XLIFF exported for the current translation job should be used for re-import to ensure WPML recognizes it.
If this solution does not resolve your issue, or if it seems outdated or not applicable 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. Additionally, feel free to open a new support ticket at https://wpml.org/forums/ for further assistance.
Problem: The client is experiencing issues with product titles and text content appearing in Czech and needing retranslation after adding translations through XLIFF files. Additionally, there's a discrepancy in the display of product variation tables between the Czech (CZ) and German (DE) versions of a WooCommerce site. The client uses a plugin (PVT - Product Variation Table for WooCommerce) and a custom PHP script to display these tables.
Solution: 1. For the issue with the product variations not displaying correctly in the translated version, the client needs to ensure that the custom code or plugin fetches the translated variation names instead of just the slugs. We recommend using the WPML hook
2. Since the PVT plugin is not listed as compatible with WPML, we suggest contacting the plugin author to discuss making the plugin compatible or consider using a WPML-compatible plugin like Product Table for WooCommerce.
If these solutions do not resolve your issue or seem 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 the problem persists, please open a new support ticket with us for further assistance.
Problem: The client experienced issues with missing product variations in the Czech version of their website after synchronizing translations. They had only translated some attributes relevant to the product and noticed that variations disappeared post-synchronization. Solution: We recommended checking the translation settings in WPML. It was necessary to set Products, variations, and each attribute to 'Translatable' under WPML > Settings. We also updated WCML to version 5.5.2.2 and ran the Sync option, which resolved the issue without causing further problems. The client might need to update the default language product and re-translate to ensure the translation works correctly.
If this solution does not resolve your issue, or if it 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 problems persist, please open a new support ticket at WPML support forum for further assistance.
Problem: The client reported an issue where translated products did not display any product variations. This problem arose after attempting to translate products using XLIFF files and synchronizing taxonomies, which also led to the disappearance of variations in the default language.
Solution: We advised the client to ensure that all global attributes are correctly translated, as missing translations in the secondary language can prevent variations from displaying correctly. The steps include: 1. Confirming that global attributes are used and translated. For guidance on translating global attributes, visit Translating Global Attributes. 2. Using the Advanced Translation Editor (ATE) to automatically translate attributes by assigning them to a test product and selecting automatic translation. This method is efficient as it does not incur charges for numerical values, only text. For more details, see How to Translate All Taxonomy Terms at Once and Advanced Translation Editor.
If the solution provided does not resolve the 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 problems persist, please open a new support ticket at WPML Support Forum.
Problem: You are trying to assign translations for pages created with BeBuilder in Betheme and export the content to XLIFF, but you only see a few words instead of the full content. Solution: First, ensure that all your plugins are up-to-date. You can check for WPML updates by navigating to Plugins > Add new on the Commercial tab and clicking "Check for WPML Updates". After updating, retest the export/import functionality of XLIFF. If you are using a staging site with a professional translation service, make sure to authorize the service for your site URL.
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: You are trying to set a fixed shipping price in a different currency using WPML on your WooCommerce site, but the price is being converted as if it were in the base currency. This issue arises due to a conflict between the exchange rate settings of the plugin and the WPML multi-currency settings for the same region. Solution: We recommend first ensuring that there is no conflict in the exchange rate settings that might affect the fixed price in another currency. You can try the following steps: 1. Disable all non-WPML plugins and switch to one of the default themes to check if the issue still persists. 2. Ensure that your exchange rate settings do not conflict with WPML's multi-currency settings. Specifically, check if setting an exchange ratio of 1:1 resolves the issue, as it did in your sandbox environment. 3. Always create a backup of your site (both files and the database) before making any updates or changes. If these steps do not resolve your issue or if the solution becomes irrelevant due to updates or specific use cases, 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.
Problem: The client has a website with a large database size due to previously enabled media translations in WPML, which are no longer in use. They are looking for a way to safely remove unused meta tags and attachment translation posts without affecting the content on the page and to reduce CPU load. Solution: 1. We recommend checking the following threads for solutions on how to remove WPML media translations:
2. Before applying the solutions, ensure to back up your database.
Please note that the solution provided might be irrelevant if it's outdated or not applicable to your 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, we encourage you to open a new support ticket. For further assistance, please visit our support forum.
