This way, product URLs could be /category-name/product-name. Or category names could be /root-category/child-category
the workaround for that is for GenericPathRoute to map to {*generic_name} rather than {generic_name} I believe.
But sure but please note after addition of such custom route ALL controllers and routes should be also registered. For example, somecontrollersomemethod. Otherwise, customers will be redirected to this new {*generic_name} route handler. Also think about processing of 404 errors for such cases. Some investigation required
UPDATE: each missing static ressource like /content/files/missingfile.pdf is catched by GenericPathRoute, it's not a big problem, but I'm not sure of the consequences.
see (several posts) - http://www.nopcommerce.com/boards/t/29637/performance-optimization-needed-nopcommerce-is-too-slow-.aspx?p=7#123632
vote++;
I initially thought I wanted a /category/product route too.
However I remember that NopCommerce supports multiple categories,
so would /Brand/Product be a more reliable suggestion?
Maybe ideally if we had a route such as this: /Brand/Category?/Product, where it would only display the category if it was the only category the product was in.
Thoughts?
Most helpful comment
vote++;