umbraco v 4.0.2.1 (Assembly version: 1.0.3441.17657)
ASP 2.50727
IIS ver 6.0
Windows Server 2003 ver5.2.3.790
Stack trace (can be provided on request but see below)
After install and editing the webconfig. Our main navigation disappeared and we got a js error but not when testing within the company network using the company proxy gateway. From within the company we have to tunnle then RDC to get the IIS machine. When testing after install (using an internal company proxy) there was no issue it was only when we tested a normal machine connected to the internet did we see the error.
object required
if((version>=5.5)&&(document.body.filters))
in js.adx
The instructions say umbracoDebugMode, it needs to be false so we couldn’t get a stack trace when we turned it on the issue disappeared? Why does umbracoDebugMode=false have to be set for this package, if set to true what is the issue.
Sorry for the late response, I missed this post somehow.
The main reason that debug-mode needs to be false is to avoid problems. I've had some problems using compression with debugmode turned on. When turned on, there's quite a few extra bytes added to several .NET files. On live-sites, debug-mode should always be turned off. Hope this makes some sense to you?
Back to your problem. Certain js-files get messed up a bit when compressed if there are certain patterns for comments and stuff used. (compressing those, breaks the js, thus resulting in errors). I'd check the js-files for large chunks of comment and see how they are written. Best way for small lines of comments is by having them start with // (from the top of my head)
Reason because it might work internally and not externally is because of the proxy. I've had issues with compression myself when ISA-server was involved. Turns out that proxies and firewalls sometime block some browser information. If the proxy tells the webserver compression is not available in the browser, the webserver will send uncompressed files. (It may look like compression works, but in fact files are not compressed).
Ok fixed it there where actually 2 issues 1) The Print.css was being merged with the screen css and so we lost the navigation. There is a bug on codeplex about this: link media attribute not honoured 2) the js was a png transparency fix for ie (one of those commented out include scripts)
Adding these lines to the section ExcludedPaths of config\PeterDCompress.config fixed the issue
Update the js errors kept cascading so I excluded the whole scripts/ folder. But I guess I am now loosing most of the advantages for this tool. It looks likely that the error4s are all to do with the merging of the js files into 1 and we don’t have time or resources to test check everything (for something that works with no errors when this is disabled). It is possible to allow compression only and just not merge the ccs, js files? Alec
JS error after install
After install and editing the webconfig. Our main navigation disappeared and we got a js error but not when testing within the company network using the company proxy gateway. From within the company we have to tunnle then RDC to get the IIS machine. When testing after install (using an internal company proxy) there was no issue it was only when we tested a normal machine connected to the internet did we see the error.
The instructions say umbracoDebugMode, it needs to be false so we couldn’t get a stack trace when we turned it on the issue disappeared?
Why does umbracoDebugMode=false have to be set for this package, if set to true what is the issue.
aditional we use "Enable content expiration" as described here http://umbraco.org/blog/2007/12/14/dec-10-dramatic-performance-increase-in-two-minutes
Sorry for the late response, I missed this post somehow.
The main reason that debug-mode needs to be false is to avoid problems. I've had some problems using compression with debugmode turned on. When turned on, there's quite a few extra bytes added to several .NET files. On live-sites, debug-mode should always be turned off. Hope this makes some sense to you?
Back to your problem. Certain js-files get messed up a bit when compressed if there are certain patterns for comments and stuff used. (compressing those, breaks the js, thus resulting in errors). I'd check the js-files for large chunks of comment and see how they are written. Best way for small lines of comments is by having them start with // (from the top of my head)
Reason because it might work internally and not externally is because of the proxy. I've had issues with compression myself when ISA-server was involved. Turns out that proxies and firewalls sometime block some browser information. If the proxy tells the webserver compression is not available in the browser, the webserver will send uncompressed files. (It may look like compression works, but in fact files are not compressed).
Hope this helps you out a bit,
Peter
ok thanks for the response. btw it was the dev server just wondered why debug true would prevent the error. I will hunt around in the js.
Ok fixed it there where actually 2 issues
1) The Print.css was being merged with the screen css and so we lost the navigation. There is a bug on codeplex about this: link media attribute not honoured
2) the js was a png transparency fix for ie (one of those commented out include scripts)
Adding these lines to the section ExcludedPaths of config\PeterDCompress.config fixed the issue
<add path="scripts/pngTransparencyFix.js" />
<add path="css/print.css" />
<add path="umbraco/plugins/concierge/css/print.css" />
Update the js errors kept cascading so I excluded the whole scripts/ folder. But I guess I am now loosing most of the advantages for this tool. It looks likely that the error4s are all to do with the merging of the js files into 1 and we don’t have time or resources to test check everything (for something that works with no errors when this is disabled). It is possible to allow compression only and just not merge the ccs, js files?
Alec
is working on a reply...