Thank you. This did the trick - I now updated the main posttype for Norwegian, Polish, Danish and Icelandic. These were partial updates not to set you back. For now I can continue my work and get my teams to check the individual pages for translation errors.
I would suggest closing this issue because the original problem of the glossary is now functioning 🙏🏼 But I also suggest to split this one into a new discussion for "updating existing translations". This functionality does not seem to work as expected.
This issue remains and considering the upcoming languages and my desire to use the function to have WPML translate everything automatically - once I am sure "updating existing translations" works.
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
Hello,
We can handle the updating existing translation part here. May I have more details on what you mean here?
Do you mean handling the glossary part for the existing translation? I asked about the full retraslation feature and it's already being tested which means that it should be released in no time. it was paused for a moment before to make sure the glossary was handled correctly and the UX is being improved so by the time of the release it's clear what will be retranslated and what won't (jobs not using DeepL or PTC, for example won't be retranslated).
And also some performance check are being made to make sure that on big sites, this feature will work normally without a huge impact on the site's resources.
Also, In general, when we ask to retranslate something, it's mainly a workaround we use while we find and fix the "root causes" why would someone need to do this. only in like 30% of the cases it's actually the only solution. We know the idea is to translate once and that's it so that's our goal :).
Currently I am having the translations checked. It’s easier to have errors identified for me. All ready I found that some things did and some things did not translate. For example the content of the posts was translated but not the title. I will try to identify the constants if possible. Just give me a few days/week to collect the feedback.
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
No problem, take the time you need and then bring it here, if possible with ne or more example URLs (so we can check that on our end as well) and we'll get to the bottom of it 🙂
I am still collecting data. But one issue is sure. And I can't figure out what I should do with this issue. I have the following behavior:
My CPT's have a title that corresponds to entries in my glossaries. Also the content of the CPT had the same entry (original term) in the post content.
When I retranslate the post the post-content get's translated but the title does not. I am (almost) sure that this happens to every single post.
If I would correct the title through the ATE it does see/recognize the glossary term.
The only possible reason I can think of is that I have a JetEngine metafield on the CPT that also uses the term 'title'. But maybe this is a behavior you already encountered somewhere?
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
No problem!
WPML 4.8 is going to be released either today in a few hours or tomorrow morning and that contains a lot of nice fixes that will make your experience smoother.
We also found a few more things to improve that are a bit edge case about automatic translation but well, this is mainly to mention that 4.8 has a LOT of new things (not visual things, but a lot of improvements) and both 4.8 and the next WPML 4.9 are focused on improving automatic translation workflows (migrations, translate everything, bulk translation, glossaries, etc).
We postponed WPML 4.8 to add a few fixes we found on your site and on a few other sites as well so I'm sure they will be really helpful!
I still have some issues with the system although it does seem to have improved. I updated the glossary for a language today. But I found out that keeping the column 'type' makes the system disregard the upload and does not replace the existing terms. Leaving 'type' out does solve this problem.
To prevent extra costs by translating twice - I used the update translations button. But I get this notification:
"Retranslation attempted 14 minutes ago but didn't start because you have 5802 jobs that require an update which is over our 2000 jobs limit.You can use bulk automatic translation for some of these jobs to get below this limit and then try again."
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
If you have too many jobs in a short amount of time, yes, you won't be able to retranslate it. we're working to remove that limitation and the fix is almost there 🙂
--------------
About the type issue, can you send me the CSV you were uploading? So I can try to use it and test what you mentioned and check with our devs how to fix that or why it's happening because i had tested it before letting you know and things were working normally.
------------
I can ask our devs to run the global retranslation to you but would this be only for the dev site or the main site as well?
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
Ok, i know what the problem is with the glossay entries! the kind is incorrect, it has a capital "N" (I.E: Name)instead of "name", if you add them all in lowercase and without any space, it should work.
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
The retranslation should be finished now.
About the update of the glossaries. Our devs came back and told me that they are cleaning everything up to finally get rid of the "kind" column, I'm waiting on the possible timeline because I understand the fix for the update of terms you are mentioning will be in the next deployment and I'm waiting on them to know the details of it.
- I updated the glossary including the 'name' column
- Dev has updated the existing translations
Now I am focusing on the Maltese language which I am working on:
- I still see the wrong translations for the language
- The glossary has the right term but is not implemented in the translations
- If I open the ATE I see that the glossary term is recognized but not used. I am able to change this manually, but I want the system to work - not correct everything manually.
- If a send the post again for retranslation including overwrite function. But it does not update.
So what's wrong then? The retranslation trick did seem to work before.
I will send you an Excel with both the original term and the corrected term. The posttype occupations is corresponding with hidden link
