Problem/Motivation
I have a view which lists articles. The standard view shows the 'lastest' articles ordered by date. On this page there are two entity queues which contain 'featured' and 'popular' articles. Items in the 'featured' and 'popular' entity queues should not appear in the 'lastest' list view.
By adding the 'Content queue' relationship to the 'lastest' view you can then add the view filter: Entityqueue: Content In Queue (= No). That works fine and the queue content is removed from the 'latest' view, but only if you've added one 'Content queue' relationship. If you add another one then it doesn't filter out the additional queue items.
Steps to reproduce
Create an article content type, and some sample nodes. Create 2 entity queues 'A' & 'B' and add some of the sample nodes to them. Create a view that lists out all the articles content items. Then add the 'content queue' relationship for entity queue 'A', and then add the filter 'Entityqueue: Content In Queue (= No)'. The list of 'latest' articles should now exclude anything in the 'A' entity queue.
Now add another 'content queue' relationship for entity queue 'B'. Instead of also filtering out any content in the 'B' entity queue, it doesn't. It still only filters out the content for queue 'A' but content for 'B' still shows. The order of 'content queue' relationships does have an impact, ie. if you reorder them and put the 'B' relationship first then those items are excluded and 'A' aren't.
Proposed resolution
Allow 2 or more 'content queue' relationships to be specified. Whether that is by adding two separate 'content queue' relationships or by only having one, but allowing you to select more than one queue via a checkbox selector rather than only the one via the existing radio button.
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | entityqueue.patch | 1.8 KB | justinchev |
Issue fork entityqueue-3464647
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
justinchev commentedComment #5
nilesh.addweb commentedComment #6
justinchev commentedBrilliant thanks for that Nilesh! I created a patch and tested it with the module and it seems to work as expected when I add the additional content queue relationship. I'm attaching the patch in case it's useful.
UPDATE: Patch works with version 1.8, but doesn't work on 1.9 even though the patch applies cleanly.