A view with two term-with-depth filters: it seems that the labels both get the same i18n locale_source location (e.g. Viewname:default:filter:node:term_node_tid_depth:expose:label), so the translations get mangled.
Similar issue with fields.

Comments

bart.hanssens’s picture

It seems that this has to do with views module (views\includes\handlers.inc) not passing the field's id to i18nviews (i18nviews\includes\i18nviews_plugin_localization_i18nstrings.inc), but rather the machine name of the type,

Most of the time that's just fine, but in some cases it does not work.
Say you have a content type with two vocabularies as CCK fields. Now, if one wants to create a tabular displaying the node title + two columns to display the terms of the two different vocabularies, the column labels both get the same "location" name.

I think it can be solved by a small patch in init() in views\includes\handlers.inc (+/- line 295), using $options['id'] instead of (or in addition to) $options['field'] as part of the localization_key array

bart.hanssens’s picture