Closed (fixed)
Project:
Backup and Migrate Dropbox
Version:
7.x-1.0-alpha1
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
5 Nov 2014 at 15:40 UTC
Updated:
29 Mar 2016 at 02:14 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
ytwater commentedI played with the code abit and I've gotten this module to work with Backup and Migrate 3 with a few small changes.
I'm attaching a patchfile, or you can update the two files below.
Hope it works for you!
Manual Update:
backup_migrate_dropbox.module
destinations.dropbox.inc
Comment #2
strategicweb commentedThe patch worked for me when I manually backed up to Dropbox, except scheduled backups aren't working for me.
When cron runs I get the following message in the logs
Warning: Cannot modify header information - headers already sent by (output started at includes/common.inc:2726) in Dropbox\OAuth\Consumer\ConsumerAbstract->authorise() (line 84 of /sites/all/libraries/dropbox/Dropbox/OAuth/Consumer/ConsumerAbstract.php).
When I manually run cron I get the Dropbox screen to authorize the app and then it still won't backup. Any ideas?
*** Update: resaved the Dropbox destination and it seems to be working now
Comment #3
drupalgideonPatch looks good.
However, originally I got an Error - The website has encountered an unexpected error. Checking the logs revealed I needed to enable MCrypt on my PHP. Once that was done, it has worked with a manual backup. Hopefully the scheduled backup will work later!
Maybe this could be added as a requirement of the module?
WRT the patch, you might want to change the hook "Implements" text to - Implements hook_backup_migrate_destination_types() to reflect the function name change :)
Comment #4
drupalgideonPatch for the implements text
Comment #5
botrisConfirming #4 to work.
Comment #6
wundo commentedComment #7
wundo commentedComment #8
botrisJust had a look the new function is only part of B&M 3 and not 2.
So I'm afraid that by committing #4 we broke compatibility for B&M 2.
If there is a need to support B&M 2 we should create a separate branche for that.