Domains for nodes that don’t vary by culture
Nodes based on content types that don’t allow vary by culture will by default use the default language in Umbraco when trying to resolve the domain (you can customize the logic needed). ExampleYour Umbraco installation has en-US as the default language. The node you are ingesting or one of its ancestors has the following setup for Culture and hostname.
| Domain | Culture |
|---|---|
| https://enterspeed.com/ | en-US |
| https://enterspeed.dk | da-DK |
Multiple domains per culture for the same site
For the moment Enterspeed can only handle one domain per culture in Culture and hostnames for each site node. If you have a multi-site Umbraco installation, with multiple sites nodes, you can have as many domains with the same culture as you want. This limitation is for scenarios where one site node has multiple domains with the same culture.Non-working Culture and Hostnames setup for the same site
This setup would not work as expected:| Domain | Culture |
|---|---|
| https://enterspeed.com/ | en-US |
| https://enterspeed.dk | en-US |
Working Culture and Hostnames setup
This setup would work as expected:| Domain | Culture |
|---|---|
| https://enterspeed.com/ | en-US |
| https://enterspeed.dk | da-DK |
Domains in Enterspeed
It is possible to add more domains in Enterspeed if you wish your content to be available on multiple domains.Changing Culture and hostnames
When you change a hostname in Culture and hostnames, you will manually have to re-seed the content into Enterspeed. This is currently a manual step, so please bare with us while we figure out the best way to automate this.Customize the culture logic
If you want to customize the culture logic, eg. if you use another culture then the default culture for a specific site or node that does not vary by culture you can implement your own version ofUmbracoCultureProvider either by implementing the IUmbracoCultureProvider interface or by extending the UmbracoCultureProvider class and override the methods you want to customize.