warning: array_merge_recursive() [function.array-merge-recursive]: Argument #2 is not an array in /path/includes/form.inc 1373 [#1169920]

I get following warning on every page:

warning: array_merge_recursive() [function.array-merge-recursive]: Argument #2 is not an array in /path/includes/form.inc on line 1373.

after updating drupal from 6.20 to 6.22 by deleting, restoring sites and htaccess, runing update.php & cron.php

and updating modules: filefield, imageapi, imagecache, token, imagefield, uc_disconts_alt, emfield, jstimer.
Deleted old files, uploaded new, ran update.php and cron.php

This site runs in a multisite shared tables environment. none of the other pages show this error after process.

any thoughts?

Comments

Comment #1

Al.D CreditAttribution: Al.D commented 26 May 2011 at 17:51

uc_discounts_alt is probably irelevant.
this was updated for other portions of multisite environment. And the other sites don't have errors.

Comment #2

Al.D CreditAttribution: Al.D commented 27 May 2011 at 10:16

Project:	Drupal core	» FileField
Version:	6.22	» 6.x-3.10
Component:	other	» Code
Status:	Active	» Needs work

I fixed this issue. The Problem was Filefield. There were lots of weiredly random errors, because filefield had deactivated itself during update. Allthough filefield was required by imagefield and it was activated!
even weireder was that when i deactivated imagefield, because the checkbox for filefield was locked because required allthough it was deactivated (!?), filefield then re-activated itself automatically while I deactivated imagefield. After I reactivated imagefield everything was fine again.

I found a few recent posts on this subject after i knew what was the problem:
Filefield deactivates itself during update. regardless of if it is required by other, depending modules.
I think this needs some work. Still I could be wrong, but I suppose it would be the best for filefield-developers to check on this problem.

Comment #3

quicksketch

he/him

CreditAttribution: quicksketch commented 28 May 2011 at 22:09

ImageField had a problem where it would disable itself if it couldn't find FileField (though it was fixed several releases ago, it still can happen when updating from a very old version). I've never heard of FileField disabling itself though. In any case, I don't see anything in this issue that is actionable. FileField doesn't disable itself in any way that I know of, any other module may have turned it off.