Nodequeue / Flag translations not displaying in a view

subscribing

i'm using the latest dev version together with translation helpers (drupal 6.10, php5 mysql5)

even if i choose "Treat translation nodes as a single node" when i switch to a language i can only see the original nodes (i see an empty page for the other languages.)

Can you clarify where the translated nodes are not appearing? They're not appearing in the View of the queue, or on the queue manipulation page? If the View is giving you the unwanted behavior, can you paste an export of the view here?

Based on the patch to i18n that got applied a long time ago, I would think that displaying the translated node in a view would be handled by i18n's db_rewrite_sql. However, I do notice that the current user's language Views filter adds an "AND (node.language in ('***CURRENT_LANGUAGE***'))" to the query, which won't work if the original node is in one language and the translation language is therefore note stored in node.language.

Once you clarify which problem you're having, we can pursue this further, probably in the i18n issue queue as a support request.

i don't if this message was for me but i'll try to explain my problem.
i use the latest dev version of the 6x branch together with the latest version of views2 and translation helpers.

the goal is to have a unique queue for all supported language. So in this way i have to add only one node to the queue. when i click on the translation flags the queue has to show that node in the correct language.

I created the queue checking the "Treat translation nodes as a single node" option, then I added 4 nodes to the queue.
I modified the queue through views to display the fields i want, here is my view.

$view = new view;
$view->name = 'nodequeue_1';
$view->description = 'Display a list of all nodes in queue \'notizie "in evidenza"\'';
$view->tag = 'nodequeue';
$view->view_php = '';
$view->base_table = 'node';
$view->is_cacheable = FALSE;
$view->api_version = 2;
$view->disabled = FALSE; /* Edit this to true to make a default view disabled initially */
$handler = $view->new_display('default', 'Defaults', 'default');
$handler->override_option('relationships', array(
  'nodequeue_rel' => array(
    'id' => 'nodequeue_rel',
    'table' => 'node',
    'field' => 'nodequeue_rel',
    'label' => 'queue',
    'required' => 1,
    'limit' => TRUE,
    'qids' => array(
      '1' => '1',
    ),
    'relationship' => 'none',
  ),
));
$handler->override_option('fields', array(
  'title' => array(
    'label' => '',
    'alter' => array(
      'alter_text' => 0,
      'text' => '',
      'make_link' => 0,
      'path' => '',
      'alt' => '',
      'prefix' => '',
      'suffix' => '',
      'help' => '',
      'trim' => 1,
      'max_length' => '30',
      'word_boundary' => 1,
      'ellipsis' => 1,
      'strip_tags' => 0,
      'html' => 0,
    ),
    'link_to_node' => 1,
    'exclude' => 0,
    'id' => 'title',
    'table' => 'node',
    'field' => 'title',
    'relationship' => 'none',
    'override' => array(
      'button' => 'Override',
    ),
  ),
  'field_copertina_fid' => array(
    'label' => '',
    'alter' => array(
      'alter_text' => 0,
      'text' => '',
      'make_link' => 0,
      'path' => '',
      'alt' => '',
      'prefix' => '',
      'suffix' => '',
      'help' => '',
      'trim' => 0,
      'max_length' => '',
      'word_boundary' => 1,
      'ellipsis' => 1,
      'strip_tags' => 0,
      'html' => 0,
    ),
    'link_to_node' => 0,
    'label_type' => 'none',
    'format' => 'autocomplete_url',
    'multiple' => array(
      'group' => TRUE,
      'multiple_number' => '',
      'multiple_from' => '',
      'multiple_reversed' => FALSE,
    ),
    'exclude' => 0,
    'id' => 'field_copertina_fid',
    'table' => 'node_data_field_copertina',
    'field' => 'field_copertina_fid',
    'override' => array(
      'button' => 'Sovrascrivi',
    ),
    'relationship' => 'none',
  ),
  'body' => array(
    'label' => '',
    'alter' => array(
      'alter_text' => 0,
      'text' => '',
      'make_link' => 0,
      'path' => '',
      'alt' => '',
      'prefix' => '',
      'suffix' => '',
      'help' => '',
      'trim' => 1,
      'max_length' => '120',
      'word_boundary' => 1,
      'ellipsis' => 1,
      'strip_tags' => 0,
      'html' => 0,
    ),
    'exclude' => 0,
    'id' => 'body',
    'table' => 'node_revisions',
    'field' => 'body',
    'override' => array(
      'button' => 'Override',
    ),
    'relationship' => 'none',
  ),
));
$handler->override_option('sorts', array(
  'position' => array(
    'id' => 'position',
    'table' => 'nodequeue_nodes',
    'field' => 'position',
    'order' => 'ASC',
    'relationship' => 'nodequeue_rel',
  ),
));
$handler->override_option('filters', array(
  'status_extra' => array(
    'id' => 'status_extra',
    'table' => 'node',
    'field' => 'status_extra',
    'operator' => '=',
    'value' => '',
    'group' => 0,
    'exposed' => FALSE,
    'expose' => array(
      'operator' => FALSE,
      'label' => '',
    ),
    'relationship' => 'none',
  ),
  'language' => array(
    'operator' => 'in',
    'value' => array(
      '***CURRENT_LANGUAGE***' => '***CURRENT_LANGUAGE***',
    ),
    'group' => '0',
    'exposed' => FALSE,
    'expose' => array(
      'operator' => FALSE,
      'label' => '',
    ),
    'id' => 'language',
    'table' => 'node',
    'field' => 'language',
    'override' => array(
      'button' => 'Sovrascrivi',
    ),
    'relationship' => 'none',
  ),
));
$handler->override_option('access', array(
  'type' => 'none',
));
$handler->override_option('title', 'Queue \'notizie "in evidenza"\'');
$handler->override_option('items_per_page', 6);
$handler->override_option('use_pager', '1');
$handler->override_option('use_more', 1);
$handler = $view->new_display('page', 'Page', 'page');
$handler->override_option('path', 'notizie/inevidenza');
$handler->override_option('menu', array(
  'type' => 'none',
  'title' => '',
  'description' => '',
  'weight' => 0,
  'name' => 'navigation',
));
$handler->override_option('tab_options', array(
  'type' => 'none',
  'title' => '',
  'description' => '',
  'weight' => 0,
));
$handler = $view->new_display('block', 'Block', 'block');
$handler->override_option('items_per_page', 5);
$handler->override_option('use_pager', '0');
$handler->override_option('style_plugin', 'list');
$handler->override_option('style_options', array(
  'type' => 'ul',
));
$handler->override_option('row_options', array(
  'inline' => array(),
  'separator' => '',
));
$handler->override_option('block_description', 'Queue \'notizie "in evidenza"\'');
$handler->override_option('block_caching', -1);

in that page i can only see the nodes that have been added to the queue. When i choose another language i get an empty page with no nodes.
i tried also without the current language filter but without success.

thanks in advance for your help, this is a great module!

Same problem using :
Drupal 6.10
view 6.x-2.5
nodequeue 6.x-2.0
i18n 6.x-1.0

With default nodequeue generated view, translated nodes are not appearing in the view and in the queue manipuliation page.
Only source language nodes are appearing.

Same problem here: I create a nodequeue and ensure "Treat translated nodes as single nodes" is set. I add several nodes to the queue (source, English versions). When I look at the queue either via an unaltered, default nodequeue view OR via the /admin/content/nodequeue/x/view page I see the source/English nodes. However, the queue does not change when I switch language (eg go to /fr/admin/content/nodequeue/x/view).

I was hoping nodequeues and corresponding views would handle this stuff, rather than resort to manually adding each translation to the nodequeue, then filtering by user language in the View... any suggestions? Is nodequeue (and the admin/content/nodequeue/x/view page) supposed to deal with selecting the correct translation node to display?

Drupal 6.10, Views 6.x-2.5, Nodequeue 6.x-2.0, i18n 6.x-1.0, Translation Helpers 6.x-1.x-dev

Shifting this to the i18n queue. Please see my comment in #2. Based on my understanding of how i18n implements views support, this should be beyond the scope of Nodequeue. Am I missing something?

Any guidance here would be greatly appreciated by myself and the folks in this issue (and probably plenty of other people as well).

I'm just working my head round this one as well.

In this case nodequeue just puts the nid of the source in. So obviously without doing anything the only node that will turn up is the one with the nid. When you stick i18n language_negotiation on it will then filter out any that don't meet the WHERE language criteria being used.

So you're going to have to add more nodes into the list to be filtered. Adding a join (relationship) on the translations would seem to be the obvious thing. But I'm yet to construct it so that I get the translated nodes themselves that relate to the original source nid stored in the nodequeue table. I'm not sure if it's possible with options so far.

I think I have just reported a similar issue with the flag module:
http://drupal.org/node/511178

@tomsm

Yes, think it's the same.

http://drupal.org/project/translation_helpers does the job so that only the original node and not its translations are actually in the nodequeue / flag tables.
However, when you then want to make view of this it will only show the the original node, not its translations. If you then add i18n filtering it may remove this as well (depending on mode).

The solution I believe is to make a join on the nodequeue / flag nid's with the translation tnids so they all end up in the view and can then be removed. The alternative is going to be putting all the nid's in the table (but I can see additional problems for nodequeue at least with this - queue length restrictions for a start).

[aside: I have written a solution for nodequeue (and an less working one for flag) for http://drupal.org/project/active_translation (which I intend to clean up and finish at some point). However it's easier there to do the look-up - just an inner join on a dedicated lookup table]

Possibly more accurate, certainly clearer title. But does this belong as a support request in translation_helpers, nodequeue/flag, i18n or views issue queues ;) see my comment above for more.

This is 'query rewriting' working as expected.

We need this one to better handle these issues #364001: Improve query rewriting and content selection: options, parameters, fine tuning

hi - i ran into the same problem - was their any solution to this problem at the end?

I fixed a similar problem with the flags module. Maybe the solution for this issue is similar?
Please see: http://drupal.org/node/511178

I found the solution for Nodequeue translations with views:

You need to add 2 relationships in your view. The first one is 'Node translation: Source translation'. The second one is 'Nodequeue'. Set the first relationship as a relationship of the second relationship and set the second relationship as Required. Problem Solved!

Check the screenshot for the settings of the second relationship.

Thank you Jasperknops for the advice!

Hello Jasper,

Thank you for your solution! It's very helpful!

This could almost be the solution I need for this issue: #832116: Troubles setting up a multilingual ddblock using nodequeue

I'm using nodequeue to build a ddblock slider.
Before I found your solution I couldn't add translations of a node. They wouldn't show up automatically - only the originals were shown. With your solution all translations are automatically included properly, but only if there is at least 1 translated version of that node. If there is only single node (without translation) in the nodequeue, it won't show up at all.

Any ideas?

Ok, I think it works great actually. If my nodequeue only allows 6 nodes, I can place 6 nodes in it + I can make as many translation nodes as I want. Great ! :)

Hi,

I'm experiencing the same problems here.

What I want to achieve: editors just add a node to the queue (independent of language: this could be the source node or a translation) It gets registered and on the front end, the correct translation is shown within the view.

I've also the same setup: Views + NodeQueue + Translation Helper + i18n

* Nodequeue is configured to work in the 'Treat all translations as a single node' mode.
* i18n is set to work with Shown current language + language neutral nodes
* Three languages are defined: Dutch, English and French

I've tried to use Jasper Knops' solution but to no avail. I've also tried to change the 'Source Translation' relationship into the 'Node translation: translations' relationship. Just to get all the translations and show them in my view. No luck there.

I've taken the SQL query it generates and ran it manually on my database, it just returns 1 row. I would expect it to return 3 nodes. The original one + the translations. Then, with the 'translation negotation' filters, I would be able to filter out just the relevant nodes. It has probably to do with nodequeue's INNER JOIN throwing all nodes out ot the resultsset which are not part of the nodequeue_nodes table.

I'm in a tight spot here to get this sorted out.

Here's the SQL:

SELECT node.nid AS nid,
   nodequeue_nodes_node.position AS nodequeue_nodes_node_position
 FROM node node 
 LEFT JOIN node node_node ON node.nid = node_node.tnid
 INNER JOIN nodequeue_nodes nodequeue_nodes_node ON node_node.nid = nodequeue_nodes_node.nid AND nodequeue_nodes_node.qid = 2
 WHERE node.status <> 0 OR (node.uid = ***CURRENT_USER*** AND ***CURRENT_USER*** <> 0) OR ***ADMINISTER_NODES*** = 1
   ORDER BY nodequeue_nodes_node_position ASC

Here's my Nodequeue View:

$view = new view;
$view->name = 'nodequeue_2';
$view->description = 'Display a list of all nodes in queue \'On aime\'';
$view->tag = 'nodequeue';
$view->view_php = '';
$view->base_table = 'node';
$view->is_cacheable = FALSE;
$view->api_version = 2;
$view->disabled = FALSE; /* Edit this to true to make a default view disabled initially */
$handler = $view->new_display('default', 'Defaults', 'default');
$handler->override_option('relationships', array(
  'translation' => array(
    'label' => 'Translations',
    'required' => 0,
    'language' => 'all',
    'id' => 'translation',
    'table' => 'node',
    'field' => 'translation',
    'relationship' => 'none',
  ),
  'nodequeue_rel' => array(
    'label' => 'queue',
    'required' => 1,
    'limit' => 1,
    'qids' => array(
      '2' => 2,
      '1' => 0,
      '3' => 0,
      '4' => 0,
      '5' => 0,
    ),
    'id' => 'nodequeue_rel',
    'table' => 'node',
    'field' => 'nodequeue_rel',
    'relationship' => 'translation',
  ),
));
$handler->override_option('fields', array(
  'title' => array(
    'id' => 'title',
    'table' => 'node',
    'field' => 'title',
    'label' => '',
    'relationship' => 'none',
    'link_to_node' => 1,
  ),
));
$handler->override_option('sorts', array(
  'position' => array(
    'id' => 'position',
    'table' => 'nodequeue_nodes',
    'field' => 'position',
    'order' => 'ASC',
    'relationship' => 'nodequeue_rel',
  ),
));
$handler->override_option('filters', array(
  'status_extra' => array(
    'id' => 'status_extra',
    'table' => 'node',
    'field' => 'status_extra',
    'operator' => '=',
    'value' => '',
    'group' => 0,
    'exposed' => FALSE,
    'expose' => array(
      'operator' => FALSE,
      'label' => '',
    ),
    'relationship' => 'none',
  ),
));
$handler->override_option('access', array(
  'type' => 'none',
));
$handler->override_option('cache', array(
  'type' => 'none',
));
$handler->override_option('title', 'Queue \'On aime\'');
$handler->override_option('use_pager', '1');
$handler->override_option('use_more', 1);
$handler->override_option('row_plugin', 'node');
$handler->override_option('row_options', array(
  'teaser' => 1,
  'links' => 1,
));
$handler = $view->new_display('page', 'Page', 'page');
$handler->override_option('path', 'nodequeue/2');
$handler->override_option('menu', array(
  'type' => 'none',
  'title' => '',
  'description' => '',
  'weight' => 0,
  'name' => 'navigation',
));
$handler->override_option('tab_options', array(
  'type' => 'none',
  'title' => '',
  'description' => '',
  'weight' => 0,
  'name' => 'navigation',
));
$handler = $view->new_display('block', 'Block', 'block');
$handler->override_option('items_per_page', 5);
$handler->override_option('use_pager', '0');
$handler->override_option('style_plugin', 'list');
$handler->override_option('style_options', array(
  'type' => 'ul',
));
$handler->override_option('row_plugin', 'fields');
$handler->override_option('row_options', array(
  'inline' => array(),
  'separator' => '',
));
$handler->override_option('block_description', 'Queue \'On aime\'');
$handler->override_option('block_caching', -1);

I imported your view to compare to mine. The only difference I could find was that in the Relationship - node translation: Translations - you have a dropdown called 'translation option' which i don't have. Changing the options, didn't make a difference.

When I test your view, it only displays results in the default language.

Oh ok, I see now: You used 'Node translation: Translations' and I used 'Node translation: Source translation'. If I don't add a language filter, I see all the nodes.

I think I'm confused on what your issue is.

thx. this is awesome.

The Source Translation trick sort of worked for me, however if I have nodes that do not have a default-language translation then they still don't show in the View despite adding to the Nodequeue fine.

The Source Translation trick sort of worked for me too. But it shows only nodes which are already translated. Nodes without translation are not shown.

Example:

1. I've put some nodes in English in my nodequeue.
2. I setup the "Source Translation trick", and it returns nothing cause none of nodes have translation or better to say there is no "Source Translation" for nodes which is required ("Nodequeue: Queue" is required and got "realitionship" with "Content translation: Source translation").
3. Then I translate one node to Spanish.
4. When switching languages there is only one node (translated one) shown in my nodequeue.
5. Then I translate one more node to Spanish. And there are show two nodes for English, two for Spanish.

Same when I put untranslated node in Spanish to nodequeue. Until I translated it its not shown in nodequeue.
I want to show all nodes in queue and than filter them via views lang filter Content translation: Language (= Current user's language).
I have tried to use "Content translation: Translations" setup to show ALL translations.
It really returns all nodes from my nodequeue, but setting up lang filter did nothing, still shows all translated nodes regardless of filter settings.
What I'm missing? It seems to me useless. I want simple thing: one multilingual limited (Queue size) nodequeue. So Internalization must be setup to "Treat translation nodes as a single node". And then display nodes in queue based on the current user language. It should not be dependent on whether the node is translated or not.

My setup:
Drupal 7.0
Internationalization 7.x-1.0-beta5
Translation helpers 7.x-1.x-dev
Nodequeue 7.x-2.0-alpha1

I'd suggest you take a look at this module: http://drupal.org/project/smartqueue_language

I have tested the solution as at #15 on my Drupal 7.4. It works only when the node has translations. If the node is set to content neutral, it is not shown at all. Is there any way to display both "translations of current language (with url negotiation, i.e. http://xxx/en/content)" and "content which is language neutral" ?

In hook_nodeapi I add the current nid as tnid on node create, if the node has no tnid yet. This way a node without translation will be displayed.

Dear jasperknops (#27), would you tell in more detail how should we "add the current nid as tnid on node create"? Thank you!!!

@netsensei Thanx, I'm still looking for solution for Drupal 7 :/

Thanx, I'm still looking for solution for Drupal 7 :/

#15 Amazing!! - have been searching for a solution for this for a while.

Thanks so much!

Thanks a lot jasperknops for the very very usefull post!

I am using Drupal 7.12 and my Nodequeue ( 7.x-2.0-beta1 ) not working with translation inside View.

I create a content in Spanish and added it to nodequeue say 'NodeQ1' and translate this node to English. I have already set "Treat translation nodes as a single node" for nodequeue, so that it automatically use translation for the nodes inside assigned nodequeue.

I want to have a View that generate the result of node list of NodeQ1's nodes as per the User's current language. Inside view - i add relationship for "Nodequeue: Queue" , checked box for "Require this relationship" and select 'NodeQ1' from the queue list. Filter for "Content translation: Language (= Current user's language)"

This should show me the list of my NodeQ1 nodes as per User's Current language. but its not showing up. If I remove the nodequeue and apply the translation that works. Also my node level Translation and adding that to Nodequeue also work.

any idea why this behavior? or its bug in Drupal 7.

Not this module, please move to the right one before reopening

Is there a solution for displaying nodes without translations right now?

I have the same problem that only nodes which have a translation are shown in the view when adding the Source Translation Relationship.