(Latest) translation through Advanced Translation Editor is not displayed

This thread is resolved. Here is a description of the problem and solution.

Problem:
If you're experiencing issues where taxonomies and image texts translated using the Advanced Translation Editor (ATE) are not syncing to the translation memory, resulting in untranslated strings or outdated translations appearing on your website, we can help.

Solution:
This is a known issue WPML overwrites edits in the Advanced Translation Editor for taxonomies and image texts translations

It's recommended to translate taxonomies first in WPML > Taxonomy Translation before using ATE. This ensures they appear already translated in ATE, preventing the need for retranslation. Remember, any changes should always be applied in Taxonomy Translation.

If these solutions do not seem relevant to your issue, please do not hesitate to open a new support ticket with us for further assistance: Contact WPML Support.

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: Documentation request

This topic contains 8 replies, has 2 voices.

Last updated by Laura 1 year ago.

Assisted by: Laura.

Author	Posts
October 23, 2023 at 9:57 am #14635755
anastasiosG-2	Hello there, I have assigned the complete website's translation to a professional translator through the wp admin panel -> WPML -> Translation Management. You can see the translation in the "Translators" menu item on the WPML -> Translation Management. Her name is Konstantina Koutsioumpa. So, I created jobs and assigned them to the translator for the whole website. The translator complained to me multiple times that the Advanced Translation Editor that I instructed her to use to translate the site did not sync every single string of the 100% completed translation jobs to the translation memory. I explained that I would have to open a support ticket to tackle this but we did not do it since the translation job's deadline was imminent. Therefore, the translator had to translate some strings multiple times. Now that all the translation jobs are 100% completed and I added the language switcher in the website's primary menu, I noticed that some English strings are not translated in Greek. I sent these to the translator thinking that she did not pay attention to the specific untranslated strings but she told me that she had translated them. Furthermore, upon checking on the translated version of the website as a visitor, she told me that the translation of some strings is not the latest version she had translated but an older one. Let's take for example a property's page (hidden link). As you can see for yourself, in this page there is some untranslated content like "Crib - available upon request" and "Outdoor Furniture" that the translator had translated though through the Advanced Translation Editor tool of WPML. Furthermore, she told me that some of the translated content displayed right now in the front end is not the latest version of her translation. For example, the translation of (e.g. the translation of the string "Paid Parking Garage - on premises" is displayed as "Πάρκινγ σε γκαράζ με πληρωμή - στο κτίριο" which is an outdated version of her translation job. The same with the string "Free on-street parking" that is translated as "Δωρεάν θέσεις στάθμευσης στον δρόμο". This is not her final translation either. I am sure there are more occurrences of similar problems as the aforementioned in the website. At this point, it is not easy to cross check every single page of the website so I hope there is another way to solve these issues. In case you need wp admin access I can provide you with an admin account. Please, let me know how to share the credentials so they won't be publicly visible. Thank you in advance for your time,
October 24, 2023 at 10:17 am #14646069
Laura Supporter Languages: English (English ) Italian (Italiano ) Timezone: Europe/Rome (GMT+01:00)	Hi, thanks for contacting us. Before checking the site, I would ask you to increase the WP Memory Limit following this procedure https://wpml.org/faq/checklist-before-opening-a-ticket-in-wpml-support/#how-can-i-increase-my-sites-memory-limit After doing that, try to resend the post with the issue to translation and download it again. Check if it's working as expected. If not, please provide me with your site's credentials. I'm enabling a private box
October 24, 2023 at 5:25 pm #14650137
Laura Supporter Languages: English (English ) Italian (Italiano ) Timezone: Europe/Rome (GMT+01:00)	Hi Anastasios, thanks for the credentials. I found something interesting about the Features - these are taxonomies, and if you go to WPML > Taxonomy translation you'll see the ones untranslated in the property are untranslated here. I did a test translating "Crib - available upon request" (copying the string displayed in the translation editor) and I see it's indeed translated. Same with the "Paid Parking Garage - on premises" category, in Taxonomy translation shows the "old" translaion. So WPML is fetching strings from here and not from the xliff file. I don't think this is the expected behavior so I'll have to ask, but in the meanwhile you know how to fix it. Maybe your translator (or someone else) translated the taxonomy in Taxonomy translation first? Did you notice this behavior with strings that aren't taxonomies?
October 25, 2023 at 7:47 am #14657597
anastasiosG-2	Hello Laura, thank you for your swift reply. What I know is that the translator used the Advanced Translation Editor to translate the website so WPML should fetch the translated strings from there and not from any other source (e.g. xliff). Apart from the property's features which are indeed taxonomies, on each property's page you can see some other strings being in English rather than in Greek as well such as "Photos", "Overview", "Description", "Bedrooms", "Bathrooms", "Features", and "Property on Map". I may have to ask the translator to check on the whole website in an effort to identify outdated translations of her job. I would like to avoid this for obvious reasons but please let me know if you think it is necessary. I really hope you can fix this behavior so I won't have to ask the translator to check the whole website and to translate again the missing strings via a new work environment (wp admin panel --> WPML --> taxonomy translation) since such a thing would put an unnecessary financial burden on me and will delay the delivery of the whole website to my client. P.S.: don't mind the untranslated footer. I never assigned its translation to the translator. This is my bad.
October 25, 2023 at 7:55 am #14657725
Laura Supporter Languages: English (English ) Italian (Italiano ) Timezone: Europe/Rome (GMT+01:00)	The Advanced Editor uses xliff files, actually 🙂 I'll check the other missing translation but I suspect if I check in String Translation I'll find them untranslated, so we'll go back to the initial issue. Can you check with the translator if they ever user Taxonomy Translation or String Translation to ever translate anything?
October 25, 2023 at 8:02 am #14657761
anastasiosG-2	Thank for clarifying that Laura, I did not know. I asked the translator if she ever used Taxonomy Translation or String Translation and the reply I got was negative. I hope your team can provide a solution for the wrong source of WPML's translation on property features and for the untranslated strings of my previous message.
October 25, 2023 at 2:29 pm #14662213
Laura Supporter Languages: English (English ) Italian (Italiano ) Timezone: Europe/Rome (GMT+01:00)	I have some news. The bad one: the taxonomy behavior is actually expected. We're working to fix it, but for now the only way to update taxonomy translations is from WPML > Taxonomy Translation, any change done in the Translation Editor will be overwritten. As for the strings "Overview"/"Description", these are coming from an Elementor template called "Single Property" which hasn't been translated so it's expected they are not showing. Stuff like "Feature", "Property on map" etc are from the theme (they don't appear in ATE) so you need to find them in String Translation - see an example in the screenshot. Then you can translate them in String Translation directly or send them for translation like explained here https://wpml.org/documentation/getting-started-guide/string-translation/#translating-strings If there are some strings you can't locate, I'd suggest you try this feature: https://wpml.org/documentation/getting-started-guide/string-translation/finding-strings-that-dont-appear-on-the-string-translation-page/#enable-auto-register-strings I used it with the "Bedrooms" string and I could translate it. Let me know if this fixes the issue or if you need further assistance.
October 25, 2023 at 2:36 pm #14662415
anastasiosG-2	Hello Laura, Thank you again for coming back to me so fast. To be sincere, I wouldn't expect such problems (bugs) in a paid plugin that is active for so many years but on the other hand I understand that every single software out there has bugs and in the end of the day I do appreciate your honesty on it. For now, I will have to follow your guidelines which will add an economic burden on me. The worst thing is that in the feature, when I assign website translations I will have to instruct the translator to fill in the translations of the taxonomies both in the Advanced Translation Editor and the WPML settings on the wp admin panel so that each page's translation is 100% completed and therefore the translation memory will kick in and so that the translation is displayed correctly on the front end at the same time. Having said that, I hope your team will release a software upgrade as soon as possible so that no one will have to face this problem (again) in the future. Thank you again for your fast support! You can go ahead and close the ticket.
October 25, 2023 at 2:47 pm #14662441
Laura Supporter Languages: English (English ) Italian (Italiano ) Timezone: Europe/Rome (GMT+01:00)	I understand your frustration - actually fixing this issue is much more complex that one may think, due to how the Advanced Editor works, and that's why we didn't fix it yet. Just for you know, the same issue exists for image texts. I would suggest, if you need to translate more taxonomies, to instruct the translator to translate FIRST in WPML > Taxonomy Translation. If they do so, taxonomies will appear already translated in ATE so they won't need to translate twice. Of course, any changes should be always applied in Taxonomy Translation as well. Same for image texts - but by default these do not appear in ATE, you need to enable them first.