Implements a translation support like for nodes.

Comments

funana’s picture

funana commented

Yes! This is a very important feature.

If you have a multiple language page and want english users to only see the english blocks and italian users to only see the italian ones - this feature is needed.

With i18n you could work around (due to the fact that the "language block" feature didnt work) this via URL strings: Show block only on /en/ pages for english, show block only on /it/ for italian.

Looking forward to see this feature!

Roberto Gerola’s picture

Roberto Gerola commented

I have taken a look to block api.

It seems to me not too complex to implement.
I'm thinking to one configuration option per block where you can specify
the language, or better, one multiple choices where you can specify
in which languages this block should be visible.

I have one doubt : which language should drive the blocks visibility ?
Content language or interface language ?

funana’s picture

funana commented

Great!

I have no doubt that content language should drive the blocks visibility. It is teasered conent and therefore it has to be handled as content.
Just with the title of the blocks, there should be another handling. It has to be translatable too, and this field has to be handled by the navigation language option.

One multiple choices where you can specify in which languages this block should be visible would be great!

hass’s picture

hass commented

hi

i think a block should use the content language of the current page... if not - very bad for search engines...

Regards
Alex

Roberto Gerola’s picture

Roberto Gerola commented
Assigned: Unassigned » Roberto Gerola
Status: Active » Closed (fixed)

Closed in release x.6