Running the latest version of TM (2.1.2) on Umbraco 7.12.3
It works great!
There is a feature shown in the video where after an initial translate job, the Pending Changes shows only the field(s) edited.
However in my install, editing any field on the items results in all the text fields being listed in the Pending changes. Is this a known issue?
If so then I assume that if this can be fixed then it would also affect the Send to translate screen - i.e. only send the new/amended fields through to the translator?
It should work like in the video, but you are right there does appear to be a bug there in the latest version. We will look to get a fix for this done asap.
When it is working the pending items will collect over time and you can send them from pending, but the 'send to translate' option on the content menu will always send the whole set of content to be translated
We haven't yet found a nice way of displaying only the changes in that mode mainly because space is quite restricted so the pending section offers a better chance to see what's going on - but we are open to suggestions.
In our scenario there are likely to be too many items and languages to keep track of using the Pending section.
I think they will instead make a minor change to the master content of a particular item and then want to send that item to translate. But currently it will be less than ideal for the translator to have to edit/confirm every field that has already been translated.
Perhaps a tick box on the first step of the 'Send to translate' that says 'only include changed fields'?
Or in the translator view, a way to bulk accept the existing translated copy if it has already been translated previously?
Just pushed version 2.1.3 which fixes the pending issue - so only the things that have changed end up in pending.
We have added the 'only include changed fields' feature to the list for the next release (v2.2) - which we are currently working on - it will probably be a setting or set setting thing (so something you have to pick for it to be to appear), and we are going to work on the best way of telling the user what will actually be included.
Subsequent translation job showing all fields
Hi,
Running the latest version of TM (2.1.2) on Umbraco 7.12.3
It works great!
There is a feature shown in the video where after an initial translate job, the Pending Changes shows only the field(s) edited.
However in my install, editing any field on the items results in all the text fields being listed in the Pending changes. Is this a known issue?
If so then I assume that if this can be fixed then it would also affect the Send to translate screen - i.e. only send the new/amended fields through to the translator?
Thanks, Andy
Hi Andy,
It should work like in the video, but you are right there does appear to be a bug there in the latest version. We will look to get a fix for this done asap.
When it is working the pending items will collect over time and you can send them from pending, but the 'send to translate' option on the content menu will always send the whole set of content to be translated
We haven't yet found a nice way of displaying only the changes in that mode mainly because space is quite restricted so the pending section offers a better chance to see what's going on - but we are open to suggestions.
Kevin
Thanks very much.
In our scenario there are likely to be too many items and languages to keep track of using the Pending section.
I think they will instead make a minor change to the master content of a particular item and then want to send that item to translate. But currently it will be less than ideal for the translator to have to edit/confirm every field that has already been translated.
Perhaps a tick box on the first step of the 'Send to translate' that says 'only include changed fields'?
Or in the translator view, a way to bulk accept the existing translated copy if it has already been translated previously?
Thanks Andy
Hi
Just pushed version 2.1.3 which fixes the pending issue - so only the things that have changed end up in pending.
We have added the 'only include changed fields' feature to the list for the next release (v2.2) - which we are currently working on - it will probably be a setting or set setting thing (so something you have to pick for it to be to appear), and we are going to work on the best way of telling the user what will actually be included.
Kevin
Fantastic support - thanks so much!
is working on a reply...