Thanks for a great plugin. It's saved my skin once or twice :-)
When I upgraded to 2.2.3 my schedule overnight email backups stopped working so I reverted to the working 2.2.2 and started reading and debugging.
I noted your comment about the gzipping code and memory limits. My host sets a PHP memory limit of 32M by default. WordPress increases this for access to the admin area and some other tasks.
I added this line to the wp-db-backup.php immediately after the ABSPATH check and 2.2.3 is now working perfectly for me.
Having somewhat the same problem. Tried your fix and was greeted with...
Parse error: syntax error, unexpected T_STRING in /var/www/html/blog/wp-content/plugins/wp-db-backup/wp-db-backup.php on line 36
Actually it killed the entire blog. Couldn't do anything until I removed it.
My backup started failing on 21 Dec. It was scheduled for every day and to send to email. After that time, as I just discovered, it was saving the backups in the backup-nnnnn folder. Even by doing a manual backup directed at my email it would still do the same thing. Reinstalled 2.2.3 with no improvement. In fact, now a manual backup goes nowhere - not email, and not the folder.
I'm working on a 2.2.4 fix for people with insufficient memory. Unfortunately, not every host allows you to increase PHP's memory like that, but it's one approach among others I'll attempt.
FYI, even though I was unable to reset my memory_limit from within the script, I did attack the php.ini file and reset it to 64M there. A subsequent backup to email just now worked fine.
I am having the same problem. Since this upgrade, my scheduled backups aren't emailing. I just discovered, completely by chance, that it is saving the scheduled backups to my server instead. But I don't really know/understand what you're talking about above in regard to php size and a fix...?
Austin,
Thanks for a great plugin. It's saved my skin once or twice :-)
When I upgraded to 2.2.3 my schedule overnight email backups stopped working so I reverted to the working 2.2.2 and started reading and debugging.
I noted your comment about the gzipping code and memory limits. My host sets a PHP memory limit of 32M by default. WordPress increases this for access to the admin area and some other tasks.
I added this line to the wp-db-backup.php immediately after the ABSPATH check and 2.2.3 is now working perfectly for me.
@ini_set('memory_limit', 64M);
Having somewhat the same problem. Tried your fix and was greeted with...
Parse error: syntax error, unexpected T_STRING in /var/www/html/blog/wp-content/plugins/wp-db-backup/wp-db-backup.php on line 36
Actually it killed the entire blog. Couldn't do anything until I removed it.
My backup started failing on 21 Dec. It was scheduled for every day and to send to email. After that time, as I just discovered, it was saving the backups in the backup-nnnnn folder. Even by doing a manual backup directed at my email it would still do the same thing. Reinstalled 2.2.3 with no improvement. In fact, now a manual backup goes nowhere - not email, and not the folder.
Running 3.0.4 and 2.2.3.
Thoughts appreciated.
John
I'm working on a 2.2.4 fix for people with insufficient memory. Unfortunately, not every host allows you to increase PHP's memory like that, but it's one approach among others I'll attempt.
Hi,
Thanks for the info.
FYI, even though I was unable to reset my memory_limit from within the script, I did attack the php.ini file and reset it to 64M there. A subsequent backup to email just now worked fine.
John
I am having the same problem. Since this upgrade, my scheduled backups aren't emailing. I just discovered, completely by chance, that it is saving the scheduled backups to my server instead. But I don't really know/understand what you're talking about above in regard to php size and a fix...?
@John,
Re the syntax error. I can only think that something was missed when you made the amendment.
Make sure that line is added exactly as typed about and with non-curly quote marks.
If you still can't get it to work you'll be best waiting for the official update.
RSS feed for this topic
Reply
You must log in to post.