Greetings, all. Hope I'm in the right place for this.
I'm setting up a fairly complex site for my first time using Drupal. Not the best way to go, I know.
It's moving along pretty well, but I've run into something that I'm sure is quite simple to accomplish, but can't wrap my brain around it and can't seem to find an answer for.
Basically, I'd like to use one view to handle multiple nodequeues and display any given nodequeue only for the related node. Sounds simple, and it probably is.
The site is taxonomy-driven, with 7 second-level pages, each with its own group of sub-pages. I want to have featured content carousels on the home page as well as each second-level page. This was easy enough to accomplish and works a peach.
BUT, i'd like to have a carousel on any second-level pages display the carousel ONLY for that node, using ONE view. I don't want 7 different views if I can avoid it.
So let's say I have a Section Carousel view, and I have nodequeues for Section A, Section B, Section C, etc. If I go to Section B, I want to see the carousel ONLY for Section B, and none of the others. Currently, I'm seeing the same carousel on all second-level pages.
I figure this is likely done via contexts in views--maybe...? and will have an answer so absurdly simple. but I can't seem to nail it down.
Any assistance greatly appreciated for this n00b, and I'll do my best to answer questions as clearly as I can.
thx!
Comments
also, might help to know
Using Views 3 on D7
Filter by term, sort by nodequeue
I assume the following:
Vocabulary: Section
Terms: Section A, Section B, Section C, etc
Second level pages have urls like http://www.site.com/section-b
You can add a term conextual filter to limit the nodes shown to only those in the current second level page. You can then add a nodequeue relationship and sort by queue position.
E You might not want t o use
E You might not want t o use a node queue.
On your secondary pages you could add a node ref field. And then have the view use that field to feature items.
Also you could use boxes (with entity boxes or viewboxes) or beans to create configureable block and then use context to place this in the correct sections.
E You might not want t o use
Was a dup post