Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
When running database updates after upgrading the module to version 7.x-3.3 I am receiving the following error:
Update #7305
Failed: DatabaseSchemaObjectDoesNotExistException: Cannot change the definition of field backup_migrate_profiles.machine_name: field doesn't exist. in DatabaseSchema_mysql->changeField() (line 462 from /includes/database/mysql/schema.inc).
Comment | File | Size | Author |
---|---|---|---|
#9 | backup_migrate-n2917959-9.patch | 1.48 KB | DamienMcKenna |
|
Comments
Comment #2
couturier CreditAttribution: couturier as a volunteer commentedCan you still duplicate this error under the current 7.x-3.5 release?
Comment #3
s427 CreditAttribution: s427 commentedI have the same problem and I can confirm that it still occurs under the latest (7.x-3.5) release.
Since update 7305 fails, the new update (7306) isn't applied either.
On the Status report page, Drupal warns me that those update should be performed immediately. So it would be nice to have a fix.
Comment #4
s427 CreditAttribution: s427 commented(Actually, I "solved" it by uninstalling and reinstalling the module.)
Comment #5
couturier CreditAttribution: couturier as a volunteer commentedThat's weird. I guess we will leave this issue open a little longer to see if anyone else is having this problem, but it sounds random and rare.
Comment #6
liquidcms CreditAttribution: liquidcms commentedYes, i get same issue when trying to run update after upgrading to 7.35
Comment #7
Andru CreditAttribution: Andru as a volunteer commentedSame error, on 7.58 updating backup_migrate to 7.x-3.5.
Likewise disabling, uninstalling, and re-enabling the module fixed this.
On PHP 7.0.
Comment #8
couturier CreditAttribution: couturier as a volunteer commentedOkay, so apparently some people are having this problem but not others. I don't recall seeing any old issues similar to it, so it could be something that was introduced with the 7.x-3.3 release and has continued until now with the 3.5. If so, we are currently working on another unrelated problem that we think can be traced to a commit that introduced an error within a certain time frame from one release of Backup and Migrate to the next. You can see how we found which commits might have been relevant at this comment.
Following up to @Andru at comment #7, is there any chance this error could be related to the version of PHP in use? I'd be curious which version other reporters were using.
Comment #9
DamienMcKennaDoes this fix the problem?
Comment #11
DamienMcKennaComment #13
DamienMcKennaCommitted.
Comment #14
liquidcms CreditAttribution: liquidcms commentedI just grabbed latest -dev and i still get this error when running updates:
Will do uninstall/re-install.
Comment #15
liquidcms CreditAttribution: liquidcms commentedUninstall/reinstall worked.
Comment #16
couturier CreditAttribution: couturier as a volunteer commentedComment #18
drupal-son CreditAttribution: drupal-son commentedExactly the same situation than #14 and #15.
Comment #19
m.stentaThere is a bug with the commit made in comment #12 above. $machine_name is not defined.
Line 857 of install file: https://cgit.drupalcode.org/backup_migrate/tree/backup_migrate.install?h...
Comment #20
DamienMcKennaI've uploaded a patch in #3033583: CTools exportables code no longer loading that might fix the bug, let's continue the discussion there.