I don’t know if this applies, but see my post about automatic minifying errors:
http://wordpress.org/support/topic/plugin-w3-total-cache-important-parsing-found-with-automatic-minify
(btw, I meant to say *Important* parsing error found with automatic minify)
In the minifying process, incorrect .js code was generated. You’ll see what I mean in my post. Good luck!
Thanks scott, but i don’t think your parsing problem is related to mine. I’m referring to the now aging problem where W3TC refuses to add the “gzip” extension to minified js and css files. For example W3TC outputs a file named “styles.css.” (note the . at the end) instead of “styles.css.gzip”. Since certain browsers (notably IE) can’t read these compressed files without the “gzip” extension at the end, websites are unstyled and without javascript functionality.
For some reason this problem does not affect all users so YMMV but it has been around since about 9.1.X. I have a feeling this is a server related issue (different versions of PHP, module access, etc). Here’s a short history:
http://wordpress.org/support/topic/css-is-broken-with-latest-w3tc?replies=18
http://wordpress.org/support/topic/plugin-w3-total-cache-0921-still-bad-ftp-details?replies=48
http://wordpress.org/support/topic/minify-still-broken-with-0922-update?replies=4
http://wordpress.org/support/topic/css-and-js-minify-not-working?replies=8
http://wordpress.org/support/topic/upgrade-w3-total-cache-to-0922-fix-minify-problem?replies=10
http://wordpress.org/support/topic/plugin-w3-total-cache-minify-gzip-still-a-problem-with-0923-update?replies=2
Hack fix: http://kenntwas.de/2011/tips/tools-allgemein/english-version-wordpress-get-w3tc-0-9-2-1-running-with-minify-and-gzip-compression/
Can you submit a bug submission form from the support tab of the plugin?
