Closed (fixed)
Project:
Internationalization Views
Version:
7.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Issue tags:
Reporter:
Created:
29 May 2011 at 03:41 UTC
Updated:
4 Jan 2014 at 00:53 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
webflo commentedA first version.
Comment #2
miro_dietikerAhhh great to see someone contributing here! :-)
I'll review this next week.
Comment #3
webflo commentedRerolled.
Comment #4
webflo commentedCommit e201085 on 7.x-3.x,
Comment #5
fietserwinThis patch is not correct. We may assume that i18n_taxonomy is enabled. Otherwise taxonomies are not translated at all and this whole functionality is void. However, i18n_taxonomy "takes over" ownership of taxonomy term reference fields by setting the 'module' property to 'i18n_taxonomy'. So the function i18nviews_field_views_data_alter() will miss the fields it want to alter.
In issue #1281704: Taxonomy terms are not translated in content create/edit form, I proposed a patch for the issue at hand (#14) and for translating taxonomies in Views exposed filters as well (#15). The part from #14 was accepted, but the additions in #15 were not, referring to this module.
Proposal:
If we can assume that i18n_taxonomy is indeed enabled, than the not incorporated part of #15 can be used to solve this issue. To do so we need to "complete" i18n_taxonomy in taking over the taxonomy term reference fields by implementing the Views hooks below as well.
The code to add:
What to change in this patch:
- change the line just above the addition, from its current version
to
- Remove the added handler altogether? Without looking in depth at what the filter does, my first impression is that the handler is not needed anymore, but I am not sure about that.
Comment #6
webflo commented@fietserwin: You are right.
Comment #7
webflo commentedFixed in commit 3cd6224 on 7.x-3.x.