I'm using a CCK content taxonomy field for a location hierarchy associating it with a node-profile content type, so provide for a searchable location for system users. I have it working fine using the latest dev version of content_taxonomy and the rc2 of hierarchical select for creating the data (actually assigning a location to a user), but a couple of odd things are happening in my view filters (and I have patched the views.module file, even though for whatever reason admin/logs/status is saying i haven't). One of them has to do with saved_searches (which I will post separately), but for this issue, I find that when I try to add more than one term to the filter, only the one with the earliest alphabetical value (of all the terms in the lineage) is being kept and used when i hit "Submit" to go fetch the records. And, when the page returns, there is only one line showing in the "All selections" box, and it's the lineage used for the filter. I've included before and after images.
The taxonomy is set up as
- single hierarchy.
- Use the Hierarchical Select form element for this vocabulary.
- Save term lineage
- Force the user to choose a term from a deepest level
- Display the node count: Enabled
The exposed filter is set up as
- Optional, Filter settings Default, and Lock Operator all checked.
- The "Save lineage" setting seems to make no difference.
- Force the user to choose a term from a deepest level is set.
- Display the node count: Enabled
- Enable the dropbox is set.
- Limit the number of selections: 0
- Reset selection of hierarchical select: tried both settings, no apparent change in behaviour.
Any ideas what I'm doing wrong?
| Comment | File | Size | Author |
|---|---|---|---|
| location_hs_after.png | 71.84 KB | sdsheridan | |
| location_hs_before.png | 80.25 KB | sdsheridan |
Comments
Comment #1
sdsheridanAnd interestingly I get the following three times in the Recent Log Entries with only one location selected after clicking "Submit".
Comment #2
wim leersReproduced.
Comment #3
wim leersAlso a duplicate of http://drupal.org/node/295016, which has been fixed.
Comment #4
1kenthomas commentedDuplicate of itself?