Active
Project:
Nodequeue
Version:
6.x-2.10
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
20 Jun 2008 at 18:38 UTC
Updated:
24 May 2016 at 21:43 UTC
Jump to comment: Most recent
This used to be part of nodequeue 1, but for some reason disappeared in nodequeue 2. I don't know why this was removed (perhaps there is some way to create broken SQL with it enabled?), but this a *very* useful feature and it works fine for us!
Will need a different patch for HEAD (Views 2).
| Comment | File | Size | Author |
|---|---|---|---|
| multiple_queues.patch | 672 bytes | owen barton |
Comments
Comment #1
ezra-g commentedThis seems fine with the filter an all modes: all of, none of, one of.
RTBC. Thanks!
Comment #2
ezra-g commentedCommitted, thanks! Catch this in the next release candidate.
Comment #3
owen barton commentedAwesome - thanks!
Comment #4
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #5
anoopjohn commentedIs this option present in 6.x-2.9 release? Is it possible to add an exposed filter in views that will allow users to select the nodequeue from a select box?
Comment #6
amateescu commentedCan you explain with more details what this filter should do?
Comment #7
owen barton commentedThe filter is already committed (as of 2008) and just enables you to select more than one of the queues at a time in the views filter.
Comment #8
anoopjohn commentedI tried all the following filters.
(queue) Nodequeue: Queue title exposed
(queue) Nodequeue: Subqueue reference exposed
(queue) Nodequeue: Subqueue title exposed
(queue) Nodequeue: Queue machine name exposed
and all of these exposed filters comes up as text boxes in the page display that was generated. I was referring to the possibility of one of these filters coming up as a select box (drop down) allowing end users to filter by selecting one (or multiple if possible) of the nodequeues from the select box.
Comment #9
amateescu commented@anoopjohn, as you discovered already, this feature is currently not implemented in nodequeue. I'd be happy to include it if you can provide a patch..
Comment #10
anoopjohn commentedShall we mark this as closed (outdated) given that this is about 6.x which is no longer supported?
Comment #11
fizk commented@anoopjohn I'd like to leave 6.x issues open for now in case someone is working on them.
Comment #12
anoopjohn commentedIs this feature working in 7.x?