When I add a Url into Skybrud in the Original Url field that is a current page in the website, and then select a Destination node from the link picker, the redirect doesn't work.
If I enter a Url in the Original Field that doesn't exist and then select a node in the Destination field, the redirect works as expected.
And if I enter the Url for both pages without picking a node, it works fine. It's as though there are extra checks going on for when I pick a node, versus entering a raw Url.
So thats:
Existing Node Url to Existing Node selected from the tree - doesn't work
Fake Url to Existing Node selected - works
Existing Node Url to Existing Node Url not selected from tree - works as expected.
Is this desired logic or is this a bug or do I need to hit a setting somewhere?
This is a very vanilla instance of Umbraco with no custom routing or content finders.
My client wants to redirect a page that does exist in the Umbraco tree to another page in the Umbraco tree.
As you have only provided a text box for the original URL, they enter the current Umbraco node URL there.
They want to use the link picker you provide in your plugin so that future page moves of the destination page don't need them to update the redirect manually.
But your plugin doesn't allow that? And ignores what the client has picked in the URL picker and sends them to the original page.
Yet if you enter a destination URL directly without the node picker, it does work.
So out of the box Umbraco has content finders, that's how it routes traffic to pages.
Based on this statement of yours My client wants to redirect a page that does exist in the Umbraco tree to another page in the Umbraco tree this "shouldn't" work because the original url is for a page that exists in the site.
As a result the underling standard Umbraco routing would return a 200 response, this tells the skybrud middleware to not look for any redirects and just return the current response - which sounds like the behaviour you are seeing.
This part of what you are saying is a little more confusing:
They want to use the link picker you provide in your plugin so that future page moves of the destination page don't need them to update the redirect manually. But your plugin doesn't allow that? And ignores what the client has picked in the URL picker and sends them to the original page. Yet if you enter a destination URL directly without the node picker, it does work.
Are you saying that if you "pick a page" as the destination and then move that page in the CMS the redirect doesn't update to use the new URL?
Skybrud.Umbraco doesn't redirect the way expected
Hello,
When I add a Url into Skybrud in the Original Url field that is a current page in the website, and then select a Destination node from the link picker, the redirect doesn't work.
If I enter a Url in the Original Field that doesn't exist and then select a node in the Destination field, the redirect works as expected.
And if I enter the Url for both pages without picking a node, it works fine. It's as though there are extra checks going on for when I pick a node, versus entering a raw Url.
So thats:
Is this desired logic or is this a bug or do I need to hit a setting somewhere?
Help!
Hi Colin,
This is the desired behaviour for Skybrud Redirects.
It only kicks in the all the natural routing for Umbraco and any custom content finders etc return a 404 response.
Thanks
Nik
I am a bit confused then.
This is a very vanilla instance of Umbraco with no custom routing or content finders.
My client wants to redirect a page that does exist in the Umbraco tree to another page in the Umbraco tree.
As you have only provided a text box for the original URL, they enter the current Umbraco node URL there.
They want to use the link picker you provide in your plugin so that future page moves of the destination page don't need them to update the redirect manually.
But your plugin doesn't allow that? And ignores what the client has picked in the URL picker and sends them to the original page.
Yet if you enter a destination URL directly without the node picker, it does work.
That doesn't feel logical to me.
Hi Colin,
So out of the box Umbraco has content finders, that's how it routes traffic to pages.
Based on this statement of yours
My client wants to redirect a page that does exist in the Umbraco tree to another page in the Umbraco treethis "shouldn't" work because the original url is for a page that exists in the site.As a result the underling standard Umbraco routing would return a 200 response, this tells the skybrud middleware to not look for any redirects and just return the current response - which sounds like the behaviour you are seeing.
This part of what you are saying is a little more confusing:
They want to use the link picker you provide in your plugin so that future page moves of the destination page don't need them to update the redirect manually. But your plugin doesn't allow that? And ignores what the client has picked in the URL picker and sends them to the original page. Yet if you enter a destination URL directly without the node picker, it does work.Are you saying that if you "pick a page" as the destination and then move that page in the CMS the redirect doesn't update to use the new URL?
Thanks
Nik
is working on a reply...