the i18n block doesn't generate valid links, if the currently viewed node hasn't been translated already. in this case, you get to the same node with the new language-prefix => page not found error.

it would be nice, to get to an available translation of this node instead..

Comments

fago’s picture

fago
Primary language German
Location Vienna
commented
Version: » 4.6.x-1.x-dev
jose reyero’s picture

jose reyero commented
Status: Active » Fixed

You mean getting to a non-existing-yet "available" translation? :)

I think that if you install the latest 4.6 version, you wont be getting that page not found error anymore ?, but the same node, with translated interface.

Anonymous’s picture

(not verified) commented
jose reyero’s picture

jose reyero commented
Status: Fixed » Closed (fixed)

ok, no follow ups, guess the problem is corrected by latest bugfixes