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?

CommentFileSizeAuthor
#13 nodequeue-i18n-compatible-1328602-13.patch3.12 KBFerrari
#11 nodequeue-problem_with_translated-node-1328602-10.patch607 bytesrajneeshb
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Anonymous’s picture

Anonymous (not verified) CreditAttribution: Anonymous commented

Same 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...

SELECT node.nid AS nid
FROM 
{node} node
INNER JOIN {nodequeue_nodes} nodequeue_nodes_node ON node.nid = nodequeue_nodes_node.nid AND nodequeue_nodes_node.qid = '5'
WHERE (( (node.type IN  ('header')) AND (node.language IN  ('nl')) ))
ORDER BY nodequeue_nodes_node_position ASC
LIMIT 3 OFFSET 0

Only the original English nodes are in the queue. So what is that setting "Treat translation nodes as a single node " supposed to do?

Anonymous’s picture

Anonymous (not verified) CreditAttribution: Anonymous commented

Temporarily solved by using "Manually manage translations" and adding them.

chefnelone’s picture

chefnelone CreditAttribution: chefnelone commented

I can't do this since I have around 150 nodes...
Any light on this, please.

Anonymous’s picture

Anonymous (not verified) CreditAttribution: Anonymous commented

I 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...

chefnelone’s picture

chefnelone CreditAttribution: chefnelone commented

thanks, I'll try another module to do this.

amateescu’s picture

amateescu CreditAttribution: amateescu commented
Assigned: Unassigned » amateescu

I will take a look at this in a few days, hopefully before the week ends.

chefnelone’s picture

chefnelone CreditAttribution: chefnelone commented

Thanks amateescu, I really appreciate it!

amateescu’s picture

amateescu CreditAttribution: amateescu commented

I'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.

chefnelone’s picture

chefnelone CreditAttribution: chefnelone commented

I will.

micamou’s picture

micamou CreditAttribution: micamou commented

I'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

rajneeshb’s picture

rajneeshb CreditAttribution: rajneeshb commented
Assigned: amateescu » rajneeshb
Issue tags: +languages, +nodequeue
FileSize
nodequeue-problem_with_translated-node-1328602-10.patch607 bytes

I 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,

kirie’s picture

kirie CreditAttribution: kirie commented

I can confirm that the approach outlined in #982382-18: Multingual Nodequeues - Displaying nodes based on language works

Ferrari’s picture

Ferrari CreditAttribution: Ferrari commented
Status: Active » Needs review
FileSize
nodequeue-i18n-compatible-1328602-13.patch3.12 KB

I 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.

The last submitted patch, nodequeue-i18n-compatible-1328602-13.patch, failed testing.

Anonymous’s picture

(not verified) CreditAttribution: commented
Issue summary: View changes

more info

ddrozdik’s picture

ddrozdik CreditAttribution: ddrozdik commented

any updates of this problem?

ameymudras’s picture

ameymudras CreditAttribution: ameymudras commented
Issue summary: View changes

Guys 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!

ameymudras’s picture

ameymudras CreditAttribution: ameymudras commented
Status: Needs work » Needs review
joep.hendrix’s picture

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.

ksenzee’s picture

ksenzee
she/her
Location Seattle area
CreditAttribution: ksenzee at Smartsheet commented
Status: Needs review » Reviewed & tested by the community

#16 is exactly right and should probably be documented somewhere.

fizk’s picture

fizk CreditAttribution: fizk commented
Status: Reviewed & tested by the community » Closed (works as designed)

Closing, based on #16, #18, and #19.