If I visit http://site-two.com/about I get the about page from site1... Oh now it's showing the correct page, perhaps caching issue, it seems to be correct now.
Am I doing something wrong or is umbraco doing something wrong?
Asside:
I am starting on a proof of concept with the following, does anyone have any experience with multi-domain muilit-language sites? where the domain does not map to the language?
Make sure that you have the flag in the Umbraco settings file set to true for useDomainPrefixes.
<useDomainPrefixes>true</useDomainPrefixes>
This ensures that when you are requesting pages it will only look for the page in the tree that is bound to the domain host header. Otherwise if it doesnt find it one but finds it in another you will get wierd things happening.
Thanks Pete, that sorted if for the simple scenario.
But with the more advanced scenario I still have a question, perhaps someone out there has an answer...
I've set the hostnames at the /asia/ level to be asia.example.com and I've set the hostname at the /asia/en/ level to be en.asia.example.com AND set useDomainPrefix = true this works ok, but it means URLS come out like so:
The only thing stopping me doing the latter is the dictionary language must be set along with a unique hostname. And since I have useDomainPrefixes=true then I must use the former url not the latter. Clear as mud?
Perhaps I could set the dictionary programatically???
personally, i'm suprised that they have the time to write content in english for every different country... most of the time a project like this starts with a lot of ambitions, and ends up with cutting half of the language variations simply because it's too much time to maintain ;)
As for convincing them /asia/en is a good solution -> people are more likely to enter a url starting with www.something than asia.something, for SEO purposes it's generally accepted that subfolders are nice, and subsites are a little bit more painful, technically you'll also have a better live as you'll get more transparant statistics in google analytics (it is one site afterall), and a lot les cookies to maintain (domain-bound)...
We're likely to have country specific domains in each country, the english is more likely to be tailored to reflect different content and activities in each country rather than different language, however each country may or may not have content in thier own language depending on the regional content managers.
So your assumption that it's 'one site after all' is I'm afraid misleading in this case. I'ts one application with the same functionality but that's about as 'same' as it gets :-) even the 2 languages within a country are unlikely to be direct translations of each other but tailored content to each audience.
Good point about the www.... tho, which is why I prefer www.example.co.uk and www.example.com.cn to differentiate country.
AND www.example.com.cn/en/ and www.example.com.cn/cn/ to differentiate language. which we CAN do, but we have to turn off useDomainPrefix, which has the issue of being able to access /cn/ folder from .co.uk (perhaps we can write some code to address that?)
Multilingual site shows incorrect content
Hi all
I have 2 sites where I have the following error, one is 4.0.3 the othr is 4.5.1
The site is setup like this:
if I visit http://site-two.com/ I get the correct page (yay)
If I visit http://site-two.com/about I get the about page from site1... Oh now it's showing the correct page, perhaps caching issue, it seems to be correct now.
If I visit http://site-two.com/shop I get the shop page from site1?
Am I doing something wrong or is umbraco doing something wrong?
Asside:
I am starting on a proof of concept with the following, does anyone have any experience with multi-domain muilit-language sites? where the domain does not map to the language?
Cheers.
Murray.
Hey Murray
Make sure that you have the flag in the Umbraco settings file set to true for useDomainPrefixes.
This ensures that when you are requesting pages it will only look for the page in the tree that is bound to the domain host header. Otherwise if it doesnt find it one but finds it in another you will get wierd things happening.
Hope that helps.
Peter
Thanks Pete, that sorted if for the simple scenario.
But with the more advanced scenario I still have a question, perhaps someone out there has an answer...
I've set the hostnames at the /asia/ level to be asia.example.com and I've set the hostname at the /asia/en/ level to be en.asia.example.com AND set useDomainPrefix = true this works ok, but it means URLS come out like so:
http://en.asia.example.com/
where I would like to use the following.
http://asia.example.com/en/
The only thing stopping me doing the latter is the dictionary language must be set along with a unique hostname. And since I have useDomainPrefixes=true then I must use the former url not the latter. Clear as mud?
Perhaps I could set the dictionary programatically???
I don't see an immediate solution for this, maybe opt for http://www.example.com/asia/en ?
Thanks Rik,
I missed the most obvious option, I'll put those options & thier pros 'n cons to the client and see what they want.
Chur.
personally, i'm suprised that they have the time to write content in english for every different country... most of the time a project like this starts with a lot of ambitions, and ends up with cutting half of the language variations simply because it's too much time to maintain ;)
As for convincing them /asia/en is a good solution -> people are more likely to enter a url starting with www.something than asia.something, for SEO purposes it's generally accepted that subfolders are nice, and subsites are a little bit more painful, technically you'll also have a better live as you'll get more transparant statistics in google analytics (it is one site afterall), and a lot les cookies to maintain (domain-bound)...
i could go on ;)
We're likely to have country specific domains in each country, the english is more likely to be tailored to reflect different content and activities in each country rather than different language, however each country may or may not have content in thier own language depending on the regional content managers.
So your assumption that it's 'one site after all' is I'm afraid misleading in this case. I'ts one application with the same functionality but that's about as 'same' as it gets :-) even the 2 languages within a country are unlikely to be direct translations of each other but tailored content to each audience.
Good point about the www.... tho, which is why I prefer www.example.co.uk and www.example.com.cn to differentiate country.
AND www.example.com.cn/en/ and www.example.com.cn/cn/ to differentiate language. which we CAN do, but we have to turn off useDomainPrefix, which has the issue of being able to access /cn/ folder from .co.uk (perhaps we can write some code to address that?)
is working on a reply...