Just saw your presentation at CG12 and installed and tested the package. It's seems that the Minify output is not cached in the browser. I get a 200 OK everytime I refresh the site. On the static css and js files I get 304 Not Modified and they are not downloaded again. Am I missing something
I experienced the same thing. I also installed the package after seeing the CG12 presentation. It seems to always give a 200 OK instead of a 304 Not Modified after the first request.
Also it seems to break some css in my website, but I believe that's more of a general issue when you use a combine/compress tool like this. I'll have to investigate that one.
//offtopic @Pete any thoughts on conditional css files?
Thanks for raising this. Caching "should" be in there and working, I'll have to take a look for you, I'll post here if/when I find a problem and fix it.
Can I ask which browser you where using?
@Roel, assuming you mean IE conditional css? These can still be compressed using the same method, as long as you wrap them in the right IE comments they will only be pulled in when required. Becareful if you are doing some really quirky IE hacks (which you shouldn't as thats the point of IE conditionals in the first place!). If the files are tiny (less than a 1K or so) it might be worth leaving them as it for ease rather than compressing.
If you have files which have to be install in a specific order (rare these days for us) you can either split them into two calls/tags or name them alphabetically. Remember you don't need everything in on big combined file, its ok to have a few separate calls to the server. We are just trying to get away from having 18 css and js files per page! :)
Hope that helps. I'll get back to you about the caching later this week.
I've tried Chrome anf FF - sam result. I seems that the "last modified" date is not set, which may be why
Regarding the order of loading you mention - is the files not loaded in the order by which they are writting in the path? This should load in the order base.css, skeleton.css, layout.css
@ Bo yeah that version will work as you think it will. I covered the folder method of including assets in my presentation so was thinking about that way of doing it sorry.
@ All, found the issue, the cache goodies while commented out for testing it seems. Put it back in and just running some sanity checking but should have a release today.
@Bo I am using the folder method, so I need to take the order into account. Simply renaming the assets does the trick, ie. 1.screen.css, 2.another.css etc
@Pete Great! I will check later on for the new release. Concerning the conditional IE stylesheets, I will put them in a diffent folder and use the 'file compression' instead of the 'folder compression' to make it work. Thanks
Awesome. The caching works now. The only problem is that it seems to trash some of my CSS when it compresses. I'm not entirely sure what to see in the output but it seems to me, that some CSS commands has been renamed - and that can't be true? Or what?
No browser caching?
Hi Pete
Just saw your presentation at CG12 and installed and tested the package. It's seems that the Minify output is not cached in the browser. I get a 200 OK everytime I refresh the site. On the static css and js files I get 304 Not Modified and they are not downloaded again. Am I missing something
/Bo
I experienced the same thing. I also installed the package after seeing the CG12 presentation. It seems to always give a 200 OK instead of a 304 Not Modified after the first request.
Also it seems to break some css in my website, but I believe that's more of a general issue when you use a combine/compress tool like this. I'll have to investigate that one.
//offtopic @Pete any thoughts on conditional css files?
Hi guys,
Thanks for raising this. Caching "should" be in there and working, I'll have to take a look for you, I'll post here if/when I find a problem and fix it.
Can I ask which browser you where using?
@Roel, assuming you mean IE conditional css? These can still be compressed using the same method, as long as you wrap them in the right IE comments they will only be pulled in when required. Becareful if you are doing some really quirky IE hacks (which you shouldn't as thats the point of IE conditionals in the first place!). If the files are tiny (less than a 1K or so) it might be worth leaving them as it for ease rather than compressing.
If you have files which have to be install in a specific order (rare these days for us) you can either split them into two calls/tags or name them alphabetically. Remember you don't need everything in on big combined file, its ok to have a few separate calls to the server. We are just trying to get away from having 18 css and js files per page! :)
Hope that helps. I'll get back to you about the caching later this week.
Cheers
Pete
Hi Pete
I've tried Chrome anf FF - sam result. I seems that the "last modified" date is not set, which may be why
Regarding the order of loading you mention - is the files not loaded in the order by which they are writting in the path?
This should load in the order base.css, skeleton.css, layout.css
Is that not the case? I think it's crucial that you control the order
Cheers Bo
@ Bo yeah that version will work as you think it will. I covered the folder method of including assets in my presentation so was thinking about that way of doing it sorry.
@ All, found the issue, the cache goodies while commented out for testing it seems. Put it back in and just running some sanity checking but should have a release today.
@Pete
Ahh. Sorry misread that :o)
Looking forward to the updated package - so much easier to use than CD
/Bo
Hi guys,
The flood of work emailed and "stuff" after having a week away keeps stopping me getting this one out asap.
I'm on it but please bare with me, I'll let you know when we have a new release on here, should be soon I hope.
Cheers
Pete
Hi Peter
Any progress on the update :)
/Bo
Hi guys,
Sorry for the delay, 101 things on at the minute!
Can you try the new 0.3 version and let me know how you get on. Works here but its been a while since I've packaged anything up ;)
Cheers
Pete
Hi Peter
Awesome. The caching works now. The only problem is that it seems to trash some of my CSS when it compresses. I'm not entirely sure what to see in the output but it seems to me, that some CSS commands has been renamed - and that can't be true? Or what?
Look at this towards the end. This doesn't make sence: http://www.flex-it.dk/Minify?f=/css/style.css
/Bo
Weird, I can't recreate this locally. Also it happens when running the file in debug mode too:
http://www.flex-it.dk/Minify?f=/css/style.css&debug=true
Whats the encoding of the file?
is working on a reply...