I am just creating this topic as a pointer to anyone who may experience this issue.
In deploying a .Net 4 based Umbraco 4.7.2 site we experienced a problem with the tree not displaying content. This deployment was to an off site IIS 7.5 on 64bit Windows Server 2008R2, which we have not administered much before.
Having trawled many blog entries, installation instructions and the general dregs of the internetz we tried many, many solutions and found nothing to indicate the final problem, hence this posting. Our host had set a 'Maximum query string' length to 25 at the top level of IIS. I had not even realised this setting existed or considered the consequences - what happens is that the ScriptResource.axd and WebResource.axd references (which include a 216 byte query string) fail with a 402, so no AJAX / JS features within will operate (The JS error is 'Sys is undefined').
You can override this in a local web.config setting within system.webServer:
Another tree not refeshing problem - solved
I am just creating this topic as a pointer to anyone who may experience this issue.
In deploying a .Net 4 based Umbraco 4.7.2 site we experienced a problem with the tree not displaying content. This deployment was to an off site IIS 7.5 on 64bit Windows Server 2008R2, which we have not administered much before.
Having trawled many blog entries, installation instructions and the general dregs of the internetz we tried many, many solutions and found nothing to indicate the final problem, hence this posting. Our host had set a 'Maximum query string' length to 25 at the top level of IIS. I had not even realised this setting existed or considered the consequences - what happens is that the ScriptResource.axd and WebResource.axd references (which include a 216 byte query string) fail with a 402, so no AJAX / JS features within will operate (The JS error is 'Sys is undefined').
You can override this in a local web.config setting within system.webServer:
<security>
<requestFiltering>
<requestLimits maxUrl="1234" maxQueryString="1234">
...
I hope this might help anyone who encounters this gotcha.
is working on a reply...