Currently I’m using /up as the default upload folder. It’s the one and only folder that’s currently writable and according to my company policies, it’ll remain so.
I’m trying to use /up as the working folder for W3TC, so I had my share of tinkering with define.php, and with the 3 php files that get copied from lib/W3/Plugin to the working folder.
I haven’t been able to make it work, though. In fact, it seems that I’ve managed to erase most of my development installation content.
Haven’t you considered leaving the working folder or path for the user to choose? As I told you, there’s no way in hell our platform engineers would agree giving the folder wp-content a 777 permision.
Ok, let’s disregard that 777 and say 755. In our production environment, everyting but /up is 644.
BTW, I didn’t erase anything. It was just DB caché returning an empty result.
You tried symbolic links? Not all define statements are supported.
Thing is: our APP machines mount the blog folders from a read only NFS volume, in which the /up folder is NFS mounted to a writable volume.
I could mount w3tc folder on that writable volume too, but I’d won’t be able to update configuration files nor create any of the php scripts that must be copied to /wp-content dir. I wouldn’t mount the whole /wp-content dir in the writable volume either, because it’s purpose is prevent an unauthorized modification of the files.
I’ve rewriten most settings to run on /up but I’m not sure if it’s actually working. I’ve got front, db and obj caching and the html reads:
<!– Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/
Object Caching 0/0 objects using memcached
Now I’m not sure if it’s actually not working or just not appending the stats to the html. Most hits are coming through 127.0.0.1 instead of visitor’s IP so I’m pretty sure something is happening.
- The topic ‘[Plugin: W3 Total Cache] Change storage dir’ is closed to new replies.