same message here. what’s the right setting?
nope – that results in a Forbidden 403 message.
I have tried 644 and also that resulted for me in a Forbidden 403 message.
Just use the lowest number that lets the site actually work. 744, 755, who knows? Depends on the host’s configuration.
What exactly does turning off writeability for the main folder do? Will I still be able to update the site?
Obvious noob here though I understand how to change the settings. Just not sure how making that warning change to read-only will affect my WordPress installation.
i have disabled the super cache.
and gone backto wp-cache.
how are you all going with super cache?
Directories require the execute bit set to access what’s inside. That’s why you guys are seeing the 403 error when you try to access the directory.
Correct settings should be 755.
@pyang: the mode on my blog root is 755 but I am still getting the warning when I go to the super cache options page.
754978
I’m getting the warning too, with 755. What’s weird is that the warning tells me to set it to… 755.
I have a fix in trunk for this. Hopefully to be released soon.
Cool. Thought I was going crazy. I went to root even to check it out and my prem is set to 755. I noticed when I disabled write entirely (555) it was happy but given that 755 is recommend for a lot of plugins I figured that was running the risk of breaking something.
So its just a bug then?
P.S. Thankx for this plugin. It saves my site every day. 😉
Yeah, a minor bug. Glad the plugin help!
So does that mean the minor bug is the notification on the plugin admin page or is there a true vulnerability?
