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.
Tagged: ATE, Bug, Large Sites
This topic contains 24 replies, has 1 voice.
Last updated by Jasper 1 week, 2 days ago.
Assisted by: Alejandro.
Author | Posts |
---|---|
July 2, 2025 at 7:16 am #17191059 | |
Alejandro WPML Supporter since 02/2018
Languages: English (English ) Spanish (Español ) Italian (Italiano ) Timezone: Europe/Rome (GMT+02:00) |
Scratch that, I got confirmation that the problem was indeed on our end but it wasn't related to the change made to you, it should be fine now but also yesterday soon after you saw it. it was a temporary issue that happened while we were upgrading the servers. Can you confirm it's ok now? |
July 2, 2025 at 7:21 am #17191069 | |
Jasper |
Oké thanks. Looks oké... let me test and confirm. |
July 2, 2025 at 7:37 am #17191136 | |
Alejandro WPML Supporter since 02/2018
Languages: English (English ) Spanish (Español ) Italian (Italiano ) Timezone: Europe/Rome (GMT+02:00) |
Let us know how it goes 🙂 |
July 2, 2025 at 2:47 pm #17193844 | |
Jasper |
Hi Alejandro, I believe everything is in place now. I’ve translated key content into the remaining ~20 languages, ensuring that the main taxonomies and core glossary titles are properly translated. I used my custom export tools to generate the glossary and I’ll also be sharing my tool with the managers, so they can download and update their respective glossary items. I’ll then update those entries in the system. See: hidden link Next, I’ll get the ATE translating the full language versions and ask local reviewers to walk through the individual pages (cross-reading). Using the standard translation editor. So for now, I believe the main issues are resolved — thanks again for your support. A few things I’ll keep a close eye on: - Empty glossary cells: I’m curious how the system will behave with a few remaining empty cells. - Abbreviations and general terms: The export tool includes options for both abbreviations and full terms, but the system doesn’t seem to recognize this distinction. What’s the intended philosophy behind that? Best regards, |
July 2, 2025 at 6:36 pm #17194541 | |
Jasper |
Sorry, I did something stupid and disconnected both production and staging from my account. I don't see how to reconnect them. Both are now asking for a migration code. hidden link (80f7120627) SEEM TO DELETED THIS ONE That also disconnected my glossary (which stated only 54 entries). But I can fix that with my copy here. Sorry |
July 2, 2025 at 7:11 pm #17194617 | |
Alejandro WPML Supporter since 02/2018
Languages: English (English ) Spanish (Español ) Italian (Italiano ) Timezone: Europe/Rome (GMT+02:00) |
What's the domain you're currently using at the moment? Remember you can't connect the sites if they have a Pay as you go account. You can connect sites without one to a site with an account, when I last checked, the sites were not connected (I'm talking about yesterday). |
July 2, 2025 at 7:14 pm #17194619 | |
Jasper |
Yes I know. But there is no Pay as you Go connected either. I deleted the connections in a stupid way. I moved to hidden link I can make a new connection. But I hope to safe some of the translation memory. |
July 3, 2025 at 9:53 am #17196289 | |
Alejandro WPML Supporter since 02/2018
Languages: English (English ) Spanish (Español ) Italian (Italiano ) Timezone: Europe/Rome (GMT+02:00) |
if you connect the sites that have translation memory, they will be shared among all others. so far from what i understand the connected sites should be: - stopcarcinogensatwork.eu I can even connect them for you if you want, and you'll get to keep everything, probably even the translation memory you had in one of those sites. If there's a 3rd site (like: stg-stopcarcinogensatwork-c23taal.kinsta.cloud ) then let me know about it so i can search it. Alternatively if you do have access to those sites, you can connect them together and they will start sharing the translation memory again. |
July 3, 2025 at 9:58 am #17196350 | |
Jasper |
If you can connect them for me, I would be grateful! Just those two: stopcarcinogensatwork.eu, env-stopcarcinogensatwork-development.kinsta.cloud And could you please provide me with insight on my question before?: Abbreviations and general terms: The export tool includes options for both abbreviations and full terms, but the system doesn’t seem to recognize this distinction any more. What’s the intended philosophy behind that? Thank you very much! |
July 3, 2025 at 11:31 am #17196993 | |
Alejandro WPML Supporter since 02/2018
Languages: English (English ) Spanish (Español ) Italian (Italiano ) Timezone: Europe/Rome (GMT+02:00) |
I linked those 2 sites, try to open a page that was previously translated and see if the translation memory is in place (if it appears as translated, then it's all ok). ----------------- About the general terms and names: the "General" type was used solely for DeepL at the end and it was dropped because DeepL used it more as a "suggestion" than an actual glossary entry (it's a "feature" to use it like that, according to them, which is weird). this means that at the end, both ended up being used the same way so the "general" type was dropped. You should use only the "name" type from now on. in version 4.9 we'll completely delete the reference to it so it will be a simple glossary, by the way (That's why I was asking for your feedback regarding this, which was passed to our devs and is being studied to see if we can improve what we already have 😀 ). Regards, |
July 3, 2025 at 12:20 pm #17197192 | |
Jasper |
Hi Alejandro, Oké thank you. It was an old glossary connected to this one apparently. But I updated it. All seems fine now. Also thank you for your explanation. I am curious about future developments. Regards, |