I know this was mentioned in this post, but the discussion is not the same and it seemed appropriate to start a new thread.

I am upgrading by Drupal 5 site that was on cck 5.x-1.9 to Drupal 6.4. I have Views dev from sept 12 and cck 6.x-2.0-rc7. When I ran update.php I did not receive any errors. However, when I look at the Drupal logs I have a bunch of entries with the following referrer and message:

http://dev.cctv.org/batch?op=start&id=7
Message Invalid argument supplied for foreach() in /var/www/html/sites/all/modules/cck/content.module on line 1130.

Nothing really appears to be terribly wrong, but I get this error repeatedly in watchdog as well as on content type pages.

Comments

yched’s picture

yched commented
Component: content.module » upgrade path

Hm, hard to say anything clever we cannot assign those warnings to any specific update of any specific module...
Does your site have any content type other than core types and custom defined types - I mean content types *defined* by a contrib module ?

emilyf’s picture

emilyf commented

I do have Image(6.x-1.0-alpha3) and Event (6.x-2.x-dev) installed....

karens’s picture

karens commented
Status: Active » Postponed (maintainer needs more info)

That message indicates the code is looking for field info for a content type and not finding them. Did you perhaps have some fields previously that you haven't updated yet or did you leave some modules disabled that were previously enabled? Try clearing cache_content and see if that message pops up again. If not, it may have been a timing problem -- something was missing at some point in the process that is now there.

I would pull up each of your content types in the Content Types administration area and look at the fields for each content type to be sure they all still show up. Missing fields in D6 that you had in the D5 version usually indicate a missing or disabled field module. If all the fields are there, I would pull each one up and see if the settings look OK and save it again, just to be sure.

If you go through that exercise and all your fields look OK, I would guess that your data is fine in spite of that message.

karens’s picture

karens commented
Status: Postponed (maintainer needs more info) » Fixed

No response, assuming working by now.

emilyf’s picture

emilyf commented

Thanks KarenS. It looks like everything is working; I cleared the cache and went through all my types and haven't yet seen the message again. That upgrade was my test upgrade; the real thing is happening in a few days, so I'll make sure it is really all set then. But for now it looks indeed as a timing issue like you suggested.

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

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