[Fechado] Glossary Bug: Source Terms Auto-Fill Translations – Breaking Workflow Across 30+ Languages

Background of the issue:
Hi,

I submitted a ticket on this issue before, but it was escalated and never followed up. I’m now reopening it, as it’s blocking our workflow on a large multilingual project.

⸻

Context:
• I’m using a glossary with 483 items, designed to support 30+ languages.
• When I add a new language, the glossary for that language auto-fills with the original (English) terms, instead of remaining empty.
• This creates critical errors when using Automatic Translation Editor (ATE), as the original terms get reused in all target languages — leading to incorrect translations throughout the site.

⸻

Issue also occurs when:
• Using the “Update existing translations” button: even empty glossary fields are overwritten with the original language terms.
• This rewrites previously fixed glossary entries and invalidates many translated posts.

⸻

Tried workarounds (not sustainable):
1. Manual fix: Deleting hundreds of glossary entries manually, then resending posts for retranslation.
→ Solves the issue temporarily but is time-consuming and doubles translation costs.
2. Disconnecting WPML account before translating a new language:
→ This prevents the glossary from interfering, but obviously not viable at scale.

Urgent Questions:
• How can we prevent WPML from auto-filling glossary translations with source terms?
• Is there a way to globally disable or override this behavior?
• Is there a supported method to clear glossary translations in bulk — safely and permanently?

Symptoms:
The glossary auto-fills with original language terms when a new language is added, causing incorrect translations. The issue also occurs when using the 'Update existing translations' button, which overwrites empty glossary fields with original language terms, rewriting previously fixed entries and invalidating many translated posts.

Questions:
How can we prevent WPML from auto-filling glossary translations with source terms?
Is there a way to globally disable or override this behavior?
Is there a supported method to clear glossary translations in bulk — safely and permanently?