• Resolved panan

    (@panan)


    I am getting error at the top of my dashboard;
    Plugin could not be activated because it triggered a fatal error.
    /public_html/mydomain.com/wp-config.php could not be written, please edit config and add:
    define(‘WP_CACHE’, true); before require_once(ABSPATH . ‘wp-settings.php’);

    so I did as what it says and it solved the problem,but now my question is: should I keep it permanet as what I did to wp-conif.php?
    do I have to remove(remove define(‘WP_CACHE’, true); from wp-config.php)it again after activated the plugin.
    Thank you for any advice on this.

Viewing 3 replies - 1 through 3 (of 3 total)
  • On our site (freeandeasyblog.com) we are also running W3 Total Cache Plugin as well and we also have define(‘WP_CACHE’, true); in our config.php file as well.

    I would make sure to leave the caching code there as this informs wordpress to try and cache the data so that it does not run as many database queries which could slow down your site. So having that code in the wp-config.php is a good thing.

    If you need more details about what each function means in the .htaccess file you can visit: https://codex.www.ads-software.com/Editing_wp-config.php

    Thread Starter panan

    (@panan)

    Thanks for your reply.
    I am also see the below error and I do not know what to do with them.
    it would be helpfull if you can give any video tutorial for all this things set up for newbies.

    You’ve selected disk caching with enhanced mode however the .htaccess file is not properly configured. Please run 777 chmod /public_html/mydomain.com/.htaccess,

    You’ve enabled Browser Cache feature however the .htaccess file is not properly configured. Please run 777 chmod /public_html/mydomain.com/.htaccess,

    The error you are seeing really depends upon what you would like to do. If you want to use Browser Cache then you can make the permissions of the .htaccess 777.

    The plugin is asking you to do this because it wants to add some custom caching code to your .htaccess file to help with site loading. In order for the plugin to write the code to the .htaccess it needs 777 permissions to do this action.

    You can make this change to 777 and let the plugin write to it, after it does this step you can change the .htaccess permissions back to whatever you would like.

    *Please Note: If you host is running something like suPHP then it will block the 777 permissions, in this case make the permissions 755.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘[Plugin: W3 Total Cache] getting fatal error after instalingW3 Catch’ is closed to new replies.