Don't miss out Virtual Happy Hour this Friday (April 26).
Try our conversational search powered by Generative AI!
AI OnAI Off
Don't miss out Virtual Happy Hour this Friday (April 26).
Sorry, I'm NOT using:
CatalogRouteHelper.MapDefaultHierarchialRouter(routes, true);
I'm using false instead, to make hierarchical URL's:
CatalogRouteHelper.MapDefaultHierarchialRouter(routes, false);
Hi,
If you're using CatalogRouteHelper.MapDefaultHierarchialRouter and your catalog is named "Products" then the url http://myshop.local/da/products/ should point to page with renderer of CatalogContent. I assume you're missing that page type, hence the 404 error. Can you try to add it to see if it works?
Regards.
/Q
Hi,
Thanks - Apparently it works if I make a controller that uses the CatalogContent instead of NodeContentBase.
But my colleague has a similar project that works with the NodeContentBase, so I'm a little confused why it does not work that way in my project.
Best regards
Rasmus
Hi,
I am using the default routing according to this documentation: http://world.episerver.com/documentation/Items/Developers-Guide/EPiServer-Commerce/8/Routing/Routing/
But I am having trouble getting it to work at all.
I have the following controller:
I also have a catalog called "Products" with the "Name in URL" called "products".
When I try to request the products page I request the following URL: http://myshop.local/da/products/ that is also the url the backend refers to when clicking "View on website".
But it does not get to the controller. I just get the default "HTTP Error 404.0 - Not Found" with the "StaticFileHandler", just like any other random url that does not exist.
The routing for content pages works perfectly.
Does anyone have a clue what could be the problem here?
Thanks
Rasmus