Refine by taxonomy: D6 port via Deadwood-module

this is not a patch. http://drupal.org/patch/create

I would need this module too for my D6 site... if it´s not a patch... what is it? Could it be used in a production site? What does Bér thinks of it?
What about the security announcement?

BTW, I´ve tried it on a test D6 site and seems to work just fine. I´m just worried because I need it for a production site, and I´ve recently find that security announcement...

I'm interested in it, too.

There´s this other module (Faceted Search [D6 version is being worked out]), but I think isn´t as easy as Refine by Taxo is.

I've made a patch of the version posted by motto. This is the first patch I've made, if I did any mistakes I'd be happy for pointers on what do to differently next time.

I've tried it (briefly, with a very small vocab), and it works. Demo at http://www.pvv.ntnu.no/~zirvap/sandkasse/

Coder module had the following comments:

• Line -1: @file block missing (Drupal Docs)
• Line 1: Include the CVS keyword $Id$ in each file. This should be in the format // $Id$ or // $Id$ (Drupal Docs)//$Id: refine_by_taxo.module,v 1.9.2.2 2008/08/26 16:30:00 Exp $
• Line 167: string concatenation should be formatted without a space separating the operators (dot .) and a quote $replacement = '$0' . $splitter . $refine_tid;
• Line 193: string concatenation should be formatted without a space separating the operators (dot .) and a quote $sql = db_escape_string('SELECT DISTINCT tn.tid FROM {term_node} tn INNER JOIN {term_data} td ON td.tid = tn.tid WHERE' . $conditions);

Yet another module you can try with similar functionality
http://drupal.org/project/taxonomy_filter

Thanks, motto and zirvap, I'm using refine by taxonomy again after my upgrade to Drupal 6. So far I haven't found any problem, just a minor issue:

I have a taxonomy for "YEARS" wich is not multiselectable, so only one year tag per node. If I go to the taxonomy page for 1990, for example, refine by taxonomy outputs a filter showing "1991" wich is a)impossible b)weird since none of the nodes had this 1991 tag. Could be possible that refine by taxonomy is using the terms history for the nodes?

For me, refine by taxonomy is more user admin friendly than other modules since it's really simple to install and configurate.

Regards.

Although the module seems to work perfectly for the main admin, I'm getting this error when I try to see the taxonomy page from other roles: