tag:blogger.com,1999:blog-6395361280120165112.post3991244196754581191..comments2023-05-11T17:58:36.074+02:00Comments on Treble Click: Fix 404 pages W3 Total Cache in WPESVhttp://www.blogger.com/profile/00378746204489625224noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-6395361280120165112.post-21213164562233227732010-09-28T00:49:33.967+02:002010-09-28T00:49:33.967+02:00This is completely unrelated, but it just came to ...This is completely unrelated, but it just came to my mind. The <i><IfModule mod_rewrite.c></i> and its closing counterpart <i></IfModule></i> could be commented out once you make sure that such module IS activated on your server. <br /><br />It just eats up some (few) cycles of your server on each request. And it is configured that way on each default installation!ESVhttps://www.blogger.com/profile/00378746204489625224noreply@blogger.comtag:blogger.com,1999:blog-6395361280120165112.post-83693898611068446352010-09-27T20:37:23.901+02:002010-09-27T20:37:23.901+02:00I have to mention that the support of the W3TC dev...I have to mention that the support of the W3TC developer, <a href="http://twitter.com/w3edge/" rel="nofollow">Frederick Townes</a> on the topic has been great and lightning fast.<br /><br />Nevertheless, I'm still quite positive that after the W3TC uninstall process the rewrite engine part of the main .htaccess was somehow removed. I was even able to find <a href="http://wordpress.org/support/topic/plugin-w3-total-cache-404-on-every-page-when-disabled" rel="nofollow">something similar on the WP Support Forums</a>. Anyway, now it isn't something very worrying.<br /><br />If you are on dedicated server environments or if the server will be managed by users with good technical knowledge, W3 Total Cache would still be worth using - it's a cache plugin of unrivalled power on good hands.ESVhttps://www.blogger.com/profile/00378746204489625224noreply@blogger.com