Subqueues don't seem to be added for a node of the specified content type until a node that is eligible to be added to the subqueue is added.
So if you've set up a Content Type Queue that generates subqueues for nodes of type 'Artists' and can have 'Artwork' nodes added to the subqueue:
1. Add 'Artist' node
- no subqueue generated for the 'Artist' node at this point
2. Add 'Artwork' node
- a subqueue is now generated for the previously saved 'Artist' node
Can anyone else confirm this?
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | smartqueue_subqueues_nodeapi-1116406-4.patch | 1.45 KB | mikl |
| #3 | smartqueue_subqueues_nodeapi-1116406-3.patch | 1.48 KB | kasperg |
Comments
Comment #1
khalor commentedAfter further testing it seems it isn't the node save that's triggering the subqueue generation, but rather viewing a node that can be added to the subqueue.
Comment #2
tema commentedThank you for your interest. I know about this deficiency. I tried to make this module simple, so it does not implement
hook_nodeapi(), nodequeue.module implements it anyway.Yet put it to "Won't fix", but if you provide a patch, perhaps you will win :)
Comment #3
kasperg commentedHere's a patch against 1.2-beta2 with the hook_nodeapi() implementation.
Comment #4
miklThere was a syntax error in the patch from #3. Fixed now.