Problem: The client needed to translate product descriptions from Greek to Bulgarian while keeping English words unchanged. They also inquired about the behavior of the translation memory when deleting and retranslating products. Solution: We explained that when the client translates descriptions for products using automatic translation, these translations are saved into the translation memory. If the client edits and corrects a translation for a product, this updated translation is stored in the translation memory. For any new product created with the same description, it will automatically use the newly edited translation. However, for existing products, the client will need to manually update the description to apply the changes from the edited translation. Regarding the deletion and retranslation of products, the client can delete their translated products and retranslate them without using any credits, provided they do not delete the "primary" language of a product. We advised the client to perform a backup before proceeding.
If this solution does not resolve your issue or seems outdated, we 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 noticed that the number of translated product posts in Bulgarian (922) exceeded the original product posts in Greek (857) on their WordPress site. They were unsure if this discrepancy was due to an error in the translation process or if additional products were created in Bulgarian.
Solution: We recommended the client to first check for any duplicate products by filtering Bulgarian products in WooCommerce > WooCommerce Multilingual & Multi-Currency > Products. This could reveal if original Bulgarian products were mistakenly created. Additionally, we suggested running a test by translating a product to 100% to see if any unexpected results occur.
For the issue of managing translations, we advised using the WPML Translation Editor for translating products after importing the original products in Greek. If the client had used WP All Import for importing products, it's crucial to use the WPML All Import Addon for translations, although this plugin is outdated and no longer recommended. Instead, we now recommend using the new "WPML Export & Import" plugin, which can be found here: https://wpml.org/documentation/related-projects/wpml-export-and-import/
To manually connect translations or change the source language, the client can refer to this guide: https://wpml.org/faq/how-to-link-already-translated-pages/. Additionally, to identify translated content by code, WPML's hooks can be utilized. More information on obtaining translation IDs (trid) and fetching translations can be found here:
If these steps do not resolve the issue or if the solution seems outdated or irrelevant, 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 WooCommerce Multilingual & Multicurrency to set different prices per currency based on the visitor's location. However, the price does not change according to the visitor's location when accessed from Bulgaria, showing the same price as the Greek version.
Solution: 1. To display currency based on the visitor's language, ensure the content is translated into the respective language. For example, when a visitor from Bulgaria accesses the site in Bulgarian, the prices should display in BGN. 2. For proper location detection use the "MaxMind Geolocation" API. More details can be found here: Setting up currencies per location. 3. Check for plugin conflicts by deactivating other plugins and testing the currency display. Also, verify the correct operation of the VPN or MaxMind service being used for geolocation. 4. If issues persist, consider opening a new support ticket focused on this specific problem.
Please note that this solution might be 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. If the problem persists, please open a new support ticket at WPML support forum.
