Press Ctrl / CMD + C to copy this to your clipboard.
Copied to clipboard
Flag this post as spam?
This post will be reported to the moderators as potential spam to be looked at
Topic author was deleted
Nov 05, 2018 @ 09:54
Only top node is part of task (not finding unpublished descendants)
Hey,
I'm just testing this package since we have a site that needs to be translated. I'm using the latest version 2.1.2
Here is my content setup:
So I'm trying to translate the EN (unpublished) from NL
I've made the translation set
But when I send to translate from the content context menu, the dialog seems to loop trough all descendants but when I view the task it only contains the homepage
Are the sub nodes beneath en related to the ones in NL (e.g where they created with copy / include descendants?)
If they are not related then it won't be able to work out what should happen (but equally it will create new nodes if that is true)
You don't need the content tree beneath the target language before you start as it will be created as part of the translation job (but if its related you can have it)
Do the child nodes in NL have anything in them to translate at the moment? If they don't have any text values in them then they won't appear in the job as they would be "blank" - the default setup is not to include blank items in the translation job (you can change this in the settings section)
Topic author was deleted
Only top node is part of task (not finding unpublished descendants)
Hey,
I'm just testing this package since we have a site that needs to be translated. I'm using the latest version 2.1.2
Here is my content setup:
So I'm trying to translate the EN (unpublished) from NL I've made the translation set
But when I send to translate from the content context menu, the dialog seems to loop trough all descendants but when I view the task it only contains the homepage
Hi
Are the sub nodes beneath en related to the ones in NL (e.g where they created with copy / include descendants?)
If they are not related then it won't be able to work out what should happen (but equally it will create new nodes if that is true)
You don't need the content tree beneath the target language before you start as it will be created as part of the translation job (but if its related you can have it)
Do the child nodes in NL have anything in them to translate at the moment? If they don't have any text values in them then they won't appear in the job as they would be "blank" - the default setup is not to include blank items in the translation job (you can change this in the settings section)
Kevin
Comment author was deleted
Thanks for the details Kevin, that works now!
is working on a reply...