This thread is resolved. Here is a description of the problem and solution.
Problem: The client was unable to update to WPML version 4.7 and faced issues with their glossary disappearing after attempting updates and key changes in a staging environment. The glossary was not stored locally but on WPML's servers, and the client was concerned about the loss of translations and glossary entries. Solution: We advised the client to ensure they were not using the beta channel for updates and to switch to the production channel to check for updates. If necessary, the update could be manually downloaded from the WPML.org account. For the glossary issue, we confirmed that glossary entries and automatic translations are stored under an ATE (Advanced Translation Editor) account on WPML's servers, not linked to the WPML registration key. We recommended ensuring that both staging and production environments are connected to the same ATE account to avoid issues like missing glossary entries or unsynced translations. If discrepancies continue, we suggested re-registering the WPML key without affecting existing translations or glossaries, as these are managed separately through the ATE account. For detailed steps on managing glossary entries, please refer to this documentation.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific 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 problems persist, please open a new support ticket at WPML support forum.
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
Sorry my Gmail is a different account then jasper@drieshen.nl please grant me access via drieshen. I try to be online tonight to solve this so we can end this problem today. (shoot. I needed to send this an hour ago. Just opened my office)
*If* these files have the correct version in it. What does this mean. Obviously we can repair the glossary. But have I also lost translations (from the translation memory) that were on the pages?
If so - can we re-implement those on my staging account and how? And *if* that succeeds. I had troubles before with the migration from staging to live. Can we prevent this?
Thank you. Wel obviously the bigger one ( "client_identifier": "312e8270-c5f4-45b8-b51d-c47ee984a6be" ) is the one to use.
It only feels very limited and like there should be more. Is there not a bigger glossary? If not let's opt for this one and get on with it. I want this fixed.
Yes we are almost on opposite end of the planet I believe. This makes it a bit hard to communicate. I will be fine importing this data into the glossary. But my worries are not soothed yet.
So two more questions for:
1: Glossary
The glossary feels very empty still. Could you please have a look if there is a more complete version? Either my mind is playing tricks or this is not the final version. Maybe move up a mont or look for other client ID? It would be appreciated.
2: I need a better understanding
I still wonder about the disconnection of my site to the WPML servers. I would like a better understanding of what is stored one your end - and what is stored on my end - and the possible consequences.
So obviously the glossary is stored on your end. But if WPML is discontinued from my website. What else is lost?
I know there is a difference between the glossary and the translation memory for example. So if the "client_identifier" is lost - is this also lost? And is this lost for content of my pages or only for future translations?
And this situation arrises, should we reconnect this memory or id to my site?
And are there any other items not stored on my server that is vital for translating with WPML?
The 2 glossaries are what I found under the name for the website between staging and production, but if I search for your email I do find more entries from other projects -- maybe you recognize one that is related to this one?
hidden link
-----------------------------
Let me break down how WPML and translations work to help clarify things:
Automatic Translation & ATE (Advanced Translation Editor)
When using ATE and automatic translations, everything operates through the cloud. Your site connects to WPML’s servers to manage translations.
Each site has a unique Site ID, and there is also an Organization ID.
Think of the Organization ID as an umbrella—multiple Site IDs can belong to the same Organization.
Site Moves (e.g., Staging to Production)
When you move your site (for example, from staging to production), a new Site ID is generated.
A prompt will appear asking you to connect the new site to the same Organization ID.
If you don’t complete this step, you may run into issues like missing translation memory or glossaries.
What Is Stored in the Cloud (All this data is stored under the Organization ID and when sites go under an organization they share it):
Translations done with ATE and automatic translation
Translation memory
Glossary
Translators and Translation Managers
Translation credits
What Is Not Stored in the Cloud:
Translations done manually via the WordPress editor or the Classic Translation Editor
Two Important WPML IDs:
ATE ID
This includes the Site ID and Organization ID. All cloud-based translation data is tied to this.
Site Key
This connects your site’s URL to your WPML.org account and confirms your license status.
It does not affect your ATE or translation data.
Thanks again. Nearly there. I am starting to understand.
Concerning your Loom.
I would like to check c6a4d888-… and Cc6fe7dc-… to be sure (if I not revived these already).
So - In my project *all translations* were done with ATE. Probably sometime with multiple ATE ID's.
However, most of it was done within a certain period. So there is storage in the translation memory. *If* I identify the definite glossary - We have the glossary re-imported to my website.
However not the (partial) translation memory connected to it. Can we reconnect again to the website and if so how? And will it retro-update pages?
Sorry one more thought. Yesterday WPML found another roughly 900 translations to process. Resulting in a € 200 bill. Now I did not add any major content to the website and I found it very strange. But I was in a hurry to get staging into production (which I now did) and proceeded.
Now I am wondering if this amount of translations has to do with the ATE translations memory too?
In order to share the translation memory 2 sites have to be under the same Organization.
We can do this and connect them but it's important to note that they are also going to share the same credit card and expenses.( just in case these are different projects/clients)
Just shared the glossaries.
I took a look at the recent orders and I see a lot of translations coming from /admin-pages/ content.
Yes please connect the memory if it is NOT hidden link or hidden link.
The stagings and the productions are the same project and credit card. So if we can salvage the memory that will be great. You only have to connect the live version. So stopcarcinogensatwork.eu. I will delete the staging shortly.
Regarding the recent orders. How can I exempt pages for auto-translation? I can look for the answer myself. But you know best.
