I create a queue called: Flats which contains nodes of the Flat type.
Then I checked: Treat translation nodes as a single node
Finally I created a view and adde Flats queue as a relationship. So far so good.
But I have these node in english and spanish languages. So I added this filter to the view: Content translation: Language (= Current user's language)
But the view only show the nodes for the language which I added in the Queue, but not for its translations.
If I change to check: Manually manage translated nodes and then add manually the nodes it works fine. But this is massive work for my site.
What am I missing here?
Comment | File | Size | Author |
---|---|---|---|
#13 | nodequeue-i18n-compatible-1328602-13.patch | 3.12 KB | Ferrari |
#11 | nodequeue-problem_with_translated-node-1328602-10.patch | 607 bytes | rajneeshb |
Comments
Comment #1
Anonymous (not verified) CreditAttribution: Anonymous commentedSame problem! I hae the same setup, but nodes of different translations are invisible to views.
Views coughs up this query and finds no Dutch nodes, because the Dutch language node ids are not in the queue table...
Only the original English nodes are in the queue. So what is that setting "Treat translation nodes as a single node " supposed to do?
Comment #2
Anonymous (not verified) CreditAttribution: Anonymous commentedTemporarily solved by using "Manually manage translations" and adding them.
Comment #3
chefnelone CreditAttribution: chefnelone commentedI can't do this since I have around 150 nodes...
Any light on this, please.
Comment #4
Anonymous (not verified) CreditAttribution: Anonymous commentedI think nodequeue needs to hook into the views query and add another left join to get the nids of translated content. Seems hard to do...
Comment #5
chefnelone CreditAttribution: chefnelone commentedthanks, I'll try another module to do this.
Comment #6
amateescu CreditAttribution: amateescu commentedI will take a look at this in a few days, hopefully before the week ends.
Comment #7
chefnelone CreditAttribution: chefnelone commentedThanks amateescu, I really appreciate it!
Comment #8
amateescu CreditAttribution: amateescu commentedI'm sorry but I couldn't get the time to look into this issue.. Maybe you can try the workaround from here #982382-18: Multingual Nodequeues - Displaying nodes based on language in the meantime.
Comment #9
chefnelone CreditAttribution: chefnelone commentedI will.
Comment #10
micamou CreditAttribution: micamou commentedI've had the same problem ordering the translated nodes according to the original language ordering and made a quick and dirty fix inside the module :
in the file
/nodequeue/includes/views/nodequeue_handler_relationship_nodequeue.inc
on line 74 I modified the join query from
'left_field' => 'nid'
to'left_field' => 'tnid',
This works since the translated nodes reference the partent node ID with this column AND the parent node references ITSELF so it works all the time.
BE careful this only work when the original node IS translated in at least 1 other language!
Good luck
Comment #11
rajneeshb CreditAttribution: rajneeshb commentedI also faced same problem and resolve it by making changes according micamou.
This only work when the original node is translated in at least 1 other language.
I have created patch for same. PFA for patch.
Thanks,
Comment #12
kirie CreditAttribution: kirie commentedI can confirm that the approach outlined in #982382-18: Multingual Nodequeues - Displaying nodes based on language works
Comment #13
Ferrari CreditAttribution: Ferrari commentedI tested the patch earlier but he did not fit coherently my use-case.
After applying the current patch it started listing out all translations from that node.
To adjust this I made a new patch that addresses this peculiarity.
Comment #14.0
(not verified) CreditAttribution: commentedmore info
Comment #15
ddrozdik CreditAttribution: ddrozdik commentedany updates of this problem?
Comment #16
ameymudras CreditAttribution: ameymudras commentedGuys there is a simple way of doing this. Please follow the below steps:
1. In the views add relationship of the "source translation"
2. below that add another relationship of node queue and select the relation of "source translation".
3. Add a filter node queue : in queue.
4. Add a filter for node language as current users language.
This should solve the problem without any patch!
Comment #17
ameymudras CreditAttribution: ameymudras commentedComment #18
joep.hendrix CreditAttribution: joep.hendrix at CompuBase Internet Solutions commented#16 works nicely.
Thanks!
However, some queues work without the extra relationship.
I guess it is a bug.
Comment #19
ksenzee#16 is exactly right and should probably be documented somewhere.
Comment #20
fizk CreditAttribution: fizk commentedClosing, based on #16, #18, and #19.