Redirects not working properly on multilingual site
Unfortuatenely URL Tracker is not working quite as expected for my multilingual site. When for example renaming a node in the content editor, the "Old URL" is set properly. On the other hand, whenever an 404 error occurs on the site the "Old URL" is just set to the query (and not the hostname), for example:
I have been investigating the issue a bit further, and have not found a solution. However, I have noticed that whenever a 404 error is found, it is not added as the correct site on which it occured. No matter which site (.dk, .com or .de) it is always registered as if it occured on the .dk site. And yes, each site has an associated hostname set.
It seems to me as the hostname is not registered, causing Url Tracker to register the "Old URL" as "http/a-page-not-found/".
Below are some entries from the tracelog with logging enabled for Url Tracker (some information has been omitted):
When entering the "Old URL" manually, the redirect is working properly, but only for my .dk domain. For the other sites, the redirects are not working at all.
Redirects not working properly on multilingual site
Unfortuatenely URL Tracker is not working quite as expected for my multilingual site. When for example renaming a node in the content editor, the "Old URL" is set properly. On the other hand, whenever an 404 error occurs on the site the "Old URL" is just set to the query (and not the hostname), for example:
http://www.mysite.com/test
redirects to:
http/test/
If I try to add the 404 as a permanent redirect, the "Old URL" just stays the same.
Below are entries for urlRewriting.config:
I'm not so confident in those rewrites, and wonders if some information are lost in the process?
From web.config
And the following from 404handlers.config
Please let me know if you need any other information :)
Best regards
Stefan
I have been investigating the issue a bit further, and have not found a solution. However, I have noticed that whenever a 404 error is found, it is not added as the correct site on which it occured. No matter which site (.dk, .com or .de) it is always registered as if it occured on the .dk site. And yes, each site has an associated hostname set.
It seems to me as the hostname is not registered, causing Url Tracker to register the "Old URL" as "http/a-page-not-found/".
Below are some entries from the tracelog with logging enabled for Url Tracker (some information has been omitted):
When entering the "Old URL" manually, the redirect is working properly, but only for my .dk domain. For the other sites, the redirects are not working at all.
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.