[wp-hackers] Backup plugin and writability
skippy at skippy.net
Sun Jan 8 18:08:41 GMT 2006
Elliotte Harold wrote:
> I enabled the WordPress 2.0 backup plugin and tried to backup. I got
> these two messages:
> WARNING: Your wp-content directory is NOT writable! We can not create
> the backup directory.
> WARNING: Your backup directory is NOT writable! We can not create the
> backup directory.
> 1. Why is it trying to writing anything to /var/www/cafe/?
> /var/www/cafe/wp-content/backup-05ad9/ I understand, but /var/www/cafe
> shouldn't need to be written.
It's checking whether it can create the directory it needs.
> 2. Why isn't it using /usr/tmp for temporary files like a good Unix
WordPress is not a good UNIX program, it's a web-based application. It
might be running on Windows, in which case /usr/tmp is a bogus value.
> 3. Is there any way to configure it to tell it to use this location
You can edit the plugin as needed. Line 22:
define('WP_BACKUP_DIR', 'wp-content/backup-' . $rand);
> I'm very nervous about making directories world writable just so
> WordPress can muck with them.
As am I. I started a thread about this just before the 2.0 release.
Matt's official response was "wp-content was always meant to be writable
by the webserver".
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
More information about the wp-hackers