Posted by nhck on October 29, 2009 at 12:38pm
| Project: | NodeReferrer |
| Version: | 6.x-1.x-dev |
| Component: | Miscellaneous |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
| Issue tags: | i18n, multilanguage |
Issue Summary
What are your suggestions on fixing this problem:
Setting
I created a field its called
field_animalfarm
I created some nodes which all refer to field_animalfarm:
- Cat - this one is originally in language "de", translatable, but no translated
- Donkey - this one has no language
- Monkey - this one is originally in language "en", translatable, but no translated
- Sheep - this one is originally in language "de", translatable and translated
Current State
When I open my view using the default "de" language I get this list:
- Cat
- Donkey
- The de-string for Sheep
When I open my view using the "en" language I get this list:
- Monkey
- Donkey
- The en-string for Sheep
Expected Result
What I would like to see in "de"-language view is:
- Cat
- The en-string for Monkey since its not translated
- Donkey
- The de-string for Sheep
and in the "en"-langugage view:
- The de-string for Cat since its not translated
- Monkey
- Donkey
- The en-string for Sheep
Solutions tried
I tried to rewrite the queries however the are pretty complex..but this seems the way to go.
I also tried the option Include translations of referrers however this only gives me the en-string for Sheep and the de-string for Sheep in both views.
Comments
#1
oh my.. translation... this is a main problem - I've no time to test this feature. when views support was added nobody cares about about multilingual so I just add same code as node_reference
If you find a time to work on this glad I'm to commit because nobody touch this before
#2
Hmm, actually that was a support request.
The problem is the WHERE-Clause that i18n adds. It just doesn't live up to the complexity of this query. So I decided to split the current query.
I created a hack, but without an option in the administration screen its going to cause unexpected behavior for some users. I guess there should be an option to switch this on/off - or an option in i18n to apply the language clause a little different. Maybe we can get some help from over there?
So some work to do there. Still I am providing this right now for users that would like to see untranslated Referrers of the translated Version of the node.
What do you think about getting using this for the module?