U4-9525 - Create Redirects with Correct URL's When Renaming with Custom URL Provider

Created by Nicholas Westby 14 Feb 2017, 01:49:42 Updated by Alan Mac Kenna 05 Jul 2018, 17:25:00

Relates to: U4-8802

When renaming a page, this redirect got created in umbracoRedirectUrl:


Based on the custom URL provider I created, this is the actual redirect that should have been created:


In fact, based on how the URL provider works, several redirects probably ought to be created:

1089/en-us/main/products-overview/accessories/item 1089/fr-us/main/products-overview/accessories/item

The "1089" is (as expected) the homepage node ID. It seems the redirect tracking functionality built into Umbraco does not work with the URL provider.

1 Attachments


Stephan 15 Nov 2017, 14:05:23

custom url providers are indeed not supported - so this = feature request, implement support for custom url providers in redirects

Dennis Aaen 15 Nov 2017, 15:23:34

@zpqrtbnk Would it be possible to perhaps add some info about in which version we expected this to be fixed?

simone chiaretta 15 Dec 2017, 11:50:35

@Shandem this affects also articulate (https://github.com/Shazwazza/Articulate/issues/283)

In Articulate there is a url provider that add the date of the post in the url. So if post has title "my blog post", published on 15/12/2017, it's url is /archive/2017/12/15/my-blog-post (while the standard url without urlprovider would be /archive/my-blog-post

But if I rename the post to "my amazing blog post", the redirect rule created has the correct new url /archive/2017/12/15/my-amazing-blog-post but the "source" url is without the urlprovider So it redirects from /archive/my-blog-post => /archive/2017/12/15/my-amazing-blog-post, which will never happen.

I think this is either a bug, or missing documentation on how to properly implement custom urls to please the redirect module

Alan Mac Kenna 05 Jul 2018, 17:25:00

Is this fix on the roadmap? I have the below site structure and with a Custom Url Provider to remove the "content" segment it means that if any content page is renamed the redirect will not work, which in effect means the utility of the 301 redirect feature is lost for most of the site.

-Website --Shared Content --Content ---Home ---Posts ----My blog post ---About ---Contact

Priority: Normal

Type: Bug

State: Submitted


Difficulty: Normal


Backwards Compatible: True

Fix Submitted:

Affected versions: 7.5.9

Due in version:


Story Points: