I'm finding that there are copies of the backup files in the root directory of the website.
Not a big deal as the files are being transferred to my dropbox. I just delete them but if users are unaware of this they may find they accumulate quickly depending on the frequency of backups.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | backup_migrate_dropbox-copies-files-website-root-directory-1326534-5640700.patch | 739 bytes | danny englander |
Comments
Comment #1
jdanthinne commentedJust saw that as well, there were about 100 backups in my root folder… not very good!
Comment #2
danny englanderI have had this same issue sporadically, I think Backup Migrate Dropbox somehow temporarily puts it in root before it transfers it to Dropbox but I could be wrong about this. I first get this error:
Could not run backup because the file could not be saved to the destination.... and then I see:
There was a problem when we tried to save the file to Dropbox, the error message was: File '/home/mysite/public_html/mybackup-2012-02-22T14-45-45.mysql.gz' does not exist or is not readable.-- Note that public_html is synonymous with 'root' in my case.
Comment #3
danny englanderLooking into my logs further, I also see this error:
I am not sure what it means but it implies a permissions error but I think it's a little more serious than that...
Comment #4
danny englanderI have what I think is a fix for this based on the comment here.
This is the first patch I have made using git so I hope it's ok and that people can test it but it fixed the issue here for me. What happened is that some code from 6.x was inadvertently added to the 7.x branch. This patch addresses that.
variable_get('file_directory_temp', '')should actually be:
variable_get('file_temporary_path', '')... in destinations.dropbox.inc
Comment #5
danny englanderComment #6
pefferen commentedthanks highrockmedia the patch in #4 works for me.
Comment #7
wundo commentedThanks, pushed to 7.x-1.x branch