Umbraco Url Redirect for renamed nodes of Virtual Parent
Hi there,
I'm finding that when you rename a node that has a virtual parent that the Umbraco Url Redirect is broken as it does not recognise that the containing node is a virtual one and as a result, it includes the virtual node segment in the Original Url.
Navigating to the original url without the virtual node segments produces a 404 instead of a redirect to the new url.
To make sure I have understood, your issue is with the Url Redirect Manager, not with the virtual node per se. Meaning that the both the urls for the "old" and the "new" node's name under the virtual parent work, but they won't both work since the URL tracked will unexpectedly contain the virtual node.
If this is the case, then yes, it's a problem I faced ever since the Url Redirect Manager came into play. Unfortunately I have no ready solution for this yet.
Yes, if the old URL (that has a parent virutal node) is navigated to you will get a 404 because Umbraco Url Redirect is unaware it should treat the virtual node as such and so retains the virtual node path segment as part of the redirect URL.
I'm not sure how the Url Redirects work. Ideally there would be an event that could be hooked into when a redirect is being created at which point it could be checked if a segment of the path was virtual and if that's the case remove it from the redirect that's being saved... ideally... :)
Umbraco Url Redirect for renamed nodes of Virtual Parent
Hi there,
I'm finding that when you rename a node that has a virtual parent that the Umbraco Url Redirect is broken as it does not recognise that the containing node is a virtual one and as a result, it includes the virtual node segment in the Original Url.
Navigating to the original url without the virtual node segments produces a 404 instead of a redirect to the new url.
Cheers,
Alan
Apologies for the very late response.
To make sure I have understood, your issue is with the Url Redirect Manager, not with the virtual node per se. Meaning that the both the urls for the "old" and the "new" node's name under the virtual parent work, but they won't both work since the URL tracked will unexpectedly contain the virtual node.
If this is the case, then yes, it's a problem I faced ever since the Url Redirect Manager came into play. Unfortunately I have no ready solution for this yet.
Yes, if the old URL (that has a parent virutal node) is navigated to you will get a 404 because Umbraco Url Redirect is unaware it should treat the virtual node as such and so retains the virtual node path segment as part of the redirect URL.
I'm not sure how the Url Redirects work. Ideally there would be an event that could be hooked into when a redirect is being created at which point it could be checked if a segment of the path was virtual and if that's the case remove it from the redirect that's being saved... ideally... :)
is working on a reply...