Needs work
Project:
Nodequeue
Version:
7.x-2.x-dev
Component:
Code
Priority:
Minor
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
16 Apr 2009 at 08:31 UTC
Updated:
24 Nov 2019 at 22:08 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
ezra-g commentedIt's not currently possible. I would review a patch to make this possible but it would probably complicate several parts of Nodequeue. I'm not opposed but I'm also not bowled over with enthusiasm
Comment #2
bohz commentedThanks for the info.
I am not capable to develop anything at the moment :(
Moreover, I don't see a lot of users with similar issues, so I guess we can skip this feature request.
I will look for an alternative way to warn/educate the editors on how to assign nodes to queues.
Thanks anyway!
Comment #3
ezra-g commentedMarking as minor unless anyone feels differently.
Comment #4
ezra-g commentedComment #5
amateescu commentedThis should be fairly easy to do after #1049000: allow hook_nodequeue_add/remove to block the action.
Comment #6
b.ravanbakhshI add one line code to delete all previous queue that node belongs to before doing add to new queue.
for the 7.x-2 versions the line number is 1044.
Let me know if you need help backporting it, or if anything needs work.
prowebdesigner.com.au
Comment #7
jenlamptonWe can't prevent all nodes from being in more than one queue or we'll break lots of existing sites that need to have them in multiple places. This needs to be implemented as a setting, so that people who want the limitation can opt-in.
I'm changing the branch to 2.x, since the 3.x branch is no longer supported.