By kulfi on
I've gone through both http://drupal.org/node/134630#comment-220910 and http://drupal.org/node/74747, and it still isn't clear whether dependent drop downs are possible using Category and Active Select modules.
What I'm trying to accomplish, preferably without custom coding:
- Have a vocabulary 'place'
- 'Place' has the following hierarchical terms:
USA
AL
AK
AZ
...
WI
WY
UK
England
N. Ireland
Scotland
Wales
...
- When a user creates content and selects 'USA' first drop down list, only the US states should show in the second drop down list
Is this possible? Thanks.
Comments
Looks like my formatting was lost
Simple example
Here's the URL for simple demo module which has 4 levels of linked dropdowns reading from the database.It's a location select which is what you were enquiring about. Hope this is of help.
www.keyreels.com/drupal/locations.html
I've included some sample data - don't forget to switch on activeselect.
Geoff
Apologies
Apologies - you would already have come across this on the previous threads you'd looked at.
I did take a look at your
I did take a look at your solution, and at first glance it doesn't look like a module? I'd like to maximize maintainability by using plug/play modules without customization.
At various points in the threads, various people have claimed success, for various Drupal versions. Was hoping for a clean solution :)
module?
It is a module - but only a demonstration module. I stripped the minimum I could out of my working code just to show others how it could be done. It would take some effort to make it a full stand-alone solution with admin to add new entries and some code to submit the result - I'm just sorry I haven't the time to do it just now.
Thats cool. So is it just an
Thats cool. So is it just an implementation of active select, or taxonomy + active select?
Just chained activeselects
It just allows you to select a country, then a town, then a building then a room. Just a demonstration of how you chain things together and an example of how you would store this in a database in a single table.
It could be modified to use taxonomy rather than its own table but there are a number of pros and cons in that area and in my current implementation (for an assets module) it seemed better to use my own table than use taxonomy
Quasi-closure
For anyone looking for the same (UI only appropriate for smaller datasets), I went with Taxonomy Super Select module. Still clunky, but better than the original default checkboxes/dropdown list.