When sending a content tree to translate with a new translation set it doesn't seem to find all the nodes on the first try.
As an example, for a tree with 25 nodes the send action had to be triggered 3 times. The first time finding 10 nodes, the second finding 16 (including the original 10) and then finally the third finding all 25 nodes.
Yes there is a slight bug in how Translation Manager is sending the nodes for translation the first time when the corresponding content doesn't exist on the target site.
It means the first /second time you asked for translations not all of the nodes where being created in the right order on your target language site, so where missing, but when you ran it again they where because the first pass had put some in.
Good news: this was down as a fix in the latest release and is in v1.3.1 which has just now being published.
Send to Translate not finding all nodes
Hi,
When sending a content tree to translate with a new translation set it doesn't seem to find all the nodes on the first try.
As an example, for a tree with 25 nodes the send action had to be triggered 3 times. The first time finding 10 nodes, the second finding 16 (including the original 10) and then finally the third finding all 25 nodes.
No errors in the log.
Hi David
Welcome to our the friendliest forum!!! What version of Umbraco are you using?
/Alex
Thanks :) Currently 7.7.6
Hi David,
Yes there is a slight bug in how Translation Manager is sending the nodes for translation the first time when the corresponding content doesn't exist on the target site.
It means the first /second time you asked for translations not all of the nodes where being created in the right order on your target language site, so where missing, but when you ran it again they where because the first pass had put some in.
Good news: this was down as a fix in the latest release and is in v1.3.1 which has just now being published.
Kevin
Hi Kevin,
Great! Thanks for the quick response.
Dave
is working on a reply...