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.
Sun | Mon | Tue | Wed | Thu | Fri | Sat |
---|---|---|---|---|---|---|
- | 9:00 – 13:00 | 9:00 – 13:00 | 9:00 – 13:00 | 9:00 – 13:00 | 9:00 – 13:00 | - |
- | 14:00 – 18:00 | 14:00 – 18:00 | 14:00 – 18:00 | 14:00 – 18:00 | 14:00 – 18:00 | - |
Supporter timezone: America/Los_Angeles (GMT-07:00)
This topic contains 27 replies, has 2 voices.
Last updated by Jasper 10 hours, 14 minutes ago.
Assisted by: Bobby.
Author | Posts |
---|---|
March 17, 2025 at 4:58 am #16822847 | |
Jasper |
Background of the issue: Symptoms: Questions: |
March 17, 2025 at 10:01 am #16823739 | |
Dražen Supporter
Languages: English (English ) Timezone: Europe/Zagreb (GMT+02:00) |
Hello, Thanks for contacting us. While you wait for my colleague to take over the ticket, let me try to help you with the issue quickly. It is available to update, make sure you are not using the beta channel but the production one. Then click the button to check for updates. - https://wpml.org/faq/how-to-install-beta-and-development-versions-of-wpml/ You can also download it manually from your WPML.org account, image attached. Regards, |
March 17, 2025 at 10:39 am #16823927 | |
Jasper |
Thank you. I found that page. However I get: Connection failed! Please refresh the page and try again. (Unable to register: Site key not matching). This is my staging environment. And WPML is connected as such. Please advice. |
March 17, 2025 at 11:14 am #16824090 | |
Alejandro Supporter
Languages: English (English ) Spanish (Español ) Italian (Italiano ) Timezone: Europe/Rome (GMT+02:00) |
Hello, Please try the following: - Go to Plugins > Add New > Commercial |
March 17, 2025 at 11:20 am #16824103 | |
Jasper |
Hi Alejandro, Before I do this... to make sure. You want me to deregister the production domain and then register this on the staging domain? Will that not destroy my current lexicon on production? |
March 18, 2025 at 11:04 pm #16832822 | |
Bobby Supporter
Languages: English (English ) Timezone: America/Los_Angeles (GMT-07:00) |
Hi there, What my colleague is suggesting will not affect your tranlsations or automatic translation lexicon. He is referring to the WPML account registration key which is only related to your wpml.org account. Your automatic translations and the library use another account that is seperate and will not interrupted by this change. |
March 20, 2025 at 12:40 am #16837678 | |
Jasper |
Oké that worked. Thank you |
March 20, 2025 at 2:15 am #16837797 | |
Jasper |
Oké so I did al this and relinked the site. This resulted in the deletion of my previous link code. I probably is considered a new website. Now I found out that almost all of my glossary is gone. Just after we released a press release! Many people have worked on this glossary and I am in a problematic spot now. Restoring backups on my production site to recover this glossary does not fix the issue as I found out that the glossary is not stored locally! I googled it and found: "We informed the client that Glossary entries are not stored in their site database but are saved on our server. These entries are used when utilizing the Advanced Translation Editor to translate content on our server and can be shared between sites associated with the client's organization." Result: my production is also broken. Exactly what I asked beforehand and was cautious of! Now how can I (or rather you) retrieve this glossary? I need it urgently! My last entry has been 22/01/24. Please, please, please I hope you can help me. I look like an idiot now with this press release and a badly translated website. |
March 20, 2025 at 7:40 pm #16841772 | |
Bobby Supporter
Languages: English (English ) Timezone: America/Los_Angeles (GMT-07:00) |
What is the URL of the new website? The URL that I have is hidden link When reviewing your AMS account, I noticed there are two pages of entries, which indicates frequent staging-to-live migrations. I highly recommend reviewing the documentation I’ve shared below to ensure a smoother process. Please provide the URL you need me to connect to, and I will manually migrate them together. Re-registering the WPML key with WPML.org will not remove existing translations or the glossary, as these are unrelated. Something else in the process must have caused this issue—such as migrating the site without properly linking it to the existing AMS account. We advised creating a new key for WPML.org registration, which would not have impacted your translations. You can find more details on this here: |
March 21, 2025 at 2:25 am #16842246 | |
Jasper |
The hidden link is the staging site of hidden link. It was a recent pull from the production website. Both are missing the complete glossary. I disconnected the production and needed to create a new key (as suggested) for the staging in order to make the update. I needed to delete the key of production on WPML for that. Since I assumed the glossary was on the site, I did this. I think the old key is associated with the glossary? However that is deleted. Can you confirm that the glossary is indeed stored at WPML? And if this is retrievable? |
March 21, 2025 at 7:51 am #16842878 | |
Jasper |
Also I did some further investigation. But it turns out that translations from the glossary are not resulting in a 'stored' result on the page. In other words my corrections on the automatic translations are gone and pages continue have spelling issues. Since this a scientific site one could state that these pages now contain functional errors. I also backtracked any other explanations how this glossary could be gone since a few entries are still there. But I could not find any other reasons or explanations. I really hope that retrieving a previous used WPML key results in the retrieving of a backup of the glossary that I can again upload to our staging. |
March 21, 2025 at 5:48 pm #16846088 | |
Bobby Supporter
Languages: English (English ) Timezone: America/Los_Angeles (GMT-07:00) |
This is the official documentation for the glossary The glossary is related to your ATE account(organization). There are multiple organizations under your URLs. I would like to request temporary access (wp-admin and FTP) to your site to test the issue. **Before we proceed It is necessary to take FULL BACKUP of your database and your website. Providing us with access, you agree that a backup has been taken ** I often use the Duplicator plugin for this purpose: http://wordpress.org/plugins/duplicator/ NOTE: If access to the live site is not possible and the staging site does not exist please provide me with a duplicator package created with the duplicator plugin. Thank you, |
March 21, 2025 at 11:53 pm #16846660 | |
Jasper |
Oké then I advise to have a look at the production website since it runs a daily backup. My staging has the old WPML running Production site PLEASE BE ADVISED: [removed] FTP: These details are only valid for 24 hours and change each time you access them. [removed] Staging site If you would like to have a look at the new WPML running at the staging website. The following credentials can be used. NOTE: This runs NO BACKUPS! or has FTP. Also it has a NEW WPML key associated with it (after deleting the old one). [removed] Also. I would still like an answers to my question: "Can you confirm that the glossary is indeed stored at WPML? |
March 24, 2025 at 6:35 pm #16853737 | |
Bobby Supporter
Languages: English (English ) Timezone: America/Los_Angeles (GMT-07:00) |
Yes, I can confirm that the glossary is stored on WPML's servers—not in your website's database, and it's not linked to your WPML registration key. Here’s a quick breakdown of how it works: The WPML Key Automatic Translation & Glossary It’s important to note that when migrating a site (e.g., from staging to live), you need to ensure both environments are connected to the same ATE account. If they aren't, it can result in issues such as missing glossary entries or translations not syncing properly, because the data is saved under two separate ATE "organizations." If that happens, we can fix it on our end—but to do so, I’ll need to confirm where the glossary currently "lives" (i.e., which ATE account it’s stored under). From your message, it looks like you have both a staging and a production site —let me know which one has the glossary, so we can proceed from there. --- Which site at the moment has the glossary working OK? (does it show ok here ? hidden link --- Which site is missing the glossary? (The staging from what I understand here hidden link |
March 25, 2025 at 5:50 am #16854668 | |
Jasper |
Hello Bobby, Oké, then at least I have growing confidence that I don’t need to ask all these people to redo their work. However, neither of the websites currently has the correct glossary. I now have two working theories: 1. The glossary was lost when we deleted the key while updating to WPML 4.7. In the first scenario, the link to the glossaries may have been broken when I deleted the key for stopcarcinogensatwork.eu on WPML.org, as suggested (or understood). To my knowledge, previous migrations between staging and production didn’t affect the ATE account—except during the last attempt when upgrading to 4.7. The second theory came to me after reviewing previous invoices for automated translations. According to those invoices, the account appears to have been connected to a different, older staging environment: stg-w1mn5b.elementor.cloud. After pushing to development, we deleted that staging environment. (Reference: Invoice ATE-1087982 / Payment reference A5B8133F-0004). I can't be sure if I checked the glossary state after the deletion of that staging. Here’s how you can identify the correct glossary: - The correct glossary was originally associated with stopcarcinogensatwork.eu. At this point, my only concern is recovering the glossary. I hope it can be retrieved based on the above information — either by restoring it directly to the production site or providing it as a CSV file so I can import it into the staging environment. Kind regards, |