If the original content node hasn't been assigned a language, any translations added will lose their connection to the original item. Similarly, attempting to re-link a translation to a node without a language assigned will also fail.

It would be nice if this wouldn't be a requirement, since I can see it being a substantial source of frustration for end users.

Comments

jose reyero’s picture

jose reyero commented
Title: Lost Translations » Translation tab showing for nodes with no language
Priority: Normal » Minor

IMHO, having a node without language translated doesn't make any sense.
So I think the real bug is showing the 'translation' tab -I renamed this issue accordingly

mandclu’s picture

mandclu commented

I see your point, but there will be users that don't see the translations tab and don't know why. I think it would be better to still show the tab, but if the original item hasn't been assigned a language, going to the translations tab will show an error stating that the content must be assigned a language first.

jose reyero’s picture

jose reyero commented

Ok, I like this latest idea.
I'll look into it.

jose reyero’s picture

jose reyero commented
Status: Active » Fixed

Finally went for the solution suggested. Hope you like it :-)

Thanks

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)