This issue is related to other glossary issues reported to Alejandro on ticket number 12257999. Please can this ticket be referred to Alejandro?
1. The whole sentence which has glossary entries is not translated. There are multiple entries for 'job' in the glossary, which is 'project' in French. See screenshots showing where 'job' is translated correctly and where it is not translated (see below). hidden link
Here is the article link hidden link
2. Here is another example where the whole sentence is not translated where the 'Job' is in the glossary. hidden link hidden link
3. A sentence with no glossary entries is not translated. There are other situations where the translation is not done. If I test the sentence using Google Translate, it works correctly. hidden link hidden link
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+01:00)
Hello!
1) Can you please send me the glossary entry you have in your site? this way i can compare it with the translation editor Job for the page "hidden link" and understand better what's going on.
2) This point is related to point 1, correct? can you please write the steps you took to recreate the problem? this way i can also test this on our staging and test servers to see if this is a problem that is fixed in our next ATE update.
3) I'm not understanding this statement. if you do not have a glossary entry, then it doesn't translate but if you do have a glossary entry, then it translates the content? (i'm trying to understand this better since it seems like a contradiction from point 1 and 2)
Let me know please so i can start running a few tests.
Item 1 - 'Job' and 'Jobs' are in the glossary (see the first screenshot). In the article, the first sentence, which has 'Job' in it, is not translated. In the second sentence, where 'Job' is used multiple times, the translation is correct and 'Job' is translated from the glossary, which is 'Projet' (see the second screenshot). hidden link hidden link
Item 2 - This is a similar issue where the whole sentence which contains the glossary entry for 'Job' is not translated.
Issue 3 - This is a general issue we see where whole sentences are not being translated, independent of having a glossary entry. If the same content is translated by going directly to Google Translate outside of WPML, the content gets translated. So it appears that Google recognises the content and translates it correctly.
Please let me know if you require additional information.
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+01:00)
On our end this is what i see: hidden link
This job came from May 2, it was automatically translated and in our editor it appears to have the glossary entry recognized and translated correctly and also the entire segment translated.
However, i've seen cases where the translation editor shows something but the content is not translated in the front-end and that only happens when the page is modified in any way before the job is uploaded.
If you do the following on the page in question (/knowledge-base/contract-maintenance/), would the segment appear as empty in the translation editor, translated correctly, or something else?
- Please edit the page in the original language (English)
- Add a character to the title
- Save the changes
- OPTIONAL: Remove the character and save the changes again
- Edit the translation
- Check if it appears 100% translated and check if it appears in a darker greenish blue color (automatically translated) or in a light green one (Translated manually).
- Click "complete" button
- Wait a few seconds until the icon of the language, under the "languages" tab, shows a pencil icon.
- Check the front-end now and check if it appears translated correctly or if the content is not translated yet.
I added WPML to the title of the article and followed your steps. The translations did not work. Please see the screenshot showing this hidden link
The steps I followed for the auto translate are 1) Select the article on the dashboard and add it to the Translation Basket, 2) Send the item for translation from the Translation Basket and 3) In Bulk Auto Translate, select Translate Automatically.
I created a new article and have an example where a glossary entry does not translate correctly consistently. Please see the screenshot hidden link
Here is the link for the article hidden link
Please let me know if you need additional information.
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+01:00)
Would it be possible to have access to the site in question of the testing (it seems to be a staging server) so i can try to check what could've happened.
I'm mainly going to check revisions and probably create a few similar pages and test translations with it.
Every credit i use will be reimbursed right after the tests on my end (and i'll also re-add the credits you used for these tests from the screenshots).
We would be happy to provide you access to this staging site. I think we have already provided WPML with access to this site. It may have been someone else on your team.
Unfortunately, our IT specialist for WordPress is at an off-site conference this week, so it will likely not be until this Friday that he will be able to set you up with access.
Apologies for the delay ... please can you put this ticket on hold until the end of the week.
We appreciate your assistance in checking our issues.
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+01:00)
Of course! it's not a problem. i don't see any other ticket open but if there's an user you can use here, then i think you can just edit the user from users > View users > Select the user you wish to edit and click "edit".
Then you can click "reset Password" and a field will appear with the new password which you can copy and paste in our credential fields.
However, we can wait without issues, it's not a problem 🙂
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+01:00)
Were the changes done with the user "benjenk..."?
That user was missing info on their profile and was triggering a few issues because he was set as a translator.
I edited it and filled name and last name to have this fixed.
I checked the site but:
1) the first link you sent me seems to have been filled only in the staging site and not the site you gave me access to so the editor was empty there and I couldn't verify anything.
This statement applies to the point 1,2,3 from your first reply. I suspect the problem is the same as my following point since the patterns seems to relate.
2) the problem with the link missing is because if you edit that job, you'll know it's not set as complete and it doesn't have a link assigned. I'm asking our Devs how could this have happened but can you tell me of you edited that page in ATE manually and left it like that on purpose, by any chance or if it appeared as translated before (it's the yellow one, set as a "draft" segment) ?
Thanks for changing the Profile. I will ask Ben, our IT specialist, to check which Profile was used for the changes, and I can let you know.
Regarding the missing link, I made the change to the English article through the regular editor, and then I did an automatic translation through the Dashboard. I would appreciate you checking why it did not work for the translation.
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+01:00)
I think i know what happened and maybe how to fix it.
It's a bit difficult to explain without visual input so i created this video for you: hidden link
It seems at one point one entry remained as a draft, so all the future segments created with the same content would be set as a draft as well. drafts are ignored by the automatic translation because they mean you're "working on it" so as a result you got the content as it was set in the draft (translated but without the HTML Markers).
resend the job, preferably from translation management > Dashboard, and then assign it to a translator, edit it and then add the markers. set it as complete and you should see the links there.
do the same for the glossary entry pages and let me know if that fixes all the issues this time.
1. Regarding the issue with sentences not translating, I updated an article on the Staging site earlier this week. I added WPML to the original title. The article link is hidden link
- For this article, 'Job' and 'Jobs' are in the glossary (see the first screenshot). The first sentence, which has 'Job' in it, is not translated. In the second sentence, where 'Job' is used multiple times, the translation is correct and 'Job' is translated from the glossary, which is 'Projet' (see the second screenshot). hidden link hidden link
2. Regarding the article with the missing link in French, I initially added it (with Profile Jane Michalow), and then Ben Jenkins reviewed it and saved it again. In both cases, we edited the article with the standard WP Editor in English to add the link. We did not edit it using the ATE editor. I think you can see the link does not work in the French version of the article. hidden link
The article link is hidden link
3. We uncovered a new issue in our testing where the category hierarchy not holding on the French site. We use Heroics to manage the categories. In the screenshot, 1) you can see the article hierarchy on the Dashboard and 2) the category hierarchy on the French site. Creation de Facture is not showing correctly as a sub-category hidden link
I hope this provides you with the information you need to take a look at the issues. Please let me know if you require any additional information.
Thanks again for your assistance.
Jane
New threads created by Alejandro and linked to this one are listed below:
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+01:00)
In order to have the problems field we have to focus on one issue at a time, or we won't be able to understand each other.
let's focus on this one for now:
we edited the article with the standard WP Editor in English to add the link. We did not edit it using the ATE editor.
The translation is in "french", but you edited the content in English, which is ok (you can't really update or modify the original language of the page in the translation editor).
However, the translation that you currently see in french, is the one coming from the translation editor, which i suspect you first sent to translate automatically and then reviewed manually. in the information we have this is the scenario that seemed to have happened:
You translated the content using ATE (it could be you sent it to translate automatically from WPML > Translation Management, opened ATE and clicked "translate automatically", reviewed it later or translated it manually by clicking "complete" on each segment when you finished)
However at one point, wether it was done using automatic translation or manually, the segment affected was saved as a draft and didn't get updated. the draft was missing the HTML markers which turned out to be LINKS.
now, the drafts were created because of any of these reasons:
- you had this segment in other pages and when reviewing or translating them, you never hit the "complete" button, so it got switched to a draft
- In the following pages, whether you opened them manually using ATE or via the automatic translation, our system would ignore the drafts and not translate them (this is NOT a bug, we ignore such segments to avoid overwriting content that you are editing).
- At one point you used the automatic translation from WPML > Translation management and the translation got retrieved to your site, but with the "change" left from the draft. the translation was done but the markers weren't added and as a result, you had the content translated without the links.
I double checked everything, even past jobs, to determine what happened and the scenario mentioned here, is the only one that fits the data we have (We checked with our developers as well, to have more info on the matter).
The same answer from the link above this paragraph is the only way to have this fixed and you have to access the advanced translation editor to do so.
