Hi,
rutra:
when i add a new product by hand i always get a proper url mydomain.com/category/product
but most of my products are imported from my suplier's database and his categories in imported file are different than mine.
That's not a great idea IMO. If it's a regular (standardised) thing I'd simply reprogram the import software to put the products straight into the appropriate categories.. i.e. remap the IDs when importing.. can't be too hard to do.
rutra:
after an import i move all products to my categories.
Then you have changed the "context" of where the products are. They are no longer in their main categories, but in "linked" categories.
As such, Ceon URI Mapping is smart enough to see this and the cPath is used to maintain the user's "context" on the site.
rutra:
when moving i get an info from ceon module that new url was created : mydomain.com/category/product but when i check from index page clicking category then product i always get mydomain.com/category/product?cPath=number with the number of the master category, it's undersood and aceptable for me.
Oh, okay. I'd rather not have cPath if I didn't have to, which you don't appear to have to really, the reason for the "linked" usage being more of a technical issue in what you've described above.
rutra:
but when i choose some of these product to be Featured Products and appear on an index page all links shows without ?cPath=number, just simply mydomain.com/category/product
so right now same product page in my store has two different urls - is it normal or i'm doing something wrong?
No, you see two different ones as the cPath is used to maintain context in a linked category, but when a product is shown anywhere else on the site the cPath isn't needed as the product isn't in a category, it's independent of the current address.
This isn't a problem as Ceon URI Mapping has full canonical support built in.. search engines see all variations of a product's URI - with however many different cPath values - as the same URI.. check a product's info page and you'll see the "canonical" tag which is all the search engines care about.. they ignore all the additional query string parameters, like cPath.
Handy this module is sometimes :)
Hope that sets your mind at rest!
I'd still adjust your import methodology if I was you though.. simply to make things "look" better. Why not, if it can be automated? :)
All the best..
Conor
ceon
