Hey Wim,
I like to look at HS (taxonomy) with an expanded view instead of the dropdown boxes. I can expand the view by pulling down the grippie, but every time I select a new level of the hierarcy, the view collapses back to the drop down menus. Is there a way to keep the menus expanded?
I read over the api documentation to no avail. It feels like I'm just missing a setting, but I can't figure it out.
Attached is a screen show of how I *want* it to look.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | hs_taxonomy.module.patch | 331 bytes | digitalproductionart |
| Picture 2.png | 28.39 KB | digitalproductionart |
Comments
Comment #1
wim leersThat's not a missing setting. It's a bug. Are you absolutely sure you're running the latest version? This bug has been fixed *many* months ago. It'd be rather odd if it was reintroduced.
Can you reproduce this at http://wimleers.com/demo/hierarchical-select/taxonomy? It works fine for me there.
Comment #2
digitalproductionart commentedI was not able to reproduce that link alone, but I did get it to work.... Here's my troubleshooting steps:
1. Un-installed HS
2. Re-installed HS (latest dev version)
3. ran Update script
--> Did not work
I've been reading over the api documentation before I posted the original issue, and I could not find the #size parameter. Just searched all files again, and figured it was *missing*.
4. Searched files for #size parameter
5. added '#size' => 10, on line 202 of hs_taxonomy.module
6. It works now.
I'm running the og_vocab module, just an fyi. Not sure it this is the conflict.
Attached is a patch.
Hope this helps in your developement. Thanks again for your help Wim!
Comment #3
Roze-1 commentedCan you please tell me how to fix the height , coz even when i change the size to =>1 they show me in single row.
A little help will be useful.
Thanks in Advance
Comment #4
kars-t commentedDear fellow Drupal enthusiasts,
this issue is now lasting for a very long time in the issue queue and was unfortunately never solved. As Drupal is a open source project everyone is helping on voluntary basis. So that this is was not solved is nothing personal and means no harm. But perhaps no one had time to deal with this issue, maybe it is too complex or did not describe the problem comprehensibly.
But this issue is not the only one. There are thousands of issues on Drupal.org that have never been worked on or could not be processed. This means that we are building a wave that is unmanageable and just a problem for the Drupal project as a whole. Please help us keep the issue queue smaller and more manageable.
Please read again, "Making an issue report" and see if you can improve the issue. Test the problem with the current Core and modules. Maybe the problem doesn't exist anymore, is a duplicate or has even been solved within this issue but never closed.
Help can also be found for it on IRC and in the user groups.
In order to remove this issue, I have set this issue to "fixed"
If there is new information, please re-open the issue.