but these files both return a file not found error..... any idea what I could be doing wrong? I have umbraco debug mode set to false, scriptResourceHandler compression is set to false as you specified in the install notes.
I was expecting some of my stylesheets not to work as I use the @import method from within my main stylesheet.... but wasn't expecting the above.... any ideas?
yes, sorry my bad.... I forgot these two lines <remove verb="*" path="js.axd,css.axd"/> <add verb="*" path="js.axd,css.axd" type="PeterD.Compress.CompressionHandler,PeterD.Compress"/>
yeah, I notice when I run in integrated mode, that the compression no longer works..... any way around this?
Yes, integrated mode should work, you need to alter the web.config a bit. Not sure what exactly from the top of my head, have to look it up tonight when I get home.
Hi Peter, I finally got the chance to try the above and am happy to say that it works. I also took out my @import css rules and linked them in from my main template so that they all get slapped together in the one file.
I only have one problem now..... after the javascript has been compressed.... it doesn't seem to work anymore. Are there any easy gotcha's to look out for?
Great package by the way, you can see what a huge difference it makes when comparing compressed and non compressed via ySlow.
Figured it out..... needed to add my conditional ie7.js to the exclusion list.... and had to change the order of this around a bit for example even after you have added ie7.js to be excluded, if you have your conditional script first:
linked js files and css files are throwing a 404 error
Hi Peter,
when I enable compression in the web config It seems to do it's thing
but these files both return a file not found error..... any idea what I could be doing wrong?
I have umbraco debug mode set to false, scriptResourceHandler compression is set to false as you specified in the install notes.
I was expecting some of my stylesheets not to work as I use the @import method from within my main stylesheet.... but wasn't expecting the above.... any ideas?
A couple of things to check I guess:
- Is axd mapped to .NET in IIS?
- Did you add the lines to the web.config? (httpHandler-section)
If both above are true, are you using the .NET 3.5 web.config by any chance?
Peter
yes, sorry my bad....
I forgot these two lines
<remove verb="*" path="js.axd,css.axd"/>
<add verb="*" path="js.axd,css.axd" type="PeterD.Compress.CompressionHandler,PeterD.Compress"/>
yeah, I notice when I run in integrated mode, that the compression no longer works..... any way around this?
Glad it was that easy ;)
Yes, integrated mode should work, you need to alter the web.config a bit. Not sure what exactly from the top of my head, have to look it up tonight when I get home.
ok Great.... please add the integrated settings to the documentation if possible for us lesser mortal beings :)
For integrated mode, use this (do not alter the system.web part, or if you did, undo that)
In the system.webserver-part, add this:
in modules:
in handlers:
After that, it should work in integrated mode as well.
HTH,
Peter
Hi Peter, I finally got the chance to try the above and am happy to say that it works.
I also took out my @import css rules and linked them in from my main template so that they all get slapped together in the one file.
I only have one problem now..... after the javascript has been compressed.... it doesn't seem to work anymore. Are there any easy gotcha's to look out for?
Great package by the way, you can see what a huge difference it makes when comparing compressed and non compressed via ySlow.
- Tim
Figured it out..... needed to add my conditional ie7.js to the exclusion list.... and had to change the order of this around a bit
for example even after you have added ie7.js to be excluded, if you have your conditional script first:
<!--[if IE 6]>
<script src="/scripts/js/IE7.js" type="text/javascript"></script>
<![endif]-->
the compression script seems to latch onto the first script it finds, resulting in:
(even though now IE.js is now referenced seperately as well.... I guess the script see's the first js file as a hook, or place to start)
hope this helps others who have the same problem.
- Tim
is working on a reply...