2 different taxonomy_term views with same path for 2 different vocabularies
Hi guys,
I currently have two different vocabularies (vA and vB).
Vocabulary_A is associated with content type, Content_A; Vocabulary_B is associated with content type, Content_B.
I created two view pages under taxonomy_term views, one for Vocabulary_A, and one for Vocabulary_B. Both have the same page view path: taxonomy/term/%, but each view page has different "Taxonomy: Term ID (with depth)" argument with "taxonomy term" validator. Like the Vocabulary_A page view has "taxonomy term" validator = Vocabulary_A box checked, and Vocabulary_B page view has "taxonomy term" validator = Vocabulary_B box checked. Rest argument settings remain default.
Now the view page only works for Vocabulary_A, but it doesn't work Vocabulary_B. Every time when I go to a term under Vocabulary_B, it always shows "Page Not Found".
Does anyone know how to fix this problem? Do I need to set any other argument to make this work? It seems like there's some argument not passing through the url. I hope I have explained it.
Many Thanks,
Jerry

Please help guys
Please help guys
Could someone please help me
Could someone please help me on this? or can this be done?
Thanks so much!
Solved: Taxonomy Redirect is the answer
I was facing similar issue and i came across a module called "Taxonomy Redirect"
1) Using above module create a redirect path for each vocabulary
i.e. for vocabulary1 > category1/term/!tid
for vocabulary2 > category2/term/!tid
2) Create views for each vocabulary using above path instead of taxonomy/term% now use category1/term/% and so for category2 use category2/term/%
That's it, all done, you can now have different style and look for both of your vocabulary node listing..
Jackie Rana
Yea, I actually realize that
Yea, I actually realize that module before, but I just thought views can probably do the job if I set the argument correctly. I guess it can't be done in views since no one else know the answer to that.
I guess I will just use Taxonomy module to solve the problem then.
Thanks
Is there a way that this can
Is there a way that this can be done in Views 2?
i'm using views dev 3.x but
i'm using views dev 3.x but even there this seems imposible. Driving me crazy.