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.
