After updating to 7.x-3.6 and visiting /admin/config/system/backup_migrate/restore or /admin/config/system/backup_migrate/backups I get this error:
Call to undefined function _backup_migrate_temp_files_delete() in backup_migrate_destination->list_files() (Zeile 846 von /xyz/sites/all/modules/contrib/backup_migrate/includes/destinations.inc).

CommentFileSizeAuthor
#4 backup_migrate-n3023804-4.patch461 bytesdamienmckenna

Comments

adam1 created an issue. See original summary.

damienmckenna’s picture

Version: 7.x-3.6 » 7.x-3.x-dev

Do you have any modules installed which add more destinations or sources?

adam1’s picture

I've got module backup_migrate_sftp installed. But even after disabling, the error occurs.

damienmckenna’s picture

Status: Active » Needs review
StatusFileSize
new461 bytes

Does this help?

adam1’s picture

Status: Needs review » Active

Thank you, it's working, the error message disappeared.

damienmckenna’s picture

Status: Active » Needs work
Issue tags: +Needs tests

Ok excellent.

Need to add some test coverage to make sure it works as intended.

louis delacretaz’s picture

I got the same error after updating a basic backup_migrate to 3.6. The patch in #4 fixed it

jprj’s picture

Patch #4 appears to work and can't find adverse effects

oliverpolden’s picture

#4 works for me

solideogloria’s picture

#4 works for me, too

damienmckenna’s picture

brankoc’s picture

Any suggestion as to what this test coverage would look like?

eloivaque’s picture

patch #4 Work for me.

virtualmitra’s picture

Patch #4 worked for me too. Thanks!

mtoscano’s picture

Works fine.

drupal_jon’s picture

Works for me.

maxmendez’s picture

Works for me.

solideogloria’s picture

Does 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.

damienmckenna’s picture

If 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.

solideogloria’s picture

Well, 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.

jazzitup’s picture

Status: Needs work » Needs review

I 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-dev and the error still persisted.

I can confirm a patch from #4 above fixes this issue and it may be reviewed/ported to dev.

brankoc’s picture

Note 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?

jazzitup’s picture

Hm. 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.

solideogloria’s picture

Once the temp files have been deleted, removing the patch won't do anything to break it again.

damienmckenna’s picture

Status: Needs review » Reviewed & tested by the community
Issue tags: -Needs tests

I'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.

pdcarto’s picture

Looks like this is still waiting to be committed?

  • DamienMcKenna committed 359bda9 on 7.x-3.x
    Issue #3023804 by DamienMcKenna, solideogloria, adam1, jazzitup,...
damienmckenna’s picture

Status: Reviewed & tested by the community » Fixed

Committed.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.