For nodes with hierarchical taxonomy terms I get duplicates in my taxonomy overwrite view if they are added via VBO. The nodes are added to several subqueues because they have several hirarchical terms. If I remove them from all but one subqueue all is fine. Maybe it would make sense to add them only to the lowest term in branch an make the subqueues sortable/hierarchical? So the node gets a weight like 0 - 5 - 143 (0 for weight in first subqueue - 5 for weight in second subqueue - and 143 for weight in the actual subqueue). Don't know if this makes sense.
grossmann-mcs

CommentFileSizeAuthor
#7 subqueue config.png125.32 KBjackmc

Comments

grossmann’s picture

grossmann commented

As I found out this is also the case in non-hierarchical taxonomies. If the same node is in multible subqueues it get duplicate entries in the view. Setting the view query setting to distinct doesn't help any.
grossmann-mcs

grossmann’s picture

grossmann commented

OK after playing around I think I found out the main problem here. Nodequeue ignores the subqueues for displaying the nodes in a view. Example:

Subqueue 1:
 node_x weight = 1
 node_y weight = 2
 node_z weight = 3
Subqueue 2:
 node_a weight = 1
 node_b weight = 2
 node_x weight = 3 (same as in subqueue 1)

The view result for taxonomy term of subqueue 1 looks like this:

 node_x weight = 1
 node_y weight = 2
 node_z weight = 3
 node_x weight = 3 (duplicate)

This results in duplicates on nodes with multible terms independent if they are on the same level or in a hierarchy.
grossmann-mcs

grossmann’s picture

grossmann commented

To continue my monologe here ;-) this may be a duplicate to adding the same node more than once to a queue causes bad behavior but I a not sure if this is a general problem or specific for the smartqueue taxonomy submodule.
grossmann-mcs

grossmann’s picture

grossmann commented
Title: Duplicate nodes in hierarchical taxonomies if added via views bulk operation » Same node in multible subqueues gets duplicates in views

Edit of the issue title to reflect the more general problem.
Nodes which are in more than one subqueue get mixed up and duplicate displayed in a view (as described in #2).
grossmann-mcs

Anonymous’s picture

Anonymous (not verified) commented

I solves this as follows:

- add a filter by Subqueue reference "(queue) Nodequeue: Subqueue reference (= )"
- in the filter settings choose "Pick arguments for values" and select the contextual filter "Content: Has taxonomy term ID (with depth)"

This basically restricts nodequeue-nodes to a specific subqueue only. This solution works for taxonomy terms pages/views of course.

jackmc’s picture

jackmc commented

I have the same issue, can you elaborate on how you resolved this?

I can't reproduce the second step - in the filter settings choose "Pick arguments for values" and select the contextual filter "Content: Has taxonomy term ID (with depth)"

Thanks a lot,

Jack

jackmc’s picture

jackmc commented
StatusFileSize
new subqueue config.png125.32 KB

After some pain, I got this working (for my case). Desired functionality was to have a taxonomy smartqueue, then use views to show a listing of content within a given subqueue, overriding the standard taxonomy term page.

The solution, which was quite logical, was to ignore taxonomy completely in the filters, and just rely on subqueue. I think this is what morningtime was referring to above.

Hopefully this helps others. Please ask if you want more details.

Views smartqueue taxonomy Config

Anonymous’s picture

Anonymous (not verified) commented

Sorry for late reply. In my version of Views (probably latest dev), filters criteria can have the option "Pick arguments for values". I setup a contextual filter "Content: Has taxonomy term ID (with depth)", and then selected this as the "Pick arguments for values".
This reduces duplicate nodes from multiple smartqueues on taxonomy/term pages.

gooddesignusa’s picture

gooddesignusa commented

moringtime I updated to the latest dev of views and still dont see that option. I looked through the views issue queue and found this post:
http://drupal.org/node/357082 - Pull filter value from an argument?
Did you happen to apply a patch from that issue or do you have http://drupal.org/sandbox/itangalo/1086472 (Views arguments in filters) sandbox project installed?
Thanks in advance.

shadysamir’s picture

shadysamir commented
Issue summary: View changes

Thanks @grossmann-mcs that was really helpful

webstudiodelta’s picture

webstudiodelta commented

@jack-mc 's solution works but leaves one feature desired, which is the ability to have all non-queued nodes simply appear below the queued ones, provided they are also tagged with the appropriate term. Any ideas on how I might accomplish this?

grossmann’s picture

grossmann commented

I can not get it to work. I tried @jack-mc but setting the subqueue ref in the contextual filtes gave me nothing. My tid was 104 and with content: taxonomy ref i get the desired results but with lots of dublicates.
The stuff @morningtime mentions is not in my views 3.7 version so i could not try this.
Setting the query to distinct didn't solve anything too.
So I am bit lost here. Any help is welcome.

grossmann’s picture

grossmann commented
Status: Active » Closed (fixed)

Ok that was definitly a pilot error. I tried to use a tid (104) which was not part of a smartqueue (even the nodes had already a taxonomy with a smartqueue). I simply had to make a new taxonomy queue with the right terms and add the nodes to this queue and everything worked fine.
Conclusion: Solution in #7 works and you have to check if the term is truely part of an nodequeue (eg. taxonomy queue).
This leaves only open the requested feature of #11 which I think might be a seperate issue (if any at all). So I close this as fixed.