Translation Manager - unable to translate pages to unpublished culture

Hi everyone,

I am running Umbraco 13.12.1 with Translation Manger 13.2.19. My setup is using culture variants with single content tree. But I have 3 content trees for different purpose. Main content is on one of the tree.

On the translation tab, when I tried to create a translation job for a page, which is published in the default culture/language but not in the target culture/language, as the screenshots below shows. Then I got into an error: Error one or more nodes could not be created - pages may not be correctly linked, or there may be no content to translate for these pages.

Once I published the targeted culture for that page, it has no problem to create the translate job. Do I miss configured anything? I remember a few weeks ago, I was able to create translation jobs even the targeted culture for that page is unpublished.

Hi,

If the languages are all on the same tree (so using variants) then it shouldn’t matter if they are published or not, as the content goes back into the same content node (just in a different place).

The error you see should only ever pop up if the target languages are in a different content tree to the source ones. and the parent content nodes haven’t been translated or linked together (underneath it’s all using the relation serivce).

I would double check if the content is all going to the same nodes that the master and targets for the set are the same content node (e.g the homepage).

if you are trying to translate between content trees it might be worth sending the parent nodes to translation first then the children should be ok. or you can use the “Linked Pages” package to manually put the links between the content nodes.

1 Like

Thanks Kevin.

My translation set is targeting the same node as the following screenshots shows.

Could the database be messed up at some point? I deleted the translation set and re-create it again and it didn’t help either.

It turned out there is an implementation of TranslationNodeCreatingNotification in the repo, which stopped the unpublished nodes to be translated.

Thanks for your help @KevinJump again.