Magnus von Wachenfeldt
Feb 17, 2010
visibility 7680
star star star star star
(1 votes)

Update to the Url Mapping Module

I previously wrote about a module for responding with correct status codes.

I’ve added some more functionality to it, making it able to handle descendants and moving pages from the waste basket. I also refactored out some logic from SimpleSqlUrlMapper, making IUrlMapper a little more dumb and thus easier to consume and add your own implementation.

Give it a shot and tell me what you think!


Feb 17, 2010

Comments

Apr 3, 2017 11:15 AM

error Please login to comment.
Latest blogs
Composition Over Inheritance: Why Your Content Contract Is Not a Base Class

Inside the structural conformance pattern in SaaS CMS — from server-side inheritance to pipeline governance. A contract in Optimizely SaaS CMS is...

Vipin Banka | Sep 19, 2026

Optimizely Opti ID Integration: Why the API Key Was Missing from the DXP Management Portal

While working on an Optimizely CMS 12 Opti ID integration recently, we ran into an issue that initially appeared to be related to SSO authenticatio...

Madhu | Sep 18, 2026 |

Extending a Contract: What You Can Override

Contracts share fields across content types — but not every field setting can be overridden. Push the same contract onto several components, and CM...

Chirag Khanna | Sep 18, 2026 |

Building a Blazor Server UI Inside the Optimizely CMS 13 Admin Shell

What I learned shipping a Blazor Server UI inside Optimizely CMS 13 — Razor components in a NuGet package, the Blazor hub next to MapContent(),...

Stanisław Szołkowski | Sep 17, 2026 |