Thank you. I will add one more behavior to this issue. This might help finding it. I just added a new Language Turkish to the website (production). Without doing anything to it the Glossary 'filled' itself with translations using the original term als translated term. Again it did not touch anything, I only added the language.
Can you please create a backup and then do the same thing on your staging site and try to reproduce the issue so we can confirm the issue is happening? That way, we can then revert the backup and do the same steps and see what happens and goes wrong.
Hoping this does not use extra credits. I know it should not but I experienced different before. I added the translation and it showing a fallback to original term under Turkish. Not sure if that's because it is doing so here or getting that info from the connected memory on production. I would say the latter.
I am sorry, but I am confused by your reply. I am not sure what exactly you did seems like some new steps you tried. I would like us to try the steps suggested and concentrate on reproducing that issue first.
Can you please check my reply again from above, and see if this new issue happens also on staging when adding a new language to website?
Thanks for getting back. That is clear now, and I have confirmed it also.
I tested further, and it seems this happens on any WPML website; the glossary is filled with default language terms. This is confusing, and I am checking with our team on this and for 2nd opinion.
Luckily, this default language term is not used when you translate the page; the string is correctly translated and does not use a term from the glossary. The issue is only with the display of the glossary table, which should be empty in that language and not filled.
Thank you. I am curious about the response. I found similar stories online.
I am now preparing a glossary that has every cell filled to prevent this. If I understood right is requires less 'guessing' and computing power for the ATE then an empty field.
The only thing is that is strange is that it is not consistent. I did not have this before. So either this fallback is new or something else explains this.
Sorry this is a different topic... I was misreading. I need to think of way to check this issue, because I now created all my languages and created a full glossary to prevent this issue from happening. See also https://wpml.org/forums/topic/glossary-entries-are-not-overwritten
sure, you can check with new glossary item or with current existing one / language. Maybe in the staging site if possible.
Let me share some context to keep the topic clear 🙂
Steps to check issues:
1)
Go to WPML > Translation Management> Translation tools > Glossary
Find "Aerospace Engineers", click the edit link, and remove Portuguese entry (empty) and save
Looks fine now
Recheck in 10 -> 60 minutes, observe that the deleted term has reappeared.
2)
The context is that you have existing Glossary entries. When adding new entries the original language term is by default copied across to the other languages, but sometimes clients will delete those and have no value for some of the languages.
So for example there is no value for French languge. After adding new languages, like Italian and Portuguese we end up with all languages having the default value, including French that was empty.
If a client has intentionally left a language blank that should not be overwritten.
The current behavior for single entries works as expected.
My concern is how this behaves in bulk when adding a new language in ATE, especially with a very large glossary.
If all “original terms” are copied into the new language, I will end up with hundreds of wrong-language entries. For my workflow, this is worse than having empty fields, because:
- Most glossary items are also my post titles and taxonomies.
- Correcting from English → target language is far more work than reviewing an AI-suggested translation.
- I can’t pre-build the glossary for a language that doesn’t yet exist. And this a lot of work. Again I rather review the AI work.
With the current 30-day / 2000-job limit, translating, then checking and updating the full glossary is not feasible at my scale. But I know this limitation will be removed in the near future.
Also the future bulk-edit will help me navigate this problem. This is why the current bug I am working on with importing and overwriting the glossary is so important for me.
Still, I would prefer new-language glossary entries to be empty by default, or have this as a option in WPML.
In short:
When creating a new language, I would opt for an 'option' to avoid using the source language as a fallback for glossary entries. This would prevent thousands of incorrect entries and make large-scale setups like mine manageable.
While I am at it - I would also suggest the feature/option to disable automatic translations for specific languages. This would also be a great timesaver for me.
thanks for getting back, I appreciate your feedback, but I am afraid you maybe have misunderstood my reply. Those are issue that were reported by you and escalated to our dev, and should be fixed now.
Currently, we are at different status of these bug, it was already reported long time ago, and our devs worked to fix bug you reported and it should work fine.
Now, to revert to previous reply from me and to stay on course and topic, we would need you to somehow confirm if those mentioned bugs are fixed now or still happens for you, maybe best on staging site. That way we can know if the ticket can be closed and issues are fixed or there are still some edge cases where it happens, like in your website.
For any new suggestion / feature request, we can open a new ticket to keep things clear.
