Closed (fixed)
Project:
Taxonomy Filter
Version:
4.7.x-3.0-beta1
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
27 Oct 2006 at 23:47 UTC
Updated:
21 Apr 2007 at 20:48 UTC
Jump to comment: Most recent file
Comments
Comment #1
styro commentedMy own usage of this module will change somewhat. For the next generation of my own site I have some ideas for a bunch of new taxonomy modules that will both take over from and extend this taxonomy stuff. But they are just ideas at this stage.
Even if I no longer use taxonomy_filter myself I probably will at least update it to 5.0 shortly after 5.0 is released. I haven't even got around to reading up on Dereks new release system yet. I will welcome patches from more impatient users :)
In the meantime, there are a few work-a-like modules (refine by taxonomy and taxonomy easy filter) that have turned up since I first wrote taxonomy_filter although I haven't tried them myself. Some of those might get ported to 5.0 before taxonomy_filter does.
Comment #2
talkingwires commentedI've played around with some of the other modules that accomplish things similar to your module. But I've found them either to be a little clunky. I found your module's simplicity to be ideal, considering the task at hand. Have you ever considered creating a version of the Taxonomy Filter as a PHP block? (I tried to make my own, but couldn't with my limited PHP skills. Incidentally, do you know how to determine the Vocabulary ID being viewed from a block?)
Comment #3
styro commentedThanks for the feed back - it's nice to know that someone finds it useful :)
What do you mean by "as a PHP block"? Do you mean making your own block that then uses the module output (ie the lists of term links) somewhere inside it?
If you want to call the output from your own block, you could try something like this in your own block:
also (or even instead of), you could override the modules theme_* functions in your own theme to customise the output of some of the bits inside the output. I have some ideas for improving the themability a bit more in future versions too.
The module looks at the url to figure out what term ids are being viewed, and it looks up the vocabs from the term ids. I'm not aware of any specific API to look that info up directly (eg in a block) though.
Also - an update on 5.0 status: I now intend to update it for 5.0 (after a 5.0 RC comes out) and keep using it myself. I've got some more (fuzzy at this stage) plans for some extra features too :)
Comment #4
styro commentedAssigning to myself.
Comment #5
talkingwires commentedHeh. By the way, thanks for your reply in my other thread. I've got my little block up and running thanks to your meticulous examples.
Comment #6
styro commentedJust an update on the status of this issue.
I haven't started porting to 5.0 yet - instead I've been working on a big rewrite (of the 4.7 version) adding lots of new features. I plan to start porting after the new 4.7 version is released and debugged etc. Hopefully a 5.0 version should only be a couple of weeks away.
Comment #7
moonray commentedI was trying out some things and wound up porting this module to drupal 5.
Find patch attached.
Comment #8
styro commentedGreat, thanks. I was looking through the porting to 5.0 docs, and just thinking how there wasn't that much to change and the size of your patch bears that out.
While I haven't tested the patch, I'm happy with all the code changes based on looking through them. Although in the .info file, I think the "packages" line should be removed as the module isn't part of a package http://drupal.org/node/101009
Would you (and anyone else interested in a Drupal 5.0 version) prefer a 5.0 compatible branch now, or after TF 3.0 is finally released? There are still one or two minor features I'd like to add to TF 3.0. Personally I would prefer to branch later after finishing TF 3.0 to minimise porting of features between the two branches as well as I'm not able to do much in the way of serious 5.0 testing yet.
But I'm also willing to give CVS access to anyone who wants to help look after the 5.0 branch (ie testing on Drupal 5.0 and forward porting of features added to TF 3.0) in the meantime. Let me know.
Comment #9
moonray commentedI'm not actually going to be using this module. But I was testing out some of its functionality, which I may borrow from. Just thought I'd share the work I did for testing... ;-)
Comment #10
moonray commentedAs far as the package is concerned, there are other packages in the "taxonomy" section that aren't shipped with core. It's the logical place to look for it, specially since it extends taxonomy, and depends on it.
Just my 2 cents.
Comment #11
styro commentedHEAD now contains a Drupal 5 compatible version. An official release will happen shortly - test reports welcome.
Comment #12
coupet commentedconfirms Head works perfectly in Drupal 5.1 version.
Suggested features:
- Provide single select option in Menu type
How to display multiple menu type filters on top on taxonomy results (similar to exposed filters in Views)?
Darly
Comment #13
styro commentedThanks for testing the Drupal 5 version. I intend to make an official release this week.
Also, thanks for the feature request. Could you please start a new issue for that :)
Comment #14
(not verified) commented