multilingual site: not redirecting to renamed node?
hi
We've come across a potential problem with Url Tracker in a
multilingual environment structure (ie multiple content trees).
Given the content structure “Site 1->Parent
Page->Child Page” if the parent page is renamed, then 301 rules are recorded
and requests for both parent and child are redirected to their respective new
Urls.
If the same type of rename change is applied to Site 2, the
user isn’t redirected to the new Url, instead the Umbraco 404 is served out.
This may only apply to sites running on a port other than the default (80), but I noticed on line 117 of UrlTrackerModule.cs that you’re using “request.Url.Host” rather than “request.Url.Authority”. This means that any port number in the url is lost, therefore the domain matching condition on line 124 will fail.
This might explain the bug I’ve originally reported here, because when no root node Is found (line 139) then the first node is assumed which isn’t entirely correct in a multilingual site scenario.
multilingual site: not redirecting to renamed node?
hi
We've come across a potential problem with Url Tracker in a multilingual environment structure (ie multiple content trees).
Given the content structure “Site 1->Parent Page->Child Page” if the parent page is renamed, then 301 rules are recorded and requests for both parent and child are redirected to their respective new Urls.
If the same type of rename change is applied to Site 2, the user isn’t redirected to the new Url, instead the Umbraco 404 is served out.
Is this a known issue?
Thanks
hi kipusoep, have you chance yet to determine if this is a bug? thanks
hi - does anyone have a multilingual site they could try this on? thanks
Just confirmed this is still an issue on version 2.6.2.
Hi Kipusoep,
This may only apply to sites running on a port other than the default (80), but I noticed on line 117 of UrlTrackerModule.cs that you’re using “request.Url.Host” rather than “request.Url.Authority”. This means that any port number in the url is lost, therefore the domain matching condition on line 124 will fail.
This might explain the bug I’ve originally reported here, because when no root node Is found (line 139) then the first node is assumed which isn’t entirely correct in a multilingual site scenario.
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.