Hi,
I have a fresh installed Drupal setup (5.2) with nodequeue-5.x-2.0-rc.tar.gz installed.
I created a new Node Queue (which has id 2, after having deleted a first one for testing purposes).
Now when i'm adding nodes to the queue through the 'Node Queue' tab by clicking the 'Add to queue' AJAX link, the column 'In Queue' shows always 'Queue empty' after the AJAX request, whereas before the AJAX request it showed the correct number of items (there are 3 items in the queue in my example).
Firebug tells me a request is made to "admin/content/nodequeue/2/add/2/9" where the first '2' is my qid, and 9 is my nid.
The request that gets returned is this:
{ "status": 1, "label": "Remove from queue", "href": "/drupaltest/?q=admin/content/nodequeue/2/remove-node
/2/9\x26tab", "count": "Queue empty", "sqid": "2" }
There seems to be a problem with the "count" property, as that should be 4 in my case (after adding to the 3 items that are already in the queue).
When i check the code that returns this count property, i'm a bit confused about the subqueue concept: i don't seem to get what a subqueue actually does?
Does this mean that you can add queues within queues? Because i wouldn't know how you could achieve that with the current module (or i must have missed an important setting somewhere).
Anyway, can you check if this count property issue is actually an issue, or just something wrong at my side?
Good luck with this great module!
Comments
Comment #1
merlinofchaos commentedI need to write some documentation about subqueues still, and that just hasn't happened. But the short explanation here is that subqueues need an additional plugin to help define them; for example, smartqueue_taxonomy creates subqueues and assigns them to taxonomy terms. Basically, if you assign a smartqueue_taxonomy to a vocabulary, then every term in that vocabulary gets a subqueue, and nodes are then eligible for the subqueues for which they have the term. This is *really* useful for newsy type sites.
I'll check the in queue counter now. This may be something I've already fixed in -dev, as I remember fussing with that a couple of times since the -rc went out.
Comment #2
merlinofchaos commentedYes, limited testing indicates this works; try either -dev or wait for rc2 (which may not be a long wait, I hope to have one when I'm doing going through the issue queue here.)
Comment #3
merlinofchaos commentedComment #4
(not verified) commented