Hi Stephen,

Thanks a lot for your input :-)

Yes, bottom line is that they want mysite.*/news (any mysite.xx can be used, they have a lot of domains) to list the global news from the News folder within the sites content. So if I enter the site with i.e.: mysite.se, the news page should display global news items, but I should also be able to click on a link to the swedish, local news page from there.

The problem is that when I enter the site with mysite.se and clicks on the News link in the menu, the domain changes to mysite.com which doesn't show any link (because the domain is .com)

So basically, the entire site should be browsable by mysite.XX and if I enter the site with mysite.se, a link will appear on the global news section to the swedish local news page.

If I understand it correctly, all I need is to set up mysite.se (and all other mysite.XX) in the manage hostnames on my site node in Umbraco and then I should be good to go with the navigation not changing to .com? :-)

Thanks again! Sorry if this is confusing.

All the best,

Bo

Btw, the version of Umbraco is 4.11.1 :-)

@bo: in theory, yes, you would setup all your mysite.xx (porn?) domains on the root node, then ensure that useDomainPrefixes is false, and you should get relative urls within the sites => the menu urls will be "/about-us", not "mysite.com/about-us".

Let me know how it works!

Hi Stephen,

If only it were porn :-D

I just tried to set it up like that on my localhost and it seems to work! The useDomainPrefixes setting were false by default. Only thing I find a bit dirty (no, it's still not porn..) is how to find the correct local news page to display.

The way I do it now is like this:

On every country-node (i.e. Denmark) I have a textstring field where the administrator can enter the domain extension that should be used to find the link. I.e. if he enters .dk the macro on news overview will parse the current domain and finde that folder. Code for parsing looks like this:

public static Node GetLocalNewsPageLink()
        {
            try
            {
                // Get a reference to the current request
                var request = HttpContext.Current.Request;

                // Get the current domain extension
                string domainExt = request.Url.Host.Substring(request.Url.Host.LastIndexOf('.'));

                // Get a reference to the local news page where the domain extension matches
                var localNewsPage =
                    uQuery.GetNodesByType("LocalNewsPage").FirstOrDefault(x => !string.IsNullOrEmpty(x.GetProperty("domainExtension").Value) && x.GetProperty("domainExtension").Value.Equals(domainExt));

                // Return the url for the local news page if the variable is not null
                return localNewsPage ?? null;
            }
            catch (Exception)
            {
                return null;
            }
        }

I'm wondering if there would be a more clean way to do this? Would certainly be a more clean solution to check on the hostname set in Umbraco, but since all hostnames are set on the site node, this is not an option.

Thanks again! :-)

Ok, no porn then ;-)

As you rightfully point out, you cannot register a domain on the local news node. So you have to create an extra property on those nodes to store the ".dk" extension which will allow you to decide which one to display, if any.

There is another solution but I can't tell if it will work in 4.11.1. It should in 4.11.4/5 but... OK. You will have to test. Starting with 4.11.? you can register "wildcard" domains on a node, that just change the culture for that node and down under. To create a wildcard domain, you just create a normal domain but set the domain name to "*" (a star).

So you could create wildcard domains on each local news node. To figure out if a node should be displayed, look at the domains defined on the node, check if one is a wildcard domain, check if the culture of that domain matches the current culture.

Nice, but a bit experimental. I know for sure how to do it in 6.x but dunno it's going to be simple in 4.x -- maybe you'll want to stick with your proved solution.

Actually, the wildcard did work in Umbraco ver. 4.11.1 :-) Didn't know you could simply put a * there, awesome!

I like the solution, it's better than having a textstring field for storing the domain extension. However, I'm not sure I want the administrators to mess around with setting up hostnames - it seems a bit more low-tech to simply enter .se in a textfield ;-)

I'll see what solution I'll go with.

Thanks a lot for your help Stephen! Hero of the day :-D

The wildcard stuff is one step in the path to separate hostnames and cultures. Brand new ;-)

Glad it works.

is working on a reply...