Items in queue show more than once in a view

This issue has come and gone for me. From what I've been able to determine, it only occurs if I try to use the sort criteria field in the view, the issue occurs. I've tried correcting it by using the "Distinct" option, but that does not solve the problem.

I find the view works OK without using the sort criteria option, though.

It seems like you're reporting two different errors here. First that you have a view that is showing the same node multiple times and second that Nodequeue doesn't allow you to add an item to a queue using the "Select title to add" field.

In my testing, I was successfully able to add nodes to a queue even if they had identical titles. The only time I got the "matches too many nodes" error message was when I didn't click the autocompleted "node title [nid]" text and just submitted the form without a nid value in the text field. Can you confirm that this is what happened? If that's not the cause of this problem, could you tell me the nid, type and title of the nodes that lead to the error?

Furthermore, I was able to successfully add the same node to a queue multiple times and save the queue. We should prevent the same node from being added to a queue multiple times by not allowing these values to be saved in the database and possibly with validation that prevents them from even being entered on this form. The former should be addressed in the refactoring at #234004: Drag and drop node ordering.

It seems possible that the reason you had multiple nodes showing up in a queue is that you were able to erroneously add multiple instances of them to the queue. Is that the case?

Thanks!

Note that the ability to have nodes in a queue multiple times was a requested feature. I'm not entirely sure it was a good idea, and the requester didn't end up using the module anyway.

[edit]
That's good to know. I think it could make sense to have the same node appear in a queue multiple times if there is demand for this feature. A search does not turn up a existing feature request. I thought about whether that would be a good feature and one immediate problem is how the add/remove ajax links would behave for a node that is in a queue multiple times.

Changing status.

@ezra-g,
We just experienced this after upgrading to D6-14. It's the first time I've seen it, so i don't really have much info about what else could have caused this, except noticed this happened immediately after the upgrade.

I was a few versions behind, so i just upgraded to nodequeue-6-2--4, and the same thing occurs. using views-6-2--6... would any other info be useful? Or, any tips where i can look for possible debugging?

@merlinofchaos, re #6, has this feature been removed in views-6-2? if so we can just upgrade. If not, i could help write a patch to remove it (if it's still a feature that the requester isn't using) - do you think that would be a good idea?

Update: this was not the problem in our case (weirdly it was a domain access module issue), so i take back what i said about a patch ;)
I did however notice a duplicate position error, but i see that's from #234004: Drag and drop node ordering so i'll take it up there if i see that again.

Can someone post an export of a view that has this problem?

Update: this was not the problem in our case (weirdly it was a domain access module issue), so i take back what i said about a patch ;)

After re-reading this thread, looks like nobody is still reporting this problem.

I was looking for something smilar and found this node. I'm using views+content profile modules and have a "search user" view and view gives same user a few times. I'm not sure if this is a views issue or a content profile module issue though.

pls have a look at to atta. picture.

I just came across the same behavior, which for me is a result of a node being listed multiple times in a single queue. That makes it a duplicate of #593468: adding the same node more than once to a queue causes bad behavior.