Better WP Security .htaccess write issues causing errors in W3 Total Cache

  • Resolved graphics616

    (@graphics616)


    10 years, 12 months ago

    I am getting a series of error messages at the top of my admin page for W3 Total Cache. They the following:

    FTP credentials don’t allow to write to file /homepages/25/d336955856/htdocs/mfg_oldSite/.htaccess

    W3 Total Cache Error: Files and directories could not be automatically created to complete the installation.
    Please execute commands manually [button: view required changes]
    or use FTP form to allow W3 Total Cache make it automatically. [button: update via FTP]

    Edit file /homepages/25/d336955856/htdocs/mfg_oldSite/.htaccess and remove all lines between and including # BEGIN W3TC Page Cache and # END W3TC Page Cache markers.

    When I look in .htaccess, the above mentioned strings do not exist. When I press the “update via FTP” button, I do not get a form to fill in my FTP details, just a blank line appears and nothing else happens.

    If I deselect “Remove write permissions from .htaccess and wp-config.php” in Better WP Security, the error message disappears but so does my protection against unwanted writing to the .htaccess file.

    is there a solution to this problem? I do not want to disable “Remove write permissions from .htaccess and wp-config.php” in Better WP Security, in order to have no error message, and I do not want to look at a permanent “Error” message at the top of the W3 Total Cache page as has been suggested in other posts about this same error message / configuration problem. Is there a fix for this problem?

    I am using the Better WP Security version 3.6, and W3 Total Cache version 0.9.3, along with WordPress 3.7.1.

    Thanks all.

    https://www.ads-software.com/plugins/w3-total-cache/

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter graphics616

    (@graphics616)

    Any takers on a possible answer to this? Don’t really want to disable a function of Better WP Security to make error messages go away in W3 Total Cache. Don’t want to give up on the plugin too soon either. Too many people are saying these plugins work together just fine. I just need a solution to this to move forward.

    Thanks All.

    I was wondering about this myself. I’ll watch this thread and hope you get an answer!

    hey , i think yo can’t use both of features . you must disable “Remove write permissions from .htaccess and wp-config.php” in Better WP Security, if you want to use W3 total cache , coz “Remove write permissions from .htaccess and wp-config.php” make a file permission to 444 (Read, Read, Read). W3 total cache need permission to write file (wp-config and htacces), u can disable this setting or you can make your file permission to (644) via ftp .

    So far I’ve been running both plugins with no problems. I think W3TC only changes .htaccess when you change your settings, so you should only need to disable the “Remove write permissions” when you’re changing W3TC settings.

    @graphics616, I note that your errors seems to be related to W3TC installation. It’s certainly the case that you need to allow W3TC to write to .htaccess during installation. I’d try disabling “Remove write permissions” in Better WP Security during the W3TC install and setup, then you should be able to re-enable that protection.

    Someone else feel free to chime in if I’m mistaken.

    Thread Starter graphics616

    (@graphics616)

    Thanks for the replies.

    I am running both plugins and have decided to do as Mike and ardi.wirawan212 say, and disable “Remove write permissions from .htaccess and wp-config.php” when I need to make any changes to my files. I noticed when looking at that functionality in Better WP Security they state that this setting can interfere with other plugins and that is is not a “Critical” setting to have on. I will not obsess! Lol.

    Thanks all.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Better WP Security .htaccess write issues causing errors in W3 Total Cache’ is closed to new replies.