i just installed and activated wp-db-backup 2.1.4 and when i went to the Manage -> Backup tab the following messages were displayed:
.
--
WARNING: Your wp-content directory is NOT writable! We can not create the backup directory.
/wordpress/wp-content/backup-96d3c/
--
WARNING: Your backup directory is NOT writable! We can not create the backup directory.
/wordpress/
--
.
.
obviously these messages were generated because the write permissions need to be set. but why two messages?
.
i'm assuming that the first message is because wp-db-backup want's to create the "backup-96d3c" directory. (btw, why "96d3c"? how is that number generated?)
.
why is there a second message that's referring to the root of the WP installation? is wp-db-backup attempting to write some additional information?
.
.
how do i change my backup directory ("backup-96d3c" located beneath my WP installation is less than ideal for me)?
.
.
when wp-db-backup saves a backup to a directory, what does it do with any backups that already exist in said directory?
.
.
is there any documentation for the wp-db-backup plugin?
.
.
can _scheduled_ backups be set to save to a directory rather than being sent via email?
.
.
how are backup names constructed?
.
.
thanks,
david
obviously these messages were generated because the write permissions need to be set. but why two messages?
You need the backup directory for the backups; if it doesn't exist, the plugin tries to create it. In your case, the backup directory doesn't exist and the parent directory isn't writable, so you get two error messages.
btw, why “96d3c”? how is that number generated?
It's based on a double hash of your database password (don't worry--it can't be reverse-engineered). That makes it practically impossible to guess, helping to reduce the possibility that someone could guess the path to one of your backup files.
how do i change my backup directory (”backup-96d3c” located beneath my WP installation is less than ideal for me)?
You can change the following line: define('WP_BACKUP_DIR', 'wp-content/backup-' . $rand);
to something else: define('WP_BACKUP_DIR', 'some/other/directory/no/higher/than/the/WordPress/directory/');
when wp-db-backup saves a backup to a directory, what does it do with any backups that already exist in said directory?
Nothing.
is there any documentation for the wp-db-backup plugin?
There is a readme file included with the plugin download. That's about it.
can _scheduled_ backups be set to save to a directory rather than being sent via email?
Not currently. For one thing, I don't want to encourage people to leave backups on their server, as it increases the possibility that their data will be compromised. For another, there's a good risk of someone filling up their drive with backups.
how are backup names constructed?
A combination of the database name, the date, and the time.
i just installed and activated wp-db-backup 2.1.4 and when i went to the Manage -> Backup tab the following messages were displayed:
.
--
WARNING: Your wp-content directory is NOT writable! We can not create the backup directory.
/wordpress/wp-content/backup-96d3c/
--
WARNING: Your backup directory is NOT writable! We can not create the backup directory.
/wordpress/
--
.
.
obviously these messages were generated because the write permissions need to be set. but why two messages?
.
i'm assuming that the first message is because wp-db-backup want's to create the "backup-96d3c" directory. (btw, why "96d3c"? how is that number generated?)
.
why is there a second message that's referring to the root of the WP installation? is wp-db-backup attempting to write some additional information?
.
.
how do i change my backup directory ("backup-96d3c" located beneath my WP installation is less than ideal for me)?
.
.
when wp-db-backup saves a backup to a directory, what does it do with any backups that already exist in said directory?
.
.
is there any documentation for the wp-db-backup plugin?
.
.
can _scheduled_ backups be set to save to a directory rather than being sent via email?
.
.
how are backup names constructed?
.
.
thanks,
david
You need the backup directory for the backups; if it doesn't exist, the plugin tries to create it. In your case, the backup directory doesn't exist and the parent directory isn't writable, so you get two error messages.
It's based on a double hash of your database password (don't worry--it can't be reverse-engineered). That makes it practically impossible to guess, helping to reduce the possibility that someone could guess the path to one of your backup files.
You can change the following line:
define('WP_BACKUP_DIR', 'wp-content/backup-' . $rand);to something else:
define('WP_BACKUP_DIR', 'some/other/directory/no/higher/than/the/WordPress/directory/');Nothing.
There is a readme file included with the plugin download. That's about it.
Not currently. For one thing, I don't want to encourage people to leave backups on their server, as it increases the possibility that their data will be compromised. For another, there's a good risk of someone filling up their drive with backups.
A combination of the database name, the date, and the time.
RSS feed for this topic
Reply
You must log in to post.