Hey there, I really think this module is exactly what I need. I created a custom view that replaces the taxonomy/term view... This view normally (internally) passes and expects termID (tid) but the views and the corresponding Tid's (200 terms possible) have been replaced by aliases.

So instead of having photos/18 I have photos/canada as the url. I think the module cannot see the tid behind the alias, so this would mean that it does not use the internal url of a page, but the aliased url?

Is there any workaround you would suggest, so I would be able to see all related terms even tho the tid is not explicitely in the url??

Thanks for what seems to be a great module!

Patchak

Comments

styro’s picture

styro commented

Works fine for me when I add aliases for listing pages (for both listings from the standard taxonomy module and a custom module).

The module is written to respond to the underlying url not the alias, but when rendering the menu of links will output aliases for any urls that have them. The underlying url to respond to is configurable as well, so it works with custom modules and views provided their underlying urls list the tids with commas between them eg ../term1id,term2id/.. etc.

What settings do you have here: /admin/settings/taxonomy_filter ?

What are the underlying urls for your views pages?

patchak’s picture

patchak commented

Hi thanks for the quick answer!

My underlying url with views is photos/$arg. So for example photos/18 would be spain, or whatever. I configured this module so that it listens to : photos/$tids and still I get no terms showing in the block.

You have any idea what could have gone wrong??
Thanks

styro’s picture

styro commented

I suspect it is something to do with the way views works (note: I don't use views, so I'm a bit ignorant about this) and what the underlying urls actually are (ie the ones grabbed by hook_menu). I suspect /photos/%tids isn't the actual underlying url, and is actually another layer of internal views aliasing.

Is it possible to insert some debugging PHP somewhere in one of your views? If you could print out what arg(0), arg(1) etc are that would give me an idea of what the underlying urls actually are. Taxonomy Filter uses the arg(n) function internally to assemble the underlying url.

http://api.drupal.org/api/function/arg/5

patchak’s picture

patchak commented

HI there,

It's true that I use the taxonomy redirect module to redirect all the terms from a certain vocab to that custom view i use. I'll try to insert that code and see what are the real args behind that. Thanks for the help.

styro’s picture

styro commented
Status: Active » Closed (won't fix)

Just closing off some old issues. Please reopen if still a problem in latest supported versions.