[Plugin: W3 Total Cache] Revision 264695 breaks .htaccess

Sorry for the trouble. Do you know how to change permissions on the file as the message shows?

Bumerangas,

Edit your .htaccess file (it’s in your domain’s root directory, same place as index.php and /wp-content etc…). Add these lines to it:

DirectoryIndex index.php

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress

Make sure you leave a carriage return after the final line (press Enter/Return). Then change the .htaccess file’s permissions to 777 (Read, Write and Execute for all users). In fact, it should be fine (and safer) at 644.

Once done, re-activate the plugin and you should be good to go.

No or at least I wasn’t successful – or tried to do thru filezila, but just got again “500 internal server error” and my host help putted another htaccess, file BAK :/

Can you give me some advice how to solve my problem? Until now the pluggin was just great and increased my pages speed time regarding Yslow results.

Waiting replay.

v0.9.1 should be available shortly. Meanwhile, you can check out this link: https://www.ads-software.com/support/topic/411535?replies=13#post-1612692

Do new update will fix errors automatically?

Thank You for replaying.

It will upgrade without error if that’s what you mean.

I just want get rid of my currently errors, and I want to use “w3 total cashe”, because I think this plug in is reliable tool. That’s all.

All works great again, after upgrade. Thank!

Great.

Frederick, 500 server error haunts me… One situation where it usually happens is when i try to preview a post before i hit publish…

I am using the latest version 0.9.1 and i faced this problem in previous versions too…

I am getting 401 errors on any minified code.

I did get an error in the W3T Cache interface notifying me that it couldn’t write to /w3tc/min/.htaccess -I 777’d the directory and clicked the retry button. The error went away, but there is no .htaccess file there and the 401 remains.

I’m on 9.1.1…

-Zach Lym

Can you deactivate and re-activate the plugin?