Upgrade to 6.5 and cck2.0-rc10 array_merge error on activating mods

Please note that disabling contrib modules is usually only needed for major cure upgrades (5.x -> 6.x), not for 'point releases' (x.3 -> x.4).
Now, the error you report is surprising - In normal circumstances, unserialize($row['global_settings']) should always be an array.

I'd be interested to take a look at a db dump of your 'content_node_field_instance' table. Could you provide this as a .txt attachment ? (or send it through my contact form, if you prefer)

Also, was your site upgraded from D5, or was it created in D6 ?

Doh, sorry, it's the 'content_node_field' table I need :-)

I just upgraded Drupal and CCK tonight, and got the same errors. I found this on the site: http://drupal.org/node/130060

Since it's the same error, I tried the same fix and it seems to have worked:

content.install, line 43,
change
$field = array_merge($row, unserialize($row['global_settings']));
to
$field = array_merge((array)$row, (array)unserialize($row['global_settings']));

I re-ran update.php (which is when I got it, since I didn't disable my modules) and no errors the second time through. I then updated another site on the same server, and it didn't give me any errors either.

I don't have a clue exactly what I did or the consequences of it, it just looked like it might fix the problem and it appears to have. Until I find out I broke something else, I'm going to live in blissful ignorance.

This happens because you have a record in the content_node_field_instance table that has no corresponding entry in then content_node_field table (meaning : a field instance with no actual field definition). At least that's the case for miahawk, I'm ready to bet it's also true for cindyr.

Not sure how you got there, but that's a (minor) case of db inconsistency (easily fixed, see below), and :
- we don't babysit broken code or db,
- it is actually better to get a notion that something is wrong rather than silently failing. If we get tons of those reports, then we might need to check if our code currently leads to such inconsistencies,
so right now I won't change the code to prevent the error.

To fix your installs :
- open up phpMyadmin or whatever db admin tool you use
- run the following query :

DELETE FROM content_node_field_instance WHERE field_name NOT IN (SELECT field_name FROM content_node_field)

(change table names if your db uses table prefixes)

I just ran that query and it didn't find any rows to delete. Is there something I'm missing here?

I am in the process of upgrading to 6.x and get the error every time I run update.php.

UPDATE: Nevermind... looks like it fixed itself somehow. If it shows up again I'll post a follow-up here.