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.

This topic contains 2 replies, has 2 voices.

Last updated by marketingD-3 3 months, 2 weeks ago.

Assigned support staff: Bruno Kos.

Author Posts
June 18, 2019 at 8:29 pm #4046395

marketingD-3

Hello,

In the past we tested the WPML functionality for when we request some pages to be translated, then we update the original page. In the past, the translators will see the page as how it was when translation was requested. They will show as: Waiting for translator (Needs update) and when the translation has been entered it will change to Complete (Needs update)

Now, we are seeing that when a translator clicks on "Translate" button and gets to ATE, they will see the latest content of the page requested (including updates made after we requested translation in translation manager).

We really want to always present our translators the page at the point when it was requested, meaning, do not include updates made to the original page.

We are not sure if with a plugin update this feature was changed in WPML, or it was moved as a setting configuration (but I can't find it). Or maybe we are facing a bug in our website that prevents the original behavior we expect.

In addition, how will the import XLIFF functionality work if the original page has been updated?

Thanks in advance.

June 19, 2019 at 10:40 am #4050791

Bruno Kos
Supporter

Languages: English (English )

Timezone: Europe/Zagreb (GMT+02:00)

Hi,

Thank you for contacting WPML support!

We really want to always present our translators the page at the point when it was requested, meaning, do not include updates made to the original page.

I'm afraid that this is not possible due to how core translation management works - if you update the original while it is in the translation job, this job will get a status “Complete – (needs update)” or perhaps Waiting for translator (Needs update), meaning that translator will see these new fields.

I'm not sure how this worked before or if it worked in a way you said it did. However, you can see the changelog here on how development of TM has progressed:
https://wpml.org/download/wpml-translation-management/?section=changelog

So I can imagine that your idea would be to limit how much content can translators see within the translation editor and that is not possible. You could perhaps assign them specific strings to translate from string translation and not through translation management - this way they will only be able to translate strings you assigned to them and no new content.
https://wpml.org/documentation/getting-started-guide/string-translation/#translating-strings

In addition, how will the import XLIFF functionality work if the original page has been updated?

An XLIFF file will be generated upon the translation job creation. If you update your original page, XLIFF file will not change - it will only change if you edit the translation, which is an action that will render new translation job and new XLIFF file.

Regards,
Bruno Kos

July 2, 2019 at 2:29 pm #4127901

marketingD-3

Thank you Bruno for clarifying that point.