I'm seeing that only published nodes are returned when nodequeue_load_front/back/random_node are called. I'm guessing that there's internal reasons for the restriction but I want to use a nodequeue to schedule unpublished content and using the built-in functions make that not possible.

Thoughts?

thanks

Martin

Comments

ezra-g’s picture

ezra-g commented
Status: Active » Fixed

These functions use db_rewrite_sql. Make sure that the current user has access to those nodes, or practice safe user masquerading as described in http://docs.google.com/Presentation?docid=dsf7w73_6crbrv6dw&hl=en.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Rob_Feature’s picture

Rob_Feature commented
Version: 6.x-2.0 » 7.x-3.x-dev
Category: Feature request » Bug report
Issue summary: View changes
Status: Closed (fixed) » Active

Reopening this for D7...the previous answer indicates this should be possible if the user has access to the nodes. But I believe this changed in D7 because I'm operating as UID 1 and it's not returning unpublished nodes.

Can someone clarify that this is not possible in D7 along with any work around?

I'm actually marking this as a bug because logically, if the nodes are in the queue (which they are) these api calls should return them...otherwise the function should be renamed something like 'nodequeue_load_front_published' (I'm not serious about that..just making a point that this function doesn't seem to do what it's name claims)

jenlampton’s picture

jenlampton
she / her
commented
Version: 7.x-3.x-dev » 7.x-2.x-dev

Changing branch, since it looks like 3.x is not active anymore.