Removing term from Node does not remove node from tax queue

Good catch. We should definitely fix this.

I'm just bumping this since it fell towards the bottom of the queue (and out of mind) and I'd like to get this fixed.

+1

@ezra-g - I haven't looked at this in depth yet (and I want to), but by chance would this be addressed by my patch at http://drupal.org/node/642864?

subscribing... found the same issue.

i couldn't apply the patch. it failed
patch -p0 < nodequeue_add_remove_hook.patch.txt
patching file nodequeue.module
Hunk #1 FAILED at 1238.
1 out of 1 hunk FAILED -- saving rejects to file nodequeue.module.rej

Edit: This version already has the patch. PATCH HAS NO EFFECT.

; $Id: nodequeue.info,v 1.7 2008/05/30 18:41:50 merlinofchaos Exp $
name = Nodequeue
description = Create queues which can contain nodes in arbitrary order
package = Nodequeue
core = 6.x

; Information added by drupal.org packaging script on 2009-12-20
version = "6.x-2.x-dev"
core = "6.x"
project = "nodequeue"
datestamp = "1261267787"

I've been going over this exact issue and come to the conclusion that nodequeue shouldn't be altered to resolve this specific case.

You can solve this very well using Rules. Do a negative textual comparison and compare an updated node's changed taxonomy term vs its unchanged taxonomy term using tokens. Then when the comparison fails you can have rules remove from nodequeue (weight -1) and add to nodequeue (weight 0). So any time you have a node updated and its taxonomy term is changed Rules will pull it from its existing nodequeue and re-add it. Since its taxonomy is updated it will re-add it to the correct new taxonomy subqueue.

The reason for not including a patch to nodequeue to take care of this behavior is that its too specific a behavior for future unknown consequences. What if you wanted to leave a node in it's old nodequeue after a taxonomy change? Better to use Rules I think. Especially since some people might be very manual in their Nodequeue usage and others might be more automated with Rules.

That's a good point @endiku, but I think it is worth addressing within Nodequeue. We can address your valid concern with a checkbox (which I think is a reasonable one) on the queue administration page.
Also, I haven't tested or re-examined the code to see if #642864: hook_nodequeue_remove hook not called in nodequeue_save_subqueue_order addressed this, but it's committed so it would be pretty easy to test ;).

did this help with: #884784: Changing taxonomy term on node doesn't move it to other sub-queue?

A fix for this would be great, but meanwhile, the Rules module can be used as a workaround. I have set up two "triggered rules", one for when content is created and one for when content is updated. The action is the same in both cases - "Add to Nodequeues" with the appropriate Taxonomy queue selected. This allows any changes in the node's category assignments to be reflected in the Taxonomy subqueues.

NOTE: In my case, I wanted all nodes belonging to a taxonomy term to be included in the corresponding subqueue. The solution above won't work if you only want selected nodes in the subqueues.

I would appreciate any help with this situation:

I work for a daily newspaper; the stories that are placed on our website are often assigned to more than one category (for example, "Today's news" for the front page, "News" for the general news page, "Local news" for the local news page).

Occasionally, a reporter may put a story in several categories, and an editor may decide that he/she wants to change the categories.

But, of course, when the categories are changed, the story remains on the same section pages (because we use taxonomy Nodequeues + Views to create those pages).

To move a story into the correct section pages, we have to use VBO (Views Bulk Operations) to run "Remove from Nodequeues" and then "Add to Nodequeues."

It would help greatly if there was a way that this would happen automatically, any time that the taxonomy is changed on a story.

My knowledge of Rules is minimal at best ... so any help with this would be greatly appreciated.

I'm having the same problem. I'm new to Drupal and Rules seems fairly complicated.
Any fixes for this?

Closing as a duplicate of #1154948: Taxonomy Sync Queue.
I know this one is older, but I explained my reason in http://drupal.org/node/1154948#comment-4458398.