The following appears on my Drupal 6.4 homepage right after installing CCK, Date, and Email modules:
warning: Invalid argument supplied for foreach() in /home/encuent/public_html/ahora/modules/cck/content.module on line 1130.
warning: Invalid argument supplied for foreach() in /home/encuent/public_html/ahora/modules/cck/content.module on line 1170.
warning: Invalid argument supplied for foreach() in /home/encuent/public_html/ahora/modules/cck/content.module on line 1170.
warning: Invalid argument supplied for foreach() in /home/encuent/public_html/ahora/modules/cck/content.module on line 1170.
I have no idea about how to remove this... any leads?
Comments
Comment #1
yched commentedTry clearing your site's cache (admin/settings/performance, hit 'cliear cached data' at the bottom of the page).
Try temporarily disabling Email module.
Comment #2
javajones commentedUnfortunately these steps did not work; any other suggestions? Should just add that the problem only appears on the home page.
Thanks!
Comment #3
javajones commentedIn another thread--http://drupal.org/node/250713--someone with a similar problem suggested deleting the CCK module and uploading a fresh one; I am a little skittish about doing that but may be desperate enough to try.
Comment #4
javajones commentedComment #5
dgoldenbaum commentedI resolved this issue by clearing content, then re-creating content in the system. all good now.
Comment #6
javajones commentedThanks for this lead. How do I clear the content? By "Unpublishing" everything?
Comment #7
dgoldenbaum commentedsorry, that was probably a little misleading... i'm using the devel module to generate content, so likewise, i used devel to delete all the content.
Comment #8
javajones commentedThanks for the clarification. Unfortunately, the suggested solution does not apply to my situation. Any other ideas. I wish the error code could just be sent to some other page than the homepage!
Comment #9
javajones commentedbump!
Comment #10
karens commentedDid you disable the Email module? Do you have any other CCK modules enabled that are not a part of the CCK core tarball? If so, disable them, too. Also move up to the latest -dev version of CCK, there are other changes since rc7 so you need to see if something else has already fixed your problem.
Comment #11
javajones commentedThanks,
I will try this and report back...
Comment #12
yched commentedSo far we intentionally left the code unshielded, precisely because it detects that some code somewhere (either in core or in 3rd party contrib) is doing something wrong. However, while CCK is not the source of the bug, those issues end up polluting the our issue queue, generating threads that quickly become flooded with unrelated 'me too's because such problems can come from many different sources. Enough with this.
I added code in the few places I could spot that could get broken to babysit invalid incoming data.
Comment #13
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.