Block multilingual settings ignored by panels layout

subs

I have the same problem as the original poster:
Multilingual site with i18n and language switcher activated.
Translated blocks outside panels work fine.
Language restricted views inside panels work fine (view filter: language = user language).
Translated nodes inside panels work fine.
Translated blocks inside panels don´t work: the original language of the block is always used, no matter what language the user is switching to on the site using the language switcher.

Workaround for me is to created a custom content type for the content that was originally created as a block, but would be nice to have the translation working for blocks as well. All under the assumption that I am not missing something.

Is block translation provided by a module? I have no idea how block translation works or at what point.

Perhaps it's only handled properly if you set the style to system block?

Same problem here, Panels ignore string translation.

Perhaps it's only handled properly if you set the style to system block?

@merlinofchaos , that was a pretty good "guess", if you had no idea. Simply changing the style worked :)!
This whole issue is pretty weird, especially since views-blocks translations worked in panels with any style.

Marking as fixed.

don't work for me :(

but I noticed that panel dosn't change language variable $node->language so I've fix this by hook_nodeapi in panel.module file:

function panels_nodeapi(&$node, $op, $a3 = NULL, $a4 = NULL) {
	if($op == 'load' && $node->type == 'panel') {
		global $language;
		$node->language = $language->language;
	}
}

This doesn't make any sense to me either. Worse, it's not really related to the original issue (Yes, both are about translation, but #7 is about panel nodes and the rest is about blocks).

Returning to previous state; if you wish to continue with this, please file a new issue. Also, you may need to be explicit in detailing what is wrong and how you think this fixes it. My gut feeling is that this is not right, and that core is supposed to be setting $node->language for us.

Hello Merlin, I got the same issue then #1 on my website, even not fully in the same logic : in my website, custom blocks defined as "translatable" and translated stay in default language while moving from one language to another. I try, as in #1 to put in in "english" to see then if it is possible to assign on block per language in my panel, but i got the same result : a block defined as "english" is still displayed whatever the language is set.

System block style solved the issue for me. Thanks!

For me #11 step 2 worked out fine.
Thx for this post!

Same issue for D7, but changing pane style to system block doesn't fix the issue.
I'm not sure that options from #11 apply - I can't find any multilingual settings for panels.

halp!

I see now that comment #11 is referring to panel nodes.
I'm having trouble with regular old panels pages not respecting multilingual settings, which is what i thought the OP was about.

I tried #11 option 1, but no effect.

What I saw is that:

- The translation doesn't work if the block is assigned to a theme-region and you try to show it in a panel-region.

- The translation works if the block is not assigned to a theme-region.

I'm running into the same problem as espurnes https://www.drupal.org/node/784648#comment-8244413

- Using the Block languages sub-module from i18n (1.11).
- Panels (3.4)

Using a block I added (title and body set to 'Make this block translatable') and translated to French. The block is added to one of the theme's regions.

When I use that same block in a panel page the block stays in English. As soon as I remove that block from the theme region it was in, the block on the panel page actually shows the correct French translation.

A work-around would be to duplicate that block for the time being, but a fix would be better :P If it's fixable by Panels though and not a core issue?

Marking this as duplicate of #1168272: Drupal blocks are shown untranslated.