Anyone got any ideas what could be wrong? The only thing the host has done is move from classic to integrated pipeline mode but can't think why it would cause a problem - i've not changed it back as the front end is working fine, it's just the CMS that is goosed?
Uh-oh, doesn't look pretty. My guess would be to do with file permissions for the /App_Data/ClientDependency directory.
But with you saying that your hosts switched from classic to integrated... you might be missing something in the Web.config, (not sure what that might though).
My first port of call would be opening it up in Firefox running Firebug.
I'd imagine its a permissions issue, so use the network section to determine what error the server is throwing for those files.
I don't suppose by any chance your host has upgraded the install for you? I've seen issues when the windows compression tool doesn't extract folders correctly and just misses files out.
I had this happen to me the other day, but can't remember what I did to fix it.
Have you tried deleting the client dependancy folder in the App_Data folder (i think)? It kinda looks like it's just the CSS that's a bit screwed. Maybe try accessing the CSS path directly and see what happens.
Yup deleted the client dep folder, same old. Recycled the app pool and nothing. The CSS is being pulled through no probs as there are no errors. Network tab in firebug tells me:
This has happened to me too, i'm can't remember 100% but I think I resolved it by clearing out /App_Data/TEMP/ClientDependency.
From what I remember it happened when I set up an initial Umbraco site using Cassini - as soon as I switched to using IIS on a proper domain I got what you're experiencing (as the backend was still trying to access resources on 'localhost').
tried recycling app pool after all the above. I've managed to reproduce it locally now in Windows 7 under IIS so can play with a few things to see what works - may try a fresh install into an integrated pool to see how it's setup
tried
recycling app pool after all the above. I've managed to reproduce it
locally now in Windows 7 under IIS so can play with a few things to see
what works - may try a fresh install into an integrated pool to see how
it's setup
Just installed a new version, set the app pool to v4 integrated and got the same thing. Changed it to v2 integrated and problem is fixed. However the original reason for doing it is for extensionless urls which now no longer work!
I thought Umbraco 4.5.2 would work in v4 integrated mode - obviously not, anyone got it working yet?
I upgraded a copy of 3.0.6 site first via 4.0.3 and then directly to 4.5.2 .net 3.5 using a backup of the original database. This on a shared host.
Everything went well, except I had to set config to xml legacy schema and republish the site.
So I backed up the original site, deleted all files and copied everything from the upgrade site. Pointing to the same (new) database.
While the front end works smoothly the backend is exactly as your screen capture. I don't get it. It's a complete copy of a site with no errors.
I guess I have to look into the app pool question, but if the upgrade site and the now halfway ruined original site runs exact same app pool setup - what can I do?? I'm no Umbraco wizard.
Sorry meant to reply to this earlier in the week and forgot! Nope I ran out of time so left as is for now i.e. a site with the .aspx extension present instead of SEO Friendly url's
I needed to revert the app pool back to version 2 to get it working, will not have it with version 4 which caused the problems
Suddenly it works! There was a crash on the server and when everything was copied back it looked the same in umbraco until I had set all permissions over again. Don't know what I did differently this time, after all Umbraco pronounced all settings perfect during the upgrade. But somehow something got the right permissions this time.
The problems started after I added some folder paths to umbracoReservedUrls in web.config. This is how it looks in my web.config (the last four entries are my custom folders - the ones that I want to exclude from umbracos URL rewriting):
I have tried lots of different ways to add these four folders to the web.config. Initially I added them to the key umbracoReservedPaths, but someone somewhere on the forum said it should be in umbracoReservedUrls.
Before I did this modification everything was working perfectly. Frontend worked like it should and the backend had its stylesheet and so on. After this modification the frontend still works like it should but the backend looks just like the screenshot posted in the first message in this thread.
I solved the problem but I'm not 100% sure what was wrong.
My solution was to download a fresh copy of Umbraco and get an untouched copy of the web.config file. Then I copied everything in the <appSettings> tag from the old web.config to the fresh copy. Then I uploaded the new web.config to the server and after that it worked like a charm. I think what happened was that when using the ISP's settings control panel, it changed some settings in the web.config as well which "broke" Umbraco.
As soon as I get my code compare tool working properly I will take a look at the old and the new web.config to see what's different and what could be causing this error.
Umbraco CMS is screwed - lost all styling
Came to setup a site today and got the following
Anyone got any ideas what could be wrong? The only thing the host has done is move from classic to integrated pipeline mode but can't think why it would cause a problem - i've not changed it back as the front end is working fine, it's just the CMS that is goosed?
Ideas?
Simon
Hi Simon,
Uh-oh, doesn't look pretty. My guess would be to do with file permissions for the /App_Data/ClientDependency directory.
But with you saying that your hosts switched from classic to integrated... you might be missing something in the Web.config, (not sure what that might though).
Cheers, Lee.
My first port of call would be opening it up in Firefox running Firebug.
I'd imagine its a permissions issue, so use the network section to determine what error the server is throwing for those files.
I don't suppose by any chance your host has upgraded the install for you? I've seen issues when the windows compression tool doesn't extract folders correctly and just misses files out.
Well for now i've got it working but had to revert to classic mode - I suspect the web.config file has been screwed in the changeover (see http://our.umbraco.org/forum/core/general/14106-Client-Dependency-woes-refresh-cache).
I'll have a look over the weekend, get it working locally in integrated pipeline mode and then upload the config file and try again
Cheers all
Si
Hey Simon,
I had this happen to me the other day, but can't remember what I did to fix it.
Have you tried deleting the client dependancy folder in the App_Data folder (i think)? It kinda looks like it's just the CSS that's a bit screwed. Maybe try accessing the CSS path directly and see what happens.
Cheers
Matt
Cheers Matt,
Yup deleted the client dep folder, same old. Recycled the app pool and nothing. The CSS is being pulled through no probs as there are no errors. Network tab in firebug tells me:
http://telcoop.local/umbraco/DependencyHandler.axd?s=L3VtYnJhY29fY2xpZW50L3BhbmVsL3N0eWxlLmNzczsvdW1icmFjb19jbGllbnQvc2Nyb2xsaW5nbWVudS9zdHlsZS5jc3M7L3VtYnJhY29fY2xpZW50L3VpL2RlZmF1bHQuY3NzOw%3d%3d&t=Css&cdv=1 404 not found - obviously linked to the client dependancy issue people have told me about but clueless how to sort it.
Front end is fine and dandy
Coupld of things to check:
1) Have you got the .axd handler registered in your web.config?
2) Have you set the .axd extension NOT to check file exists? (in IIS)
This soooo rings a bell, I just can't remember what I did =)
Matt
You could also try incrementing the version number in the client dependency config file.
Matt
This has happened to me too, i'm can't remember 100% but I think I resolved it by clearing out /App_Data/TEMP/ClientDependency.
From what I remember it happened when I set up an initial Umbraco site using Cassini - as soon as I switched to using IIS on a proper domain I got what you're experiencing (as the backend was still trying to access resources on 'localhost').
Incremented the version, no difference
Tried removing the contents of temp same
tried recycling app pool after all the above. I've managed to reproduce it locally now in Windows 7 under IIS so can play with a few things to see what works - may try a fresh install into an integrated pool to see how it's setup
The permissions are all fine?
Incremented the version, no difference
Tried removing the contents of temp same
tried recycling app pool after all the above. I've managed to reproduce it locally now in Windows 7 under IIS so can play with a few things to see what works - may try a fresh install into an integrated pool to see how it's setup
Just installed a new version, set the app pool to v4 integrated and got the same thing. Changed it to v2 integrated and problem is fixed. However the original reason for doing it is for extensionless urls which now no longer work!
I thought Umbraco 4.5.2 would work in v4 integrated mode - obviously not, anyone got it working yet?
Si
Duplicate post
Hi Simon,
I've been running all my 4.5.2 sites in .net v4 integrated, both locally and on the live server, no problems here.
Rich
Let me know if there's anything I can check here that'll help you?
Rich
Thanks Rich - could you send me a copy of your web.config as that seems to be the source of the problems I reckon.
Sure, it's just the default 4.5.2 one. Rich
Still no closer to sorting this one - very frustrating
Hi Simon, sorted it out now?
I upgraded a copy of 3.0.6 site first via 4.0.3 and then directly to 4.5.2 .net 3.5 using a backup of the original database. This on a shared host.
Everything went well, except I had to set config to xml legacy schema and republish the site.
So I backed up the original site, deleted all files and copied everything from the upgrade site. Pointing to the same (new) database.
While the front end works smoothly the backend is exactly as your screen capture. I don't get it. It's a complete copy of a site with no errors.
I guess I have to look into the app pool question, but if the upgrade site and the now halfway ruined original site runs exact same app pool setup - what can I do?? I'm no Umbraco wizard.
Hi,
Sorry meant to reply to this earlier in the week and forgot! Nope I ran out of time so left as is for now i.e. a site with the .aspx extension present instead of SEO Friendly url's
I needed to revert the app pool back to version 2 to get it working, will not have it with version 4 which caused the problems
Simon
Suddenly it works! There was a crash on the server and when everything was copied back it looked the same in umbraco until I had set all permissions over again. Don't know what I did differently this time, after all Umbraco pronounced all settings perfect during the upgrade. But somehow something got the right permissions this time.
I'm experiencing this problem as well!
The problems started after I added some folder paths to umbracoReservedUrls in web.config. This is how it looks in my web.config (the last four entries are my custom folders - the ones that I want to exclude from umbracos URL rewriting):
I have tried lots of different ways to add these four folders to the web.config. Initially I added them to the key umbracoReservedPaths, but someone somewhere on the forum said it should be in umbracoReservedUrls.
Before I did this modification everything was working perfectly. Frontend worked like it should and the backend had its stylesheet and so on. After this modification the frontend still works like it should but the backend looks just like the screenshot posted in the first message in this thread.
Please help me sort out this problem!
/Thomas
I solved the problem but I'm not 100% sure what was wrong.
My solution was to download a fresh copy of Umbraco and get an untouched copy of the web.config file. Then I copied everything in the <appSettings> tag from the old web.config to the fresh copy. Then I uploaded the new web.config to the server and after that it worked like a charm. I think what happened was that when using the ISP's settings control panel, it changed some settings in the web.config as well which "broke" Umbraco.
As soon as I get my code compare tool working properly I will take a look at the old and the new web.config to see what's different and what could be causing this error.
is working on a reply...