Issue with moving 4.0.4.3 site to production environment
We moved an Umbraco website from our staging environemnt (IIS 6 & SQL 2008, .net 4 & intgrated pipeline mode)
to our production server (IIS 7, SQL 2008, .net 4 & intgrated pipeline mode)
Now we have the issue of the blank trees in the backend of the website...
I already upgraded the site from 4.0.1 to 4.0.3 but this didn't fix the issue. Checked permissions on the web folder and windows temp folder.
does anyone see some issues with this web.config that might be causing this? I've searched the bowels of this forum and still haven't come up with a solution...
There are no requests giving errors. The GetTree.aspx (or however it is called) just returns an empty <tree></tree>...
Note: The web.config was manually adjusted to support .NET 4.0 because of User Controls.
Note 2: The upgrade to .NET 4.0 was done before doing a whole bunch of other things on the installation in the staging environment, and everything worked perfectly.
There must be an incompability with IIS 7 that we are missing.
Issue with moving 4.0.4.3 site to production environment
We moved an Umbraco website from our staging environemnt (IIS 6 & SQL 2008, .net 4 & intgrated pipeline mode)
to our production server (IIS 7, SQL 2008, .net 4 & intgrated pipeline mode)
Now we have the issue of the blank trees in the backend of the website...
I already upgraded the site from 4.0.1 to 4.0.3 but this didn't fix the issue. Checked permissions on the web folder and windows temp folder.
does anyone see some issues with this web.config that might be causing this? I've searched the bowels of this forum and still haven't come up with a solution...
Any other help is also greatly appreciated!
Kind regards,
Rik
Hi Rik,
Have you tried using Firebug or Fiddler to track down any requests that are giving an error ?
There are no requests giving errors. The GetTree.aspx (or however it is called) just returns an empty <tree></tree>...
Note: The web.config was manually adjusted to support .NET 4.0 because of User Controls.
Note 2: The upgrade to .NET 4.0 was done before doing a whole bunch of other things on the installation in the staging environment, and everything worked perfectly.
There must be an incompability with IIS 7 that we are missing.
free bottle of beer for whoever points us towards a solution:
Comment author was deleted
@Rik, did you zip the site files? and extracted them on the new server with the default windows archiver?
Also could you check if the apptree table looks the same on both version of the site
Upgraded to 4.5.2 to resolve the issue... to many bugs in the older versions... (DFS issues)
is working on a reply...