Hi! I just upgraded to WP 2.1, and installed the latest WDB plugin. (i have never used any version before - shame on me :-) Even if i have set wp-content to 777 it want work, i also have set the backup-3edeb to 777 and it still doesnt work. I get these error message: The backup file could not be saved. Please check the permissions for writing to your backup directory and try again. My blog is in a subdomain, could that be the reason? Thanks-Greatings from Norway.
gormik, sometimes when PHP creates a directory, it does it as "user" that doesn't have permission to read or write files. Try deleting backup-3edeb then re-creating it yourself, using your own FTP or SSH client.
Hi there. I'm getting the same error message as Gormik got and have done as you instructed him to no avail. Permissions on the backup directory are 777. Do you have any other suggestions?
That error message is the result of failing a very basic check: trying to open that directory for writing.
To further diagnose your problem, try deleting the at sign ('@') from lines 379 and 381 of the plugin. In other words, change $fp = @gzopen($filename, $mode); to $fp = gzopen($filename, $mode); and change $fp = @fopen($filename, $mode); to $fp = fopen($filename, $mode);
Doing that might produce a more specific error message.
Unfortunately doing as you suggested created this error message:
Parse error: parse error in /home/httpd/vhosts/brucemulkey.com/httpdocs/wp-content/plugins/wp-db-backup.php on line 23
You must, of course, replace the text "backup-directory-name" with the name of the actual backup directory that you have created and applied permissions to.
Hi! I just upgraded to WP 2.1, and installed the latest WDB plugin. (i have never used any version before - shame on me :-) Even if i have set wp-content to 777 it want work, i also have set the backup-3edeb to 777 and it still doesnt work. I get these error message: The backup file could not be saved. Please check the permissions for writing to your backup directory and try again. My blog is in a subdomain, could that be the reason? Thanks-Greatings from Norway.
gormik, sometimes when PHP creates a directory, it does it as "user" that doesn't have permission to read or write files. Try deleting
backup-3edebthen re-creating it yourself, using your own FTP or SSH client.It works! Thank you very much Mr. Matzko! Greatings from Mikkelsen in Norway.
Hi there. I'm getting the same error message as Gormik got and have done as you instructed him to no avail. Permissions on the backup directory are 777. Do you have any other suggestions?
That error message is the result of failing a very basic check: trying to open that directory for writing.
To further diagnose your problem, try deleting the at sign ('@') from lines 379 and 381 of the plugin. In other words, change
$fp = @gzopen($filename, $mode);to$fp = gzopen($filename, $mode);and change$fp = @fopen($filename, $mode);to$fp = fopen($filename, $mode);Doing that might produce a more specific error message.
In order get the backup to work, I had to do the following:
1) Manually create a backup directory; e.g. /wp-content/backup-directory-name
2) Change the permissions on this directory to 777
3) Edit the backup directory definition in the plugin file wp-db-backup.php from
define('WP_BACKUP_DIR', 'wp-content/backup-' . $rand);to
define('WP_BACKUP_DIR', 'wp-content/backup-directory-name);so that it points to the newly created directory.
I found the fix after combining several threads in these discussion forums.
Hope this helps!
Regards,
taimingshen.com
Unfortunately doing as you suggested created this error message:
Parse error: parse error in /home/httpd/vhosts/brucemulkey.com/httpdocs/wp-content/plugins/wp-db-backup.php on line 23
Any other thoughts? Or did I do something wrong?
taimingshen left off a closing quotation mark: it should be
define('WP_BACKUP_DIR', 'wp-content/backup-directory-name');instead.Sorry, but I missed out a single quotation mark in the last "define" statement in my previous instructions. The statement shoud be:
define('WP_BACKUP_DIR', 'wp-content/backup-directory-name');
You must, of course, replace the text "backup-directory-name" with the name of the actual backup directory that you have created and applied permissions to.
Thank you, thank you, Taimingshen. This solved it. Be well.
RSS feed for this topic
Reply
You must log in to post.