[wp-forums] Preping Forums for 2.0 Release

[Scott Merrill]

Vicki Frei wrote:
>> So be sure to tell everyone to make /wp-content/ writable.
>>
> 
> Is this a "you HAVE to do this"?  I have NO intention of using the wp
> backup utility personally, I manage just fine the "real" way.  So if I
> don't want to use it, I can leave the wp-content folder 644?

If you're not going to use the backup plugin, then you don't need to
twiddle permissions.

If you do want to use the backup plugin, you need to make /wp-content/
writable.  It needs to be writable so that the backup plugin can create
the pseudo-random directory.

If you would like to voice your opinion on this, here's the ticket:
   http://trac.wordpress.org/ticket/1934

Matt casts doubt on the validity of the "Hardening WordPress" Codex
page, specifically the file permissions section.  I wrote that bit, and
I stand by my recommendations.  I think that /wp-content/ should be a
container directory in which writable directories exist.

It's doubtful we'll make any changes this close to release, but we'll
never know until we try.

-- 
skippy at skippy.net | http://skippy.net/

gpg --keyserver pgp.mit.edu --recv-keys 9CFA4B35
506C F8BB 17AE 8A05 0B49  3544 476A 7DEC 9CFA 4B35