Multiple root nodes with bound host names and weird page lookups
Any help with this would be appriecated, I feel we're missing something! This site is on Umbraco v4.9 (patched).
Consider the following tree with hostnames bound at the root level.
Content
Home1 - www.domain1.co.uk
Node1-1
Node1-2
Node1-2-1
Node1-2-2
Node1-3
Home2 - www.domain2.co.uk
Node2-1
Node2-2
Node2-3
At the moment if we visit www.domain2.co.uk/Node1-2 we are shown the content from the node found under Home1.
The real world example is a contact-us page and the trace is below. When we requestthe contact-us page from a host bound node where it doesnt exist Umbraco othen continues to lookup under /root/*/* [@urlname="contact-us"] where it'll find the other contact us page, is this normal?
Prior to 4.10 the domains are an "indication" of where to look for content but Umbraco also looks in the whole tree... Starting with 4.10 once a domain is found, the search is restricted to the subtree under that node.
Multiple root nodes with bound host names and weird page lookups
Any help with this would be appriecated, I feel we're missing something! This site is on Umbraco v4.9 (patched).
Consider the following tree with hostnames bound at the root level.
Content
Home1 - www.domain1.co.uk
Node1-1
Node1-2
Node1-2-1
Node1-2-2
Node1-3
Home2 - www.domain2.co.uk
Node2-1
Node2-2
Node2-3
At the moment if we visit www.domain2.co.uk/Node1-2 we are shown the content from the node found under Home1.
The real world example is a contact-us page and the trace is below. When we requestthe contact-us page from a host bound node where it doesnt exist Umbraco othen continues to lookup under /root/*/* [@urlname="contact-us"] where it'll find the other contact us page, is this normal?
Thanks
Know 4.9 bug.
Prior to 4.10 the domains are an "indication" of where to look for content but Umbraco also looks in the whole tree... Starting with 4.10 once a domain is found, the search is restricted to the subtree under that node.
Darn, I didnt know that.
Thanks Stephan
is working on a reply...