I am using nodequeue on my site to order teasers on a couple of index pages.

I've noticed that if I click to remove a node the node disappears from the list but looking in the database I see that the node is not actually removed from the queue but instead it is still present, only the nid for the 'removed' node is set to 0.

Is this how it is supposed to work?

Comments

ezra-g’s picture

ezra-g commented

That's not how it's supposed to work. Thanks for spotting this.

This sounds just like #297027: Custom Javascript: Cannot remove items from nodequeue which I was unable to reproduce in the 6.x branch, but perhaps it is a problem in 5.x. I'll try to reproduce this in 5.x and see what happens.

billybob4’s picture

billybob4 commented

OK thanks :)

It wouldn't be a big issue for me personally, but when my client views the nodequeues summary they look at the 'total nodes in queue' figure and wonder why it doesn't correspond to the number of nodes that actually show up.

If you struggle to reproduce it let me know and I'll try to give any further info you might need.

p.s. yes it does sound like the same thing as that other report you linked to.

ezra-g’s picture

ezra-g commented
Status: Active » Postponed (maintainer needs more info)

I'm not able to replicate this so far.

One way to pursue this is to consider every possibility for how a nid value of 0 could get into nodequeue_nodes. Since I'm not able to do that right now, could you provide a debug backtrace from nodequeue_subqueue_remove_node() when you are removing a node whose nodequeue_nodes value will have an NID of 0? That would be extremely helpful. Thanks!

ezra-g’s picture

ezra-g commented

Also, could you paste the result of "SELECT * FROM {nodequeue_nodes};" ?

ezra-g’s picture

ezra-g commented
Status: Postponed (maintainer needs more info) » Closed (duplicate)

I'm marking this is a duplicate of #297027: Custom Javascript: Cannot remove items from nodequeue so that we can keep the troubleshooting information in one place. Please follow up on that issue. I'd like to found out what's going on here.

ezra-g’s picture

ezra-g commented

To clarify, both users on this thread reported that it appears as though the invalid entries in nodequeue_nodes are being created when a node is removed. I suspect that these values may be getting created when nodes are moved or entered into a queue, since the removal of a node from a queue doesn't ever modify or create a sqid value.

ezra-g’s picture

ezra-g commented

wrong thread, sorry.