Jump to:
| Project: | Taxonomy Redirect |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | support request |
| Priority: | major |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
I'm encountering a strange problem where newly created taxonomy terms of a vocabulary with a taxonomy redirect rule don't have the redirect rule for their vocabulary properly applied, even though the rule does apply to all existing terms in the same vocabulary.
So, with a vocab 'Clients' and a rule to redirect to client/!name, all existing terms when this rule was created redirect to client/some-client as expected, but newly created terms just go to category/clients/some-client
What makes this stranger is that Taxonomy Redirect does clearly know that these new terms are in its scope. If I change the rule to client/!name#a, all old terms go to client/some-client#a, and all new terms go to... category/clients/some-client#a !!
So it seems Taxonomy Redirect is either trying and failing to apply the rule, or, it's being overruled by something - but only for certain terms.
Any idea what could overrule Taxonomy Redirect like this? I have no term-specific rules in taxonomy redirect, and only a handful of taxonomy related modules active (NAT, Taxonomy Defaults). I've disabled all pathauto taxonomy rules and re-created the problem taxonomies, but that makes no difference.
In case it's relevant, the display in question is in a Views 'Taxonomy: All Terms' field, and it's different rows of exact the same view field that have the strangely different results. The same results happen if I use a php field
<?php
print "client/" . $tname
?>
Comments
#1
Hm, strangely, after a about an hour the rule has started applying as expected. I think the steps needed to fix this were removing all pathauto defaults including generic ones, deleting the terms, recreating them, clearing caches etc, then waiting... I can't see why a time delay made any difference but it seems to work now.
#2
I as well am also having this problem.
When I add a new term, the redirect does not work...as stated by alanomaly, deleting the redirect, and all of the url aliases, then adding them back fixes the problem.
#3
OK, here is a "fix".
Do not use pathauto to alias the taxonomy term path you wish to redirect to, and do not set a default path pattern, only set a path pattern for other terms you do wish to alias (if you are using more than one vocabulary on your site).
Simple really...
#4
The problem I had with redirects suddenly stop working, and finally managed to solve, had to do with Views Term Path Override module.
After saving any view, Views TPO would reset all vocabulary overrides that were set by Taxonomy Redirect to default module handler 'taxonomy' in 'Vocabulary' table.
Disabling the Views TPO module solved the issue.
Hope this helps someone else who stumbles upon this thread.
#5
Behavior also observed for renaming existing terms...
Re-opening issue because I don't think the workarounds mentioned should be required to make this work (though I will try them out if possible).