I have a problem with Nodequeue Settings page. I have selected the tyoe "Content type A" ... This is supposed to be the content of which is elegible to place within a nodequeu. The problem is that when I do, it creates a node queue for each item created of that type automatically. I have a feed item content type. Everytime I get a feed created I get a nodeques for each of my feeds which was created. However if I deselect the content type, I can not have the ad to nodequeue link appear. I think this is an error. I want this content type to be one optionally allowed to be placed with in the og nodequeue. I do not want each content item to have its own nodequeue!

CommentFileSizeAuthor
#4 smartqueue_og-eligible.patch758 byteslyricnz

Comments

chrisschaub’s picture

I am seeing this too. Seems like a bug, it's creating nodequeues for each type of eligible node, not just the primary group node. We just imported 800 articles on our site, and article is a type of node that can be posted into groups. And boom, 800 nodequeues were created as subqueues withing the group smartqueue.

Thanks for any help.

chrisschaub’s picture

Ok, you need to check off:

Group types which are eligible for a Nodequeue:

And select the "group" type. Otherwise, it will create nodequeues for all content types that are eligible to be in nodequeus.

drtrueblue’s picture

I'm struggling with this, although I'm using version 6.x-1.0-rc3. Regardless of what the settings / configuration are for [content] type or group type, I still get this problem. Any advise would be greatly appreciated.

lyricnz’s picture

Status: Active » Needs review
StatusFileSize
new758 bytes

I am also experiencing this. The problem is caused by smartqueue_og_eligible_group_type() checking for og-smartqueue enabled types using in_array() when the data structure actually looks like:

Array
(
[group_profile] => group_profile
[school_profile] => school_profile
[theme_profile] => theme_profile
[town_profile] => town_profile
[business_profile] => 0
[family_profile] => 0
[individual_profile] => 0
)

(so elements exist in the array, even when the type is not enabled).

Here's a patch that fixes it.

You can clean up any unwanted queues by using the "delete" radio button at the bottom of the nodequeue settings.

Edit: uh, description not quite right. BBIAB.

ice5nake’s picture

This issue makes this module seem pretty janky. Gonna try to test this patch if I get a chance.

AntiNSA’s picture

Is this working?

ice5nake’s picture

Status: Needs review » Reviewed & tested by the community

This patched worked for me.