but user is able to access url like this: www.example.com/directory/skpage which isn't what I want to allow, because I have some language settings on roots which can't be mixed. Is there any settings which can help me?
Due to a bug in the core of Umbraco, it does not. Anything below the second leve, third level and lower is not being handled correctly. The XML is only being traversed one level up from the current page rather than all the way to the top as it should. This is a confirmed bug that apparently was fixed but no one will tell us if there is a patch or if we must upgrade to 4.6 or 4.7 to get the update.
From CodePlex: "The problem was caused by the code only checking ParentNode of the current node for a domain, which works fine at a depth of 1, but any lower and it broke. The patch simply walks up the tree looking for a domain. It also fixes a caching problem I encountered when nodes were cached from a different domain by using the current domain name and nodeId as the cache key instead of just the nodeId."
If I read this correctly, the problem only occurs when someone links to a different site within the multisite solution?
This is not a problem for my sites as I only let backend users log into one site at a time and they can only see the tree of the current site when selecting links.
By the way, the patches are attached to the issue, right above your comment. Is there any way you can upgrade to 4.7? That would be better than creating a custom build of Umbraco IMHO.
My multi-site solution is kinda like different languages, accept in our case, it's a public area and a members area that the public can also see. We want the member pages to only be accessible via the member domain name and vice versa. We are fearful of Google dinging us for duplicate content.
I would love to just jump to 4.7 but fear having to make any template, data type, etc. mods right before the site goes live. I plan to test an upgrade, hopefully later today. I haven't seen any upgrade horror stories yet, have you?
I've recently upgraded a site from 4.0 to 4.7 and it went fine. Just make sure to follow the instructions about the config changes in 4.7, that's very important.
Unique url for 3rd level domains
Hi, I have following setup in one umbraco:
www.example.com
- pages
- page1
sk.example.com
- directory
- skpage
but user is able to access url like this: www.example.com/directory/skpage which isn't what I want to allow, because I have some language settings on roots which can't be mixed. Is there any settings which can help me?
Thanks a lot.
Petr
You can set your useDomainPrefixes in the UmbracoSettings.config to true.
Thanks Sebastian,
I look at wiki but it looks like information about this settings isn't complete in wiki.
Petr
Sebastian, that does not address the issue with third level and lower.
@Connie it should, if you set domain names on the first level nodes to clearly seperate them from each other.
Due to a bug in the core of Umbraco, it does not. Anything below the second leve, third level and lower is not being handled correctly. The XML is only being traversed one level up from the current page rather than all the way to the top as it should. This is a confirmed bug that apparently was fixed but no one will tell us if there is a patch or if we must upgrade to 4.6 or 4.7 to get the update.
Weird, I am running a site in umbraco 4.0.4.2 and when I go to: "site1.com/panoramas/a/amuse" it gives me a nice content page
If I go to "anothersite.com/panoramas/a/amuse" it gives me a 404.
These are both sites in the same install.
Something springs to mind though, do you have a property umbracoRedirect on level 1? I believe this caused a problem like that. The solution would be to change it to umbracoInternalRedirectId instead see this blogpost for a more detailed way of setting up (multi)sites.
From CodePlex: "The problem was caused by the code only checking ParentNode of the current node for a domain, which works fine at a depth of 1, but any lower and it broke. The patch simply walks up the tree looking for a domain. It also fixes a caching problem I encountered when nodes were cached from a different domain by using the current domain name and nodeId as the cache key instead of just the nodeId."
http://umbraco.codeplex.com/workitem/25975
This is for NiceURL but it's all related.
If I read this correctly, the problem only occurs when someone links to a different site within the multisite solution?
This is not a problem for my sites as I only let backend users log into one site at a time and they can only see the tree of the current site when selecting links.
By the way, the patches are attached to the issue, right above your comment. Is there any way you can upgrade to 4.7? That would be better than creating a custom build of Umbraco IMHO.
My multi-site solution is kinda like different languages, accept in our case, it's a public area and a members area that the public can also see. We want the member pages to only be accessible via the member domain name and vice versa. We are fearful of Google dinging us for duplicate content.
I would love to just jump to 4.7 but fear having to make any template, data type, etc. mods right before the site goes live. I plan to test an upgrade, hopefully later today. I haven't seen any upgrade horror stories yet, have you?
I've recently upgraded a site from 4.0 to 4.7 and it went fine. Just make sure to follow the instructions about the config changes in 4.7, that's very important.
I also found a couple gotchas that are not in the upgrade documentation, otherwise my test upgrade went smoothly.
Cool, would be good to know what the gotchas are though!
is working on a reply...