I have a (customer) website, whitch should respond to several domains - same content no matter which domain is used.
My problem is that if I make changes to the content using domain1.com/umbraco/login.aspx the content on domain2.com/page.aspx isn't updated according to the changes. Result: domain1.com/page.aspx does not have the same content as domain2.com/page.aspx
The only way I can make the two domains show the same content again is to login to domain2.com/umbraco/login.aspx and re-publish all content. But it's not very customer-friendly....
It's a website hosted in a shared environment. It seems that all associated domains needs to have their own app. pool to work properly. A technician set it up and I tested it - worked nicely.
Thanks Chris....
Best regards, Jonas
PS. Wonder why nobody has had this problem before....?
Actually it _should_ be the other way around. All domains should be attached to the same IIS site, and use the same app pool.
I have seen sites with the opposite setup, and that causes each app pool to have it's own version of the cache, thus not getting updated when the other app pools perform actions on the content.
Multible domains - one website
I have a (customer) website, whitch should respond to several domains - same content no matter which domain is used.
My problem is that if I make changes to the content using domain1.com/umbraco/login.aspx the content on domain2.com/page.aspx isn't updated according to the changes. Result: domain1.com/page.aspx does not have the same content as domain2.com/page.aspx
The only way I can make the two domains show the same content again is to login to domain2.com/umbraco/login.aspx and re-publish all content. But it's not very customer-friendly....
Hope some of you guys can help :)
Hi Jonas,
How do you have IIS setup? Are all your sites running within the same IIS root folder?
It sounds like cache file is not updating for your other domains.
Best regards,
Chris
Hi Chris,
Good point!
It's a website hosted in a shared environment. It seems that all associated domains needs to have their own app. pool to work properly. A technician set it up and I tested it - worked nicely.
Thanks Chris....
Best regards,
Jonas
PS. Wonder why nobody has had this problem before....?
Actually it _should_ be the other way around. All domains should be attached to the same IIS site, and use the same app pool.
I have seen sites with the opposite setup, and that causes each app pool to have it's own version of the cache, thus not getting updated when the other app pools perform actions on the content.
is working on a reply...