– The wordpress server producing minify file is working fine.
– I think what’s happening is as we experiment with the CSS minify settings, many versions of default.include.css are put on the CDN servers – and one may not know which one of those will be used next, (unlike one version on wordpress server). I went to maxcdn dashboard and purged all files, and things seems to be OK now.
– My problem was that a new CDN .CSS would get generated and work for some time but after a while this .CSS file gets replaced with an older broken .css file as I switch – disable all caching functionality – on/off, or just after a while.
– Perhaps W3 Total Cache can detect changes in .css/.js and CDN enabled, then warn that – You may need to purged files (.css/.js) from CDN provider as well.
