Hi,
burningice wrote:
So far, so good. Of course - now things happened as I have expected: Page links within the page content are in usual internal format ("~/page(<ID>)") and are rendered to their friendly URLs. Now I wonder, if I can provide custom logic to this rendering process to have each link being rendered with the shortcut of my exhibition - to not loose my exhibition context.
In other words: can I modify URL rendering in a way to transform URLs from "~/page(<ID>)" to "/locale/<exhibition>/path/to/my/page" instead of "/locale/path/to/my/page"?
burningice wrote:
While the latter is more technical correct, there has been no projects AFAIK which have tried to implement a custom PageUrlProviderSo - finally I've been successful in putting my logic into a custom HttpModule. I queried for an exhibition via DataConnection, got a result, stripped off the exhibition shortcut from the incoming url path and Context.RewritePath to the stripped url. Worked fine and I landed on the expected page where I accessed my selected exhibition, which I had put into Context.Items in my HttpModule.
So far, so good. Of course - now things happened as I have expected: Page links within the page content are in usual internal format ("~/page(<ID>)") and are rendered to their friendly URLs. Now I wonder, if I can provide custom logic to this rendering process to have each link being rendered with the shortcut of my exhibition - to not loose my exhibition context.
In other words: can I modify URL rendering in a way to transform URLs from "~/page(<ID>)" to "/locale/<exhibition>/path/to/my/page" instead of "/locale/path/to/my/page"?