A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More

Magnus von Wachenfeldt
Feb 17, 2010
  7347
(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

Please login to comment.
Latest blogs
Building simple Opal tools for product search and content creation

Optimizely Opal tools make it easy for AI agents to call your APIs – in this post we’ll build a small ASP.NET host that exposes two of them: one fo...

Pär Wissmark | Dec 13, 2025 |

CMS Audiences - check all usage

Sometimes you want to check if an Audience from your CMS (former Visitor Group) has been used by which page(and which version of that page) Then yo...

Tuan Anh Hoang | Dec 12, 2025

Data Imports in Optimizely: Part 2 - Query data efficiently

One of the more time consuming parts of an import is looking up data to update. Naively, it is possible to use the PageCriteriaQueryService to quer...

Matt FitzGerald-Chamberlain | Dec 11, 2025 |

Beginner's Guide for Optimizely Backend Developers

Developing with Optimizely (formerly Episerver) requires more than just technical know‑how. It’s about respecting the editor’s perspective, ensurin...

MilosR | Dec 10, 2025