On my 6.x sites the following errors were reported on update of backup_migrate from 6.x-2.6 to 6.x-2.7:
1. array_merge() [function.array-merge]: Argument #2 is not an array in update.php on line 173.
2. Invalid argument supplied for foreach() in update.php on line 340.
No such errors were reported on updating backup_migrate on 7.x sites, nor on any previous 6.x or 7.x module updates.
There have been similar reports from others in other circumstances but some time ago:
http://drupal.org/node/1193184
http://drupal.org/node/823776

Comments

rc.otto’s picture

The same problem:

"warning: array_merge() [function.array-merge]: Argument #2 is not an array in /www/.../update.php on line 173.
warning: Invalid argument supplied for foreach() in/www/htdocs/w00a38c7/html/drupal/update.php on line 340.

The following queries were executed
backup_migrate module
Update #6201
No queries"

dgorton’s picture

Can you confirm that the only update was 6201?

I believe this is due to a missing return on backup_migrate_update_6201. Drupal 6 expects a (missing) return array(); from hook_update_N: http://api.drupal.org/api/drupal/developer%21hooks%21install.php/functio...

vzsze’s picture

I've seen this issue, too when updating from 6.x-2.5 to 6.x-2.7. No other module was updated.


    warning: array_merge() [function.array-merge]: Argument #2 is not an array in /is/htdocs/wp1184562_0NK390C9SX/www/update.php on line 173.
    warning: Invalid argument supplied for foreach() in /is/htdocs/wp1184562_0NK390C9SX/www/update.php on line 340.

The following queries were executed
backup_migrate module
Update #6201

    No queries
dgorton’s picture

If any of you go back to your update.php, does it list the 6201 update as still pending?

carlodimartino’s picture

Same issue here and no, update 6201 update is not pending.

ronan’s picture

Status: Active » Fixed

I've fixed this in the latest dev. No need to update though. As long as 6201 is not still pending, there is no harm done with this error.

Thanks all.

Status: Fixed » Closed (fixed)

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