I'm using Title module with Entity translation to translate my taxonomy terms.
I have overridden my term page with a view with term id as contextual filter.
In the contextual filter section, I'm overriding the title view page with the contextual filter %1.
I'm validating the contextual filter by checking if it's a term id.
Unfortunately the title page is not translated. In my case term name displayed is always the one in English.
Just to test further, if I'm adding 2 fields term name and term description to my views. The 2 fields are correctly translated, by switching languages.
| Comment | File | Size | Author |
|---|---|---|---|
| #13 | views-overridden_term_name-1914024-13.patch | 1.75 KB | peximo |
| #11 | views-overridden_term_name-1914024-11.patch | 1.71 KB | peximo |
| #1 | HasTaxonomyTermId.PNG | 6.42 KB | heyyo |
Comments
Comment #1
heyyo commentedAnyone on this ?
Maybe my issue is no related to Title module, maybe more to Entity Translation or Views ?
It is possible to do that when using regular taxonomy with Internationalization and Internationalization Views module.
http://drupal.org/node/1541924
Comment #2
plachIf I'm not mistaken this is a Views issue, the related code is probably not using the proper API to display the term name. See #1651726: Use entity_label instead of term name for term reference exposed filters for a similar issue.
Comment #3
heyyo commentedComment #4
dermyrddin commented@heyyo do you get any progress with this problem?
I encountered the same difficulties.
Comment #5
plachI think the translations component refers to the UI translations.
Comment #6
heyyo commentedThe only solution I found is to override the views template and override the title there with my term name.
Comment #7
plachComment #8
merlinofchaos commented#1651726: Use entity_label instead of term name for term reference exposed filters looks related to this, but is probably not precisely the same issue (though it's fundamentally the same concept, just a different location).
Comment #9
merlinofchaos commentedFor this issue, the problem is going to be in views/modules/taxonomy/views_handler_argument_taxonomy.inc on line 23. The patch should be trivial.
Comment #10
dermyrddin commented@plach, I've seen this thread, but the solution is too complicated for me :(
@merlinofchaos, I think this is not correct place.
I've tryed to comment out "return check_plain($term->name);" string, but tem name stays on it's place:
http://cl.ly/image/2J1Q3p0r423q
Term name is displayed in original (Russian) language.
This is view which overrides "/taxonomy/term/%" path:
http://cl.ly/image/0L433L1M1216
Comment #11
peximo commentedHi, this should fix the issue. I used this solution in several projects and it should be right.
Comment #12
dermyrddin commented@peximo, thank you!
Your patch solves the issue.
Comment #13
peximo commentedSorry a little change: added back the check plain.
Comment #14
plachI think it makes sense to add the
check_plain()sinceentity_label()returns a raw value at least when dealing directly with an entity property. Looks good to go to me and we have a confirmation that this works.Comment #15
dawehnerEntity_load here is certainly not an often called operation, so there is no reason to not commit it.
Thanks for writing the patch!
Comment #16
yannickooThere is a problem when using taxonomy_term_load and the machine name, created a follow-up issue: #1949178: Notice: Undefined property: stdClass::$machine_name in views_plugin_argument_validate_taxonomy_term->validate_argument() (line 1.
Comment #17.0
(not verified) commentedtypo