Would you consider a patch for this? I'm not sure what the use case is for exposing, but this will make it optional.
Thanks
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | tax_depth_20110208.patch | 1.57 KB | chawl |
| tax_depth.patch | 1.73 KB | awolfey |
Would you consider a patch for this? I'm not sure what the use case is for exposing, but this will make it optional.
Thanks
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | tax_depth_20110208.patch | 1.57 KB | chawl |
| tax_depth.patch | 1.73 KB | awolfey |
Comments
Comment #1
chawl commentedYou saved my life awolfey. I don't have a dropdown with several-thousand children terms anymore.
This simple, neat and perfectly working patch should be committed ASAP (if this module is alive anyway :/) .
Comment #2
asb commentedSorry, this patch doesn't work for me when appying it from within
./sites/all/modules/tax_depth_lim_filteragainst 6.x-1.1, neither with or without the-p0option:Comment #3
awolfey commentedI ended up not using this module after all. Maybe chawl can reroll the patch. Or, it's only a few lines, could easily be done by hand.
Comment #4
asb commentedThank Aaron, I'm still interested to get this option into the module's code.
May I ask what alternative you have found to this module?
Greetings, -asb
Comment #5
chawl commentedOk, try this from module directory.
Comment #6
asb commentedThanks chawl, this patch applies cleanly and works perfectly!
Comment #7
mstrelan commented+1
Comment #8
MBroberg commentedThis is very needed, thank you! Works great for me, although terminology is a little confusing so perhaps an example would help.
Comment #9
hanskuiters commentedThanks for the patch.