Closed (fixed)
Project:
Backup and Migrate
Version:
7.x-3.x-dev
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
3 Jan 2019 at 23:29 UTC
Updated:
2 Oct 2019 at 14:39 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
damienmckennaDo you have any modules installed which add more destinations or sources?
Comment #3
adam1 commentedI've got module backup_migrate_sftp installed. But even after disabling, the error occurs.
Comment #4
damienmckennaDoes this help?
Comment #5
adam1 commentedThank you, it's working, the error message disappeared.
Comment #6
damienmckennaOk excellent.
Need to add some test coverage to make sure it works as intended.
Comment #7
louis delacretaz commentedI got the same error after updating a basic backup_migrate to 3.6. The patch in #4 fixed it
Comment #8
jprj commentedPatch #4 appears to work and can't find adverse effects
Comment #9
oliverpolden commented#4 works for me
Comment #10
solideogloria commented#4 works for me, too
Comment #11
damienmckennaComment #12
brankoc commentedAny suggestion as to what this test coverage would look like?
Comment #13
eloivaquepatch #4 Work for me.
Comment #14
virtualmitra commentedPatch #4 worked for me too. Thanks!
Comment #15
mtoscano commentedWorks fine.
Comment #16
drupal_jon commentedWorks for me.
Comment #17
maxmendez commentedWorks for me.
Comment #18
solideogloria commentedDoes anybody know how to add tests for something like this? I have no experience with creating unit tests. Personally, I'd just commit the fix.
Comment #19
damienmckennaIf someone could identify the steps to reproduce the problem I'm happy to write the tests for it, I just haven't managed to trigger the problem yet.
Comment #20
solideogloria commentedWell, I know it happens specifically after updating from the 2.x branch to the 3.x branch, so I don't think it's related solely to this branch's code.
Comment #21
jazzitup commentedI didn't update the module, originally I worked with the most recent stable version 7.x-3.6, when I opened the "Restore" menu item, I bumped straight into this message. Then I
drush dl backup_migrate-7.x-3.x-devand the error still persisted.I can confirm a patch from #4 above fixes this issue and it may be reviewed/ported to dev.
Comment #22
brankoc commentedNote that for an upgrade test you would need to reproduce the database state from before and after the update. I know how this is done for core, but have no proper ideas on how to do this for contrib modules.
Simpler would be to just test the target state, i.e. do the pages admin/config/system/backup_migrate/restore and admin/config/system/backup_migrate/backups load properly?
Comment #23
jazzitup commentedHm. In the meantime I updated Drupal core to v7.67 and all the modules, tested it again without patch from #4 above and now I could open all the menu items from this module with no error messages.
Comment #24
solideogloria commentedOnce the temp files have been deleted, removing the patch won't do anything to break it again.
Comment #25
damienmckennaI'm going to forego the need for tests and just commit this, I don't believe there's any likelihood of a regression so it should be a-ok.
Thanks everyone.
Comment #26
pdcarto commentedLooks like this is still waiting to be committed?
Comment #28
damienmckennaCommitted.