Currently, multi-lingual blocks configured under Panels observe the multi-lingual switch. If I switch to another lanuage, the blocks under Panels will switch to that language as well. However, it isn't the case for page/story. So, could this be made multi-lingual aware as well? (Or did I make some mistakes when configuring Panels?)
Many thanks.

Comments

trantt’s picture

trantt commented
Title: i18n support » Translations block instead of Language switcher

I switched to Translations block and the same problem went away.

mine@subnet142.com’s picture

mine@subnet142.com commented

I tried with translation block and it still doesn't work. Just to be sure - I mean story/page inside Panels doesn't switch language. Story/page under Drupal does switch language as triggered by translation block.

What I could perceive is that Panels seems to hardwire to the NID for "post" configured under it. So, whichever language translation triggers, it's still the same NID. For "block" configured under it, if it is a multi-lingual block, the block container responds to the translation trigger. Actually, have further tried with books. Books, if not the bottom level node, which is the content page, books container also responds to the translation trigger.

Hope it clarifies?

fulster’s picture

fulster commented

Maybe the links are hardcoded but you can't access the translated node from panel anyway.
Instead of switching panel content language, you could even think about a translation management "a la" content (because you can think the news you post on the english side is not the same that on the french side) but it's not the case either.
Panels are simply not i18n aware at all.

Is there a chance to see that in a near future ?

best wishes !

catch’s picture

catch
he/him
Primary language English
commented
Status: Active » Closed (won't fix)

this is won't fix against 4.7 and I doubt the behaviour is the same for beta 2.