We have a multi-site installation under a single Umbraco instance.
The sites are configured so that the roots of the different sites point to different paths under the same domain.
e.g. Main site -> www.xyz.com
Latin site -> www.xyz.com/la
Mexico site -> www.xyz.com/mx
Node change detection works correctly for the main site. The redirect record gets attributed to the correct RedirectRootNodeId for the main site.
e.g. for Main site, /abc -> /mno
Redirect record: Old URL (abc), RedirectRootNodeId (Root node Id of main site)
However, for any nodes under the other sites, when a node changes, the redirect record has the correct RedirectRootNodeId but the OldUrl field still prepends the main segment of the path to the url value.
e.g. for a change under /mx site from /abc -> /mno
Redirect record: Old URL (mx/abc), RedirectRootNodeId (Root node Id of mexico site)
This causes the redirect to not take effect correctly and it 404s.
We have a multi-site installation under a single Umbraco instance. The sites are configured so that the roots of the different sites point to different paths under the same domain. e.g. Main site -> www.xyz.com Latin site -> www.xyz.com/la Mexico site -> www.xyz.com/mx
Node change detection works correctly for the main site. The redirect record gets attributed to the correct RedirectRootNodeId for the main site. e.g. for Main site, /abc -> /mno Redirect record: Old URL (abc), RedirectRootNodeId (Root node Id of main site)
However, for any nodes under the other sites, when a node changes, the redirect record has the correct RedirectRootNodeId but the OldUrl field still prepends the main segment of the path to the url value. e.g. for a change under /mx site from /abc -> /mno Redirect record: Old URL (mx/abc), RedirectRootNodeId (Root node Id of mexico site)
This causes the redirect to not take effect correctly and it 404s.