Warning during update a node

I haven't seen this in the latest 6.x-3.x releases and can't reproduce in HEAD. reopen if it is still an issue.

I'm getting the same error using 6.x-3.0-alpha4. Should I use a dev snapshot?

This one is hard to track down. Using the same modules in another test environment doesn't cause this to happen, and a search for this error message brings up results in all kinds of different modules, indicating that this is not an issue with FileField but somewhere else.
I'd appreciate if anybody could link to an explanation of what's actually going on.

reopening. let me know what I can do to help you reproduce the bug, other than what the OP already mentioned.

i think it's really a views issue.

Could you expand on that? If I understand how this relates to views I can ask for support there.

I have the same issue on 6.x-3.x-dev (2008-Nov-26) and 6.x-3.0-alpha5.
I disabled views on the server, which is a very simple site, of which filefield is a central ingredient.
I experience glitches, in the form of most files saves correctly, but sometimes a file is not saved on server, without any logevents, or notices on screen. The error message referenced above shows on new nodes and update on nodes.

I created a new content type that was the exact same as the filefield one, just without the filefield. No errors then.
When adding a filefield i get these two errors:
* warning: array_merge() [function.array-merge]: Argument #2 is not an array in /home/foo/www/sites/foo/modules/filefield/filefield.module on line 297.
* warning: array_merge() [function.array-merge]: Argument #1 is not an array in /home/foo/www6/sites/foo/modules/filefield/filefield_widget.inc on line 173.

And then when adding a node of this type:
warning: array_merge_recursive() [function.array-merge-recursive]: recursion detected in /home/foo/www/includes/module.inc on line 473.

As I said in the last comment, views is disabled on this site.

I'm marking #335844: File lists missing as a duplicate of this issue, but it's worth reading that one as there's some investigation there as well.

I can replicate, and it's a serious problem. I can't tell if it involves data loss or not, so bumping to critical until we're sure. It really has to get fixed either way.

Edit: OK I'm wrong, it doesn't look like it's a dupe as the error is in a different place. Still, should be fixed. :-)

I think like drewish says in #6 it might be related to views. It happened to me after exporting my views to a module and 'clear views cache'.

I am having the same issue and pinpointed that the FileField Paths module was causing the above 'warning: array_merge_recursive()' error.

The issue has been reported here http://drupal.org/node/311526

The usage of the 'FileField Path' is not that high so I would guess that some of the above issues are not related to the 'FileField Path' module. Hopefully this helps someone.

I am just building a new website and haven't put in views or filefield_paths and get this error when I preview the content type's submission form while using the dev version from November 17th (the one bundled with Acquia Drupal). I have no content on the website yet, just building out content types.

If I roll back to 3.0 Alpha 5 (October 7th), the error goes away. Updating to the 3.x Dev (January 6th) also fixes the error.

Marking as fixed. If other conflicts arise that causes this error again, it can be reopened.

Using Alpha 6 and I get this error 2x for every pix I upload

array_merge_recursive() [<a href='function.array-merge-recursive'>function.array-merge-recursive</a>]: recursion detected in /.../includes/module.inc on line 473.

Modules Installed that might effect this
FileField Paths
FileField Tokens
ImageField
ImageCache
Pathauto
Transliteration
Token

Setttings that might effect it
Number of values: Unlimited
File path: [type]/[CCK-field_content_taxonomy_term]
No Alt, Title or Description.

Is a FileField Paths bug

see: #311526: Recursion error in filefield_paths

Hi!
I have the exact same issue on the same line as described in the description. This is a"clean install with no settings made.
Thanks!
Brian Brown, Ph.D.

It turns out that my issue (which was IDENTICAL to this issue) was being caused by the twitter module!
-Brian