warning: array_merge(): Argument #2 is not an array in /sites/all/modules/cck/content.install on line 43.

This could happen if a field has been incorrectly updated, maybe by a module or manually.

To find the field(s) that's causing this, please use phpMyAdmin (or similar) and browse the {content_node_field} table in search for rows where the column global_settings is empty, or it does not have a format similar to "a:#{...}", where # is an integer, and there's more stuff between the brackets.

The column field_name should tell you which field it is, and then you may try to fix this from that field settings panel and submit.

Prior to trying anything else, please make backups, just in case...

Once this is fixed, if the problem re-appears, then it could be caused by a another module.

Hello,

I just upgraded to cck 2.4 and i also have this warning message.
When i browse {content_node_field} table , global_settings column is fine, as indicated.

Do you have any other idea on how to solve this error message or identify the cause?

Thanks,

Matt

I currently have this same error: warning: array_merge() [function.array-merge]: Argument #2 is not an array in /Users/Cale/Sites/acquia-drupal/sites/all/modules/cck/content.install on line 43.

It pops up whenever I update my modules list. The latest with the Location module.. http://drupal.org/node/1336040

I also received the error after enabling flexifield module for the first time. If I refresh the page it disappears every time. Don't know what the problem even is... but think now it has to do with CCK

note: I had the problem with 6.x-dev.. and just installed 6.x-2.9 but received the same error.

I followed advice in #1 and wish I had more knowledge of the database to identify a 'bad' node field. But I see no missing rows under "global_settings"

Is there something else I can look for?

RESOLVED:

Go to phpMyAdmin (or similar) and browse the {content_node_field_instance} table in search of a field that is missing in the {content_node_field} table.

In my case (at one point in time) i must have manually deleted a field in {content_node_field}. As a result, I started getting the error above BECAUSE, even though this field had been deleted in {content_node_field}, it still appeared in {content_node_field_instance}

IF YOU DELETE the field in both tables, you will resolve your issue!