Site requires iis restart before changes take effect
I have an Umbraco install containing 4 sites, 3 of which are separate Visual Studio projects using uSiteBuilder.
The last site I have added as part of one of the other sites, seems to require a site restart in iis before changes take effect.
I've tried unpublishing and republishing the Root node, and republished the entire site in case there was some caching issue but no change - the only thing that seems to work is restarting the site in iis
While this is "ok" for me while developing the sites, it's not going to be good for the client when the sites are handed over.
I had an issue with this before - are all the 4 sites set up as one site using the same app pool?
All 4 should be the same site in IIS and using host headers to bind the sites. The issue I had was that I had them set up in different app pools so when publishing, it oonly kicked the main Umbraco install.
Would be worth a shout but this site is part of one of the others.
A bit of background info - A client had an exisitng site developed a while back by another dev and they had a requirement for 3 new sites built within the same Umbraco installation.
I'm using uSiteBuilder(as usual) and created 2 separate uSiteBuilder projects for 2 of the sites and pointed them at the same Umbraco DB. These 2 work fine within IIS as separate sites and appPools.
When I was creating the 3rd site the same way, for some reason the userControls an document types were only available when logged in to that particular Umbraco. When logged in to any of the other sites' Umbraco, I could access all the documents and controls, but with this last site I had to log into it's specific Umbraco URL for any changes to take effect. I've asked the question in uSiteBuilder board to see if that's a known issue.
In the meantime, I just created this site as part of one of the other sites and it's running under the same appPool as the other site it's part of.
I just checked, and when I make a content change, the Umbraco.config file IS being updated, but I don't know why only a site restart updates the front end.
Hmm that is strange! If the Umbraco.config file is being updated then it sounds like a caching issue - although the part you mentioned about the doctypes and controls being unavailable sounds ominous. Something not quite right.
Sorry, I can't be more help - hopefully someone will have an answer; as always, i'm sure they will! ;)
Site requires iis restart before changes take effect
I have an Umbraco install containing 4 sites, 3 of which are separate Visual Studio projects using uSiteBuilder.
The last site I have added as part of one of the other sites, seems to require a site restart in iis before changes take effect.
I've tried unpublishing and republishing the Root node, and republished the entire site in case there was some caching issue but no change - the only thing that seems to work is restarting the site in iis
While this is "ok" for me while developing the sites, it's not going to be good for the client when the sites are handed over.
Anyone ever seen this before?
Hi Richard,
I had an issue with this before - are all the 4 sites set up as one site using the same app pool?
All 4 should be the same site in IIS and using host headers to bind the sites. The issue I had was that I had them set up in different app pools so when publishing, it oonly kicked the main Umbraco install.
Kenny
Hi Kenny
Would be worth a shout but this site is part of one of the others.
A bit of background info - A client had an exisitng site developed a while back by another dev and they had a requirement for 3 new sites built within the same Umbraco installation.
I'm using uSiteBuilder(as usual) and created 2 separate uSiteBuilder projects for 2 of the sites and pointed them at the same Umbraco DB. These 2 work fine within IIS as separate sites and appPools.
When I was creating the 3rd site the same way, for some reason the userControls an document types were only available when logged in to that particular Umbraco. When logged in to any of the other sites' Umbraco, I could access all the documents and controls, but with this last site I had to log into it's specific Umbraco URL for any changes to take effect. I've asked the question in uSiteBuilder board to see if that's a known issue.
In the meantime, I just created this site as part of one of the other sites and it's running under the same appPool as the other site it's part of.
I just checked, and when I make a content change, the Umbraco.config file IS being updated, but I don't know why only a site restart updates the front end.
Hmm that is strange! If the Umbraco.config file is being updated then it sounds like a caching issue - although the part you mentioned about the doctypes and controls being unavailable sounds ominous. Something not quite right.
Sorry, I can't be more help - hopefully someone will have an answer; as always, i'm sure they will! ;)
Kenny
Sorted!
I still have a separate IIS site set up so essentially 2 pointing to the same app
Cheers mate - your suggestion did lead to the answer :D
Great stuff - glad i could be of some help! :D
is working on a reply...