We have page, and beneath it we have lots of child content. This is good, urls for the children are page/child, page/child1 and so on.
However there are lots of those children and we would like to group them so that structure would be: page/group1/child1 page/group1/child2 page/group2/child3 and so on... This is easily done using some pages as containers. However such containers affect url, and the url for the page becomes page/group2/child3, however we still want it to be page/child3.
I can archieve that using partial router and I have implemented it based on this post. http://joelabrahamsson.com/custom-routing-for-episerver-content/
However one problem remains, sibling routes are not modified, so if we have some sibling under child1, it's route still contains /gruop1 segment. This is undesirable. Is there some way to fix this? It seems EPiserver is not continuing to route remaining parts parts of the url. This seems to be bug.
Here is the problem:
We have page, and beneath it we have lots of child content. This is good, urls for the children are page/child, page/child1 and so on.
However there are lots of those children and we would like to group them so that structure would be:
page/group1/child1
page/group1/child2
page/group2/child3
and so on...
This is easily done using some pages as containers. However such containers affect url, and the url for the page becomes page/group2/child3, however we still want it to be page/child3.
I can archieve that using partial router and I have implemented it based on this post. http://joelabrahamsson.com/custom-routing-for-episerver-content/
However one problem remains, sibling routes are not modified, so if we have some sibling under child1, it's route still contains /gruop1 segment. This is undesirable. Is there some way to fix this?
It seems EPiserver is not continuing to route remaining parts parts of the url. This seems to be bug.
Regards,
Giedrius