Active
Project:
Node Auto Queue
Version:
7.x-2.1
Component:
User interface
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
9 Jun 2015 at 14:26 UTC
Updated:
17 Dec 2015 at 17:43 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
devd commentedHi,
If you have sitll issue can you please share the screen shots.
Comment #2
Horla commentedIt's not a big problem because users can decide to manually add the node to a queue but it is still happening.
Text is in Dutch:

Comment #3
devd commentedHi Horla,
I think you have not configured properly.
Steps to configure Node Auto Queue Settings.
Access the url: DOMAIN/admin/structure/nodequeue
Click on 'Add simple queue' link.
Enter Title and Select a Types options.
If you select the Artice then 'Automatic Queue Settings' will we display on add new Article Page not other one.
If you have still issue. You are feel free to write me. or chat with me on my skype id: dev.firoza
Comment #4
Horla commentedIt seems that I misunderstood the function of this module. If you enable it then all the nodes from those types will be automatically added unless you disable it at "automatic queue settings" when creating a new node?
I thought it would be possible to create a queue with multiple type of nodes and that you could configure at DOMAIN/admin/structure/types/manage/NODE TYPE if that type of node must allways be added to the queue.
For example:
I have a queue with "images" and "articles". All images must automatically added to the queue but only some articles (so you can just check the box if the article must be added to the queue).
If above is correct then I have a feature request :-)
Comment #5
devd commentedHi,
As per my understanding you want to configure the Node auto add at content type level as per attached image.
if i am right. please create a new issue.?
Comment #6
scotwith1tTo take it a step further, I'd like to see this but also see an option to have the checkbox simply available for the editor and off by default so that EVERY node of that type isn't included. It would be really interesting to build this as something that uses the Field API because then you could even have it conditionally checked using conditional_fields module or something like that. I'll create a new issue for these options.