I have a strange problem. I suspect that it is caused by translations of a same node.

I am using i18n module. After I created one node, I added its translation (totally two nodes).

There are two ways at my web site to adding contents into a nodequeue:

  1. When I view the content, there is a "Nodequeue" button next to "View", "Edit" and "Translate". When I click the "Nodequeue" button, there will be a "Add to queue" link under the field "Operation".
  2. Click Nodequeue from the admin menu. Select the nodequeue to add. Then fill in the autocomplete input field to add the node to the queue.

It is ok if I use the first method. However, when I use the second method, the following happens:

  1. the node cannot be retrieved by Views. The view is written with relationship of the nodequeue. This is not related to the i18n as the node cannot be retrieved no matter how I set the language filter. All other items in the queue were displayed okay.
  2. When I go to the nodequeue item list, there is no way to remove items added by this method: when I click "remove", the overlaid admin page became a normal non-overlaying admin page (I think this indicates something goes wrong), and the node is still in the queue (cannot be removed).

This node's order in the queue can still be rearranged and saved. However, it simply can't be dropped.

The only way to remove this node is to remove it from the nodequeue database table, or delete the node itself.

The nodequeue setting is:
Internationalization: "Treat translation nodes as a single node"
Modules:
i18n: latest 7.x-1.x-dev
nodequeue: latest 7.x-2.x-dev
Drupal Core 7.7

Comments

amateescu’s picture

Status: Active » Closed (duplicate)

This seems to me like a duplicate of #851616: Translation: autocomplete on subqueue lists incorrect nodes. I just commited a fix over there so please test with a 7.x-2.x-dev version from at least 2011-Sep-17 and reopen if necessary.