By jnvsor on
I want to display a hierarchical list of terms based on their popularity on the front page, the 4 most popular terms create 4 "Blocks" in the page, and each shows their 5 most popular terms, this can be cleaned up with css later:
- Popular parent term 1
- Popular child term 1
- Popular child term 2
- Popular child term 3
- Popular child term 4
- Popular child term 5
- Popular parent term 2
- Popular child term 1
- Popular child term 2
- Popular child term 3
- Popular child term 4
- Popular child term 5
- Popular parent term 3
- Popular child term 1
- Popular child term 2
- Popular child term 3
- Popular child term 4
- Popular child term 5
- Popular parent term 4
- Popular child term 1
- Popular child term 2
- Popular child term 3
- Popular child term 4
- Popular child term 5
I don't honestly know how to do this in views, there don't appear to be any filters or orders based on parent terms, and I'd need 4 different views as I can't stick them together the way I want.
Is there an easier way to do this? Will I have to write my own module?
Comments
The drupal.org recommended way to get project help
Thee 'issues' que for your project:
http://drupal.org/project/issues/views
The 'home' page for your project:
http://drupal.org/project/views
===
If you have a question about or a problem with
a specific module (a 'project'),
or a specific theme (also a 'project'),
the issue que for that project is the closest you can get
to true live help of an unlimited nature
and is in fact the recommended way to get help at drupal.org
for module-specific or theme-specific questions.
Search first. [_Search_]
The best of all possible searches
for Drupal Module-specific or Theme-specific
issues/ questions/ problems/ suggestions/
or support requests, ...
Search from any of a project's 'issues' pages,
(or from the specific project's 'home' page)
and that will limit your search to all and only
the issues concerning that specific project.
Then, if you do not find your answer, <_Create_new_Issue_>
Assuming you did Not find whay you were looking for...
Click a project issue page's
link: 'Create new issue'; and for 'Category',
if in doubt, specify 'Support request'.
===
For more details on getting help on specific projects, see...
"Get the Fastest Answers to Module-Specific
or Theme-Specific Issues at Drupal.org
- How to"
http://drupal.org/node/1478010
===
Additional drupal.org 'general' posting recommendations
Tips for posting to the Drupal forums
http://drupal.org/forum-posting
.
.
.
: o )
All the best; intended.
-Chris (great-grandpa.com)
___
"The number one stated objective for Drupal is improving usability." ~Dries Buytaert *
I think this is the right place to ask...
A "how to do something complex with Views" question is pretty commonly handled in the forums and there are a lot of experienced "site builders" here, so there is no need to clog the Views "issue queue" with "support requests". Views is about as close to "core" as you can get without actually being in core; almost everyone uses it and there are tons of modules available to extend Views and/or to do specific things with taxonomies.
My suggestions:
1) Look at modules for Views
2) Look at modules for taxonomies
3) Try to just use Views and look for documentation. You might find this helpful
4) Google: Drupal get child terms views (this is how I found the above issue, among other possibly-useful tutorials and explanations.
I think what you are trying to do is not so uncommon, so it should be possible with Views (without additional modules). I doubt you'll need to create any custom module, but it really depends on your use case/requirements.
See you at the Drupalcon!
Sure.. the Views issues que is quite clogged-- no doubt
But you are more likely to possibly find the answer there
there-by eliminating the need to post in the first place.
And so why clog up the Forums with one more post when
the developers of Views are more likely to have the answer
and are less likely to be here.
Just a thought
: o )
All the best; intended.
-Chris (great-grandpa.com)
___
"The number one stated objective for Drupal is improving usability." ~Dries Buytaert *
Searching the Views queue is a good idea...
Making a new issue in the Views queue to further weigh down the developers is not such a good one, imho. There are lots of folks here who know their way around Views and are more likely to see and respond to a help request than are folks looking for answers in the queue (especially the developers, who most likely won't respond to anything but a bug report).
Just a thought... ;-)
See you at the Drupalcon!
Solution
The Views Field Module resolves this problem.
http://drupal.org/project/views_field_view