wp-content/plugins/contact-form-7/styles.css?ver=2.1
You need to use the full URL when CSS or JS files have ?ver=2.1 for example. Also some files cannot be minified so if you have an issue you need to test one-by-one or check the wp-content/w3tc/log/minify.log if there are still errors.
Thread Starter
nubic
(@nubic)
i reed the faq and do this
and test one by one
check with [verify URI] and i see files added
wp-content/w3tc/log/minify.log is not created. i create them myself and chmod 666 then his wrote
[/wp-content/w3tc/min/default.include.css] The path “/var/www/account/data/www/site.com/wp-content/plugins/contact-form-7/styles.css?ver=2.1” could not be found (or was not a file)
and another i wrote full url and save settings but when open minify settngs i see short in CSS and JS file management
If minify cannot find the file, it cannot build the cache. Are you sure that file exists on your server?
Thread Starter
nubic
(@nubic)
i experiment whith php.ini and dont know what am i don š
files whithout strings wariables are cashe now,
but with wariables are not and adding full url is not helpfull and file’s 100% exist
Thread Starter
nubic
(@nubic)
i wrote full url in w3-total-cache-config.php and it works, dont work only if adding url from admin panel because its automaticly shorts by plagin i think, but i dont know why
and when i add another url and save settings his again short all urls and agains we hav eror 400 bad reqest instead default.include.css file
This is not a known bug, would you mind trying a re-install so that all we can be sure that something else isn’t going wrong?
Thread Starter
nubic
(@nubic)
after reinstall everything works thanks
but i have some any questions
1 i want to translate plugin but i cant see any support internationalization like e_() in WP, can you in next releases include support translations with .po .mo files
2 i don some tests and minifyed files are not cash and gzip
like
file size min size(gzip) cache (s)
/ (html) 12511 12434 1070
default.include.css 13994 2543 0
show_ads.js adsense 11143 - 86400
default.include.js 71086 23143 -
headers
HTTP/1.1 200 OK
Server: nginx/0.7.64
Date: Mon, 18 Jan 2010 12:13:11 GMT
Content-Type: application/x-javascript
Content-Length: 71086
Last-Modified: Mon, 18 Jan 2010 11:29:59 GMT
Connection: keep-alive
Accept-Ranges: bytes
Up to 47891 bytes could have been saved through compression.
minifyed files are not cash and gzip
Do you mean that the files are not created on your server?
i cant see any support internationalization
Please email me through the bug submission form on the support tab so we can speak further.
Thread Starter
nubic
(@nubic)
files created but headers without
Content-Encoding: gzip
Cache-Control: public, max-age=86400
or its normal
or may be users dont get compressed default.include.css.gz file only default.include.css
becose tests show size css 13994 kb but gziped file has size 2543 kb
Thread Starter
nubic
(@nubic)
Server: nginx/0.7.64
Date: Mon, 25 Jan 2010 20:31:34 GMT
Content-Type: text/css
Content-Length: 13994
Last-Modified: Mon, 25 Jan 2010 11:16:04 GMT
Connection: close
Accept-Ranges: bytes
Content (13.67 KiB)
Server: nginx/0.7.64
Date: Mon, 25 Jan 2010 20:34:25 GMT
Content-Type: application/x-javascript
Content-Length: 71086
Last-Modified: Mon, 25 Jan 2010 11:16:10 GMT
Connection: close
Accept-Ranges: bytes
and main html
Server: nginx/0.7.64
Date: Mon, 25 Jan 2010 20:35:07 GMT
Content-Type: text/html; charset=UTF-8
Transfer-Encoding: chunked
Connection: close
X-Powered-By: W3 Total Cache/0.8.5.1
Pragma: public
Expires: Mon, 25 Jan 2010 21:28:23 GMT
Last-Modified: Mon, 25 Jan 2010 20:28:23 GMT
Cache-Control: max-age=3196, public, must-revalidate
Vary: Accept-Encoding,Cookie
Etag: e03bebe7b1b53a899b2fef04dacac954
Content-Encoding: gzip
Content (encoded: 12.50 KiB / decoded: 55.13 KiB)
Sorry for not catching this earlier, but nginx is not yet supported.
Hope that there are plans for nginx support in the near future.
I am using it for a week after migrating from apache and I am impressed. The only thing that I miss is good caching plugin. Wp-Supercache is not good to me.
Nginx definitely has it’s strengths. Lighttpd and nginx are in the roadmap scheduled after finalization of other key features. If anyone blogs about the changes they’ve made (users are implementing it themselves I hear) I’ll make sure to share them.
I’ve searched a lot today and still nothing.
If someone have managed to implement the plugin with nginx, it would be great to share how he had done it.
