1

My question is rather simple, but I don't know how to do it ?

I want to display a content with various fields, but I want the user to browse "hierarchically". For instance :

  • Choose brand : BMW
  • Choose model : BMW / Z3
  • Choose specific model : BMW / Z3 / 2.0 i

I already made a taxonomy "Brand", a taxonomy "Model", I have a view that shows all brands.

What can I do ?

Thanks for advice, it would help me a lot !

Improve this question
1

1 Answer 1

Reset to default
1

I had a similar implementation on a drupal 6 site using Hierarchical Select. The drupal 7 branch turned out to be working slightly differently when I first tried to make the move.

There is also Simple hierarchical select which was probably developed because of these 'differences' between d6 and d7:

"This module has been inspired by Hierarchical select but is much simpler (…)."

I haven't tried 'Simple hierarchical select' yet, but if I would re-build that d6 site again, I would probably go for 'Simple hierarchical select'.

Both let you generate a taxonomy tree with dependend parent-child-relationships. So instead of having one taxonomy brandand one one taxonomy model you would have a taxonomy tree taht would contain all the branches down to specific model.

In my case is was venues which then also contained the upper branches like cityand country.

PS: You could however also use entity references to build complex hierarchical content trees. You would then for example have a content type brand and a content type model referencing each other. Nowadays I find this approach more convenient than dealing with taxonomy trees – but that's of course depending on personal preferences and/or content structure.

Improve this answer
8
  • I tried the module - so if I am understanding well, I will have to use sub-terms in the taxonomy ? For instance, the taxonomy I named "Brand" will also contain the "model types" and the "models" ?
    – Marcandria
    May 12, 2015 at 11:18
  • yes – afaik using one of the above modules you would only have one taxonomy tree.
    – tillinberlin
    May 12, 2015 at 11:26
  • That sounds a bit 'dramatic' – good luck! Btw: you can also build rich content trees without using texonomy trees – I updated my answer accordingly…
    – tillinberlin
    May 12, 2015 at 11:58
  • That's where I am lost : can you help me a bit more ? Do you have an example I can check of entity references ? Because my taxonomy is going to be VERY HUGE and if something more convenient than taxonomy is usable, I'll give it a try - I just didn't know anything else existed :) Thanks a lot for your help !
    – Marcandria
    May 12, 2015 at 12:12
  • It really depends on your content structure and your workflow. If you prefer to present rather large, 'ready-made' taxonomy trees to your editors, then taxonomy is probably the way to go. If you instead like adding new child nodes 'on the fly' then entity reference can be an alternative. This article digett.com/blog/04/04/2012/rip-taxonomy-module-drupal-7 made me think – while some of if may be very true, other paragraphs are a bit 'over the top'. But still it can be a good starting point to re-think the idea of 'content trees' instead of 'taxonomy trees'.
    – tillinberlin
    May 12, 2015 at 13:01

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.