noraJ-2

Problem:
The client experienced issues with WPML's automatic translation service where terms like 'chrome' and 'black' were mistranslated despite having glossary entries set up. Additionally, products manually translated were marked as 'needs update' after edits or bulk actions, and significant credits were deducted during bulk automatic translation of already translated content without explicit confirmation.

Solution:
1. We confirmed that the glossary entries for 'black-nero' and 'chrome-cromo' were correctly set up before the translation. However, due to the translation engine or WPML's translation memory handling, these terms were still mistranslated.
2. To address the mistranslations, we recommended switching to the PTC engine and making minor edits to the product details to force WPML to bypass the old translation memory. This involves:
- Opening the affected product in the default language.
- Making a minor edit and updating the product.
- Resending the product for translation via WPML's Translation Dashboard.
3. To resolve the 'needs update' status, we advised:
- Going to Products -> All Products.
- Clicking the circular-arrow icon in the language column for the affected product.
- Reviewing and saving the translation to mark it as complete.
4. For the issue of unexpected credit deduction, we refunded the mistakenly deducted credits and provided guidelines to prevent future occurrences by avoiding bulk automatic translations for products with potential untranslated or modified text.

Please note that this solution might be outdated or not applicable to your specific case. If these steps do not resolve your issue, 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 here.