The popular NotFound handler for ASP.NET Core and Optimizely, enabling better control over your 404 page in addition to allowing redirects for old URLs that no longer works.
Is there any reason for not supporting the scenario where an editor changes the slug of a page which has children, which normally results in all those children getting new urls and old urls breaking?
Is there any reason for not supporting the scenario where an editor changes the slug of a page which has children, which normally results in all those children getting new urls and old urls breaking?