Viewing 15 replies - 16 through 30 (of 36 total)
  • Thread Starter Peter

    (@geoorgge1968)

    Do you set wp-config.php to 444 permission ?

    W3 Total Cache is telling me:

    Plugin could not be activated because it triggered a fatal error.
    …/FilesAug04/wp-config.php could not be written, please edit config and add:
    define(‘WP_CACHE’, true); before require_once(ABSPATH . ‘wp-settings.php’);

    If you have selected to disable write permissions in “System Tweaks” the plugin will set .htaccess and wp-config.php to 0444

    Thread Starter Peter

    (@geoorgge1968)

    W3 Total Cache does not like it.

    Just remove the Tweak ?

    Yep. You can just turn it off. If W3TC is already installed it shouldn’t complain (I use both). It’s only during W3TC configuration that it needs to write to wp-config.php. When I do hit a plugin that does this I turn off the write permission features, configure the other plugin, and turn it back on.

    Thread Starter Peter

    (@geoorgge1968)

    I disabled W3TC after I had the caching issues. Now I cannot reactivate with config access.

    But switching the Tweak off, does not change permissions back to 644.
    So I do it manually.

    Try saving “System Tweaks” one more time. It always changes to 0644 to confirm it can write then changes back to 0444 if the option is selected. If the options are cached however (apc, etc) it may take an extra save to make it work.

    Thread Starter Peter

    (@geoorgge1968)

    Too late. W3T is activated.

    OK. Thanks. Working on clearing opcode caches throughout a little better (it can hold up a LOT of settings).

    Thread Starter Peter

    (@geoorgge1968)

    activated. But .htaccess still 444.
    So I retry tweak enable disable.

    Hmm, I can confirm that it is working for me with the dev version, w3tc, and php 5.4.4. If I set the “Remove write…” option it goes to 444 if I turn it off it goes to 644

    Thread Starter Peter

    (@geoorgge1968)

    I switch on and off this:

    Protect Files
    Prevent public access to readme.html, readme.txt, wp-config.php, install.php, wp-includes, and .htaccess. These files can give away important information on your site and serve no purpose to the public once WordPress has been successfully installed.

    Warning: This feature is known to cause conflicts with some plugins and themes.

    We are speaking of the same ?

    Ahh. No. In the last section turn off “Remove write permissions from .htaccess and wp-config.php”

    I know.. I need to find a way to make this less confusing…

    Thread Starter Peter

    (@geoorgge1968)

    I mixed the two up. One is external read, the other write…

    Thread Starter Peter

    (@geoorgge1968)

    I have checked the box now for Write to WordPress core files. It was unchecked since I changed it before. htaccess still444

    Thread Starter Peter

    (@geoorgge1968)

    Unchecked and saved 2 times.

    Settings Saved. You will have to manually add rewrite rules and wp-config.php code to your configuration. See the Better WP Security Dashboard for a list of the rewrite rules and wp-config.php code you will need.

    htaccess still 444 (even after leaving directory and coming back later)

Viewing 15 replies - 16 through 30 (of 36 total)
  • The topic ‘[Plugin: Better WP Security] Away Mode: Removed all bit51_bwps options, Still redirecting’ is closed to new replies.