damiantaylor:
Hi all!
I have ntoiced a slight problem with the cPath extension appended to the end of the mapped URIs.
I have a product that has a master category of 100.
If I link that product to another category with a higher number (say 120), everything still works as expected.....
When I visit the product page under the master category on my website, the URI has no cPath extension.
When I visit the product page under the linked category on my website, the URI does have the cPath extension. Nothing wrong here.
If I now link the product to a category with a LOWER number (say 80), I have a problem.....
When I visit the product page under the master category on my website, the URI now has a cPath extension.
When I visit the product page under the new linked category (category 80) on my website, the URI does not have the cPath extension.
It's as though URI mapping is taking the lowest category number rather than the master category number as the main category for the product.
This doesn't seem right to me. I'm not on the latest version of URI mapping so this could already be fixed!
Has anyone else ever noticed this one?
conor:
Hi,
Sorry, there's no logical reason for that to happen and it's not been reported by anyone else. I can't explain it but doubt it's anything to do with the module.
All the best...
Conor
ceon
Hi, Ceon,
yes, actually the same problem hit me. originally the product NO. 1 is in category A, category ID is 23, but after linked one product No.1 to category B, id is 20, problem occur. the product No. 1(without cPath=) have gone to category B, id 20. however, the original product No. 1 is with cPath in it's URL.
any suggestions? how to remove the cPath? thank you.