Closed (works as designed)
Project:
Node Auto Queue
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
21 Jun 2012 at 21:08 UTC
Updated:
17 Dec 2015 at 17:39 UTC
Jump to comment: Most recent
Comments
Comment #1
davidfells81@gmail.com commentedI wonder if this should be an option. It seems like an overall workflow type situation. I can't think of a reason to add an unpublished node but who knows how those queues are being used? We can't be sure. I'll have to think about this one.
Comment #2
davidfells81@gmail.com commentedNot acting on this one right now.
Comment #3
scotwith1tyeah, i'd say that's the job of the view that's based on the queue to handle not including unpublished nodes, but that's just my 2 cents. i'm sure there are circumstances where the patch is useful. it would be more useful to have a setting to set a variable which then determines whether the node should be added to the queue or not (checkbox on a config page for "Only add published nodes to the nodequeue", maybe a drupal_set_message that reminds the user it wasn't included if they save a node as unpublished and the auto nodequeue checkbox was checked?) There are lots of potential configuration options for this module, but don't want to get too far off the OP here :)