Thread Starter
diegpl
(@diegpl)
Thats the error warning which appears to me, although debug message enabled for page cache showing up on the source code says its alright:
W3 Total Cache error: It appears Page Cache URL rewriting is not working. Please verify that the server configuration allows .htaccess
Unfortunately disk enhanced page caching will not function without custom rewrite rules. Please ask your server administrator for assistance. Also refer to the install page for the rules for your server.
Thread Starter
diegpl
(@diegpl)
Maybe thats because I forgot to look this one:
home/xxxx/public_html/wp-content/cache/page_enhanced/xxxx/.htacces
As soon I check it up I ll let u know. Or do you think it could be something else? Thank you!
Thread Starter
diegpl
(@diegpl)
I have taken a look into the warned folder and it is alright comparing to the install instructions. But on the general settings page the warning is still showing up. Is it a bug or not? Thank you a lot and congrats for the amazing plugin!!! 😉
Thread Starter
diegpl
(@diegpl)
Thats the technical info which appears on general settings page:
.htaccess file contains rules to rewrite url http://xxxxx/w3tc_rewrite_test into http://xxxx/?w3tc_rewrite_test which, if handled by plugin, return “OK” message.
The plugin made a request to http://exxxxxx/w3tc_rewrite_test but received:
cURL error 28: Operation timed out after 2001 milliseconds with 0 bytes received
instead of “OK” response.
Thank you!
Try to open this page:
http://xxxxx/w3tc_rewrite_test
when W3tc try it, the page is returned after 2 seconds:
> cURL error 28: Operation timed out after 2001 milliseconds
Maybe, is your webserver too slow? Try yourself…
Thread Starter
diegpl
(@diegpl)
I did that. it returned a 404 error page. While logged I got this warn:
<!– Performance optimized by W3 Total Cache. Learn more: https://www.w3-edge.com/products/
Object Caching 8069/8218 objects using disk
Page Caching using disk: enhanced (User is logged in)
Page cache debug info:
Engine: disk: enhanced
Cache key:
Reject reason: User is logged in
Creation Time: 1487257699.000s
Header info:
Content-Type: text/html; charset=UTF-8
Expires: Wed, 11 Jan 1984 05:00:00 GMT
Cache-Control: no-cache, must-revalidate, max-age=0
Link: <http://xxxx/wp-json/>; rel=”https://api.w.org/”
Database Caching using disk (Request-wide User is logged in)
Served from: esites.pro @ 2017-02-16 15:08:19 by W3 Total Cache –>
While not-logged this:
<!– Performance optimized by W3 Total Cache. Learn more: https://www.w3-edge.com/products/
Object Caching 1891/1916 objects using disk
Page Caching using disk: enhanced
Page cache debug info:
Engine: disk: enhanced
Cache key: xxx/w3tc_rewrite_test/_index.html
Creation Time: 1487257755.000s
Header info:
Set-Cookie: cbc_country_name=Brazil; expires=Fri, 17-Feb-2017 15:09:11 GMT; Max-Age=86400; path=/; domain=xxxx
Set-Cookie: cbc_country_code=br; expires=Fri, 17-Feb-2017 15:09:11 GMT; Max-Age=86400; path=/; domain=esites.pro
Set-Cookie: PHPSESSID=7622c3f0daf0f810df94b5837f1ee656; path=/
Content-Type: text/html; charset=UTF-8
Expires: Wed, 11 Jan 1984 05:00:00 GMT
Cache-Control: no-cache, must-revalidate, max-age=0
Link: <http://xxxx/wp-json/>; rel=”https://api.w.org/”
Database Caching 6/33 queries in 0.262 seconds using disk
Served from: xxxx @ 2017-02-16 15:09:15 by W3 Total Cache –>
What was supposed to show up? Is the warn just about speed? It looked like an error warning, telling me something on my .htaccess was not right and because of that the plugin would not work as it should, right? Any thoughts? Thank you a lot!!!
