Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
If possible test it first on a staging site, with the beta version even though the change is a server-side one. the beta version is just improved to handle situations better so it will lower failure chances even further.
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
Whenever you migrate you'll need to change the sitekey. Maybe you have the sitekey fom another domain registered at the moment and that can be fixed by going to plugins > Add New > Commercial and then remove the sitekey and add it again.
In 4.8 the sitekey will be removed automatically when you migrate using that version to make it more on the nose, by the way :).
Anyways, if you can check it out in 4.7.6 and see it works, then you can leave it like that and use that version even know since it's already stable. 4.8 is still a beta (a stable one) so it's a but risky to use that on a live site, but it does work a bit better with the glossary feature.
Oké the import seems to work fine now (without changing to beta). I tried a full import of the glossary and partial update (one language only). Both seem to work correctly. For empty cells in an uploaded CSV it gives a neat warning and download (that’s very useful).
I am being a bit reluctant to give you 100% confirmation because it is hard to find errors with such a big database. But so far - so good! Ti be sure I documented and downloaded every step of the glossary change for safety and checks.
Normally the next step would be to use the "Update existing translations" button. This delivered errors before (glossary would fill up empty cells with original terms).
If this works as expected too I will seriously consider using the automatically translate my site switch again 🙂
But using this now will run against the limitations if I will "Update existing translations" (time or 2000 terms I believe?) on my side. I believe you mentioned this could be done from your side without the limitations? If so could you guys do this for me or take the limitation out so I can test this functionality?
I am very happy that we are getting to this phase.
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
Normally the next step would be to use the "Update existing translations" button. This delivered errors before (glossary would fill up empty cells with original terms).
Right now this will work with the last 2000 jobs from the last 30 days. However we're halfway through our implementation for the feature to work with everything, all the jobs for all the site and we expect this part to be implemented by more or less start or mid-september.
We can guarantee it will work with PTC (ex WPML AI), not so much with DeepL because they end up deciding whether to use it or not (it's a "feature" of theirs that we can't override), but so far it seems to have worked on our tests with DeepL as well so that's already a good sign.
And we can do this for you in the meantime yes. I'd suggest that you first check that the glossary is ok so we can go ahead, mainly because it might take some time so it can't be run several times in a short framework. Does this last reply mean that you're ok now with the glossary so we can proceed?
I downloaded the glossary a few times now to check. Only after a while I was able to download the full glossary. I think it took some time to synchronize.
Yes the glossary looks fine. There are a few words that delivered errors: sentences that use ";" or entries that use the same word twice (welder vs welders). So those are logical errors that need to be fixed from my end.
I will leave those in for now to see what will happen when systems is set to work.
I also made a backup for this step. Please go ahead and run. the update on the staging so: hidden link
I just run a test with a forced re-translation with overwrite existing translations. But now the glossary is not used up at all. In the previous WPML versions this was not (yet) a problem. So now it seems the glossary is disregarded completely, making it worse.
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
Hello,
I'm sorry but I don't understand your last message but it's related to what I was going to ask: did you retranslate the segment where the glossary was supposed to be used and it wasn't used at all? is that what you mean when you say that the glossary is not used?
So my conclusion is the: Because the (forced) retranslation does not use the glossary entries. The 'Update existing translations' your developers did on Friday did not result in an update my posts.
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
Yes, that explains it, thanks for the information.
I'll use the info you sent us and send it to our developers because we knew that with DeepL things were a bit tricky but it shouldn't be as you are mentioning it and with the pages and terms you mentioned, our devs can look into it 🙂
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
Quick question.
I see that you mention as an example a norwegian version of what seems to be this page: hidden link
However, on the site I can see only 3 languages that this page was translated into on our end: Estonian, Danish, Maltese.
I can see that on the front-end you do have other languages, which could probably mean they were initially translated on the live site and not the dev site. However that also means that the glossary would've not been added there at all, not by what we did.
I went and checked pages translated today and saw the other one you had mentioned: hidden link
This one is indeed a perfect example because the glossary is not applied at all here, when it should've. I saw that for some reason those glossary entries appear with "general" instead of "name" in the kind column which is why they are being ignored. However they are instead showing in the translation editor which is indeed misleading.
Would you mind allowing me access to this site and allowing me to try to reload the glossary? if possible send it to me so I can use the one you have (if not, I can use the one I see on my end, fixed with the proper "kind" value). I want to see why they didn't get updated to the correct value when you probably uploaded it correctly yourself.
