Forum Replies Created

Viewing 1 replies (of 1 total)
  • This happens because updating W3TC does a pretty inconvenient thing which should probably regarded as a bug. Once I updated w3tc it completely eliminated all settings that were there before (Performance->General Settings).

    It also reverts to disk-basic for all caching which means it wants some directories that probably aren’t there in your install, e.g. wp-content/cache and wp-content/w3tc-config which you can fix for example by doing commands like so *before* updating w3tc :

    mkdir -p /home/yourwebsite.com/html/wp-content/cache/tmp && chown -R nginx.nginx /home/yourwebsite.com/html/wp-content/cache && mkdir -p /home/yourwebsite.com/html/wp-content/w3tc-config/ && chown -R nginx.nginx /home/yourwebsite.com/html/wp-content/w3tc-config/

    Obviously replacing /home/yourwebsite.com/html with the correct path for your website’s root html directory and nginx.nginx with the use the webserver is running as.

    Once you’ve done this you can do the update without getting a text editor involved and going through manual deactivate/reactivate.

    If you’ve already done the original instructions above, you probably want to verify your performance->general settings didn’t get blown away by it, and if you’re still having the errors maybe try that command to see if it fixes it.

Viewing 1 replies (of 1 total)