Closed (fixed)
Project:
Content Construction Kit (CCK)
Version:
5.x-1.6
Component:
fieldgroup.module
Priority:
Critical
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
30 Oct 2007 at 18:02 UTC
Updated:
27 May 2008 at 06:30 UTC
Comments
Comment #1
jayjenxi commentedThis is the error I get in the admin panel:
warning: Invalid argument supplied for foreach() in /home/folder/public_html/modules/cck/content_admin.inc on line 418.
Here's the foreach() argument
Comment #2
pcorbett commentedI'm having the same issue, but with two of three node reference fields I have. They are missing in Manage Fields, but they appear in the Display Fields page...
Comment #3
pcorbett commentedI fixed this by undoing a core change I had made way back where I had increased the "weight" range from -10 to 10 TO -20 to 20. There is code in cck (content_admin.inc I believe) that explicitly uses the -10 to 10 range (not sure why maybe someone can shed light on this).
Comment #4
jayjenxi commentedThat's good news. Could you guide me through how you did it? I'm not quite sure what you mean by undoing a core change.
Comment #5
pcorbett commentedIf you haven't changed anything in the core code provided with a default Drupal install, then you're probably not having the same issue I am. I had "hacked" includes/form.inc (I believe) to allow weights to go from -20 to 20 rather than -10 to 10. Have you done this? If not, then this may not help you.
Comment #6
jayjenxi commentedNo, I haven't done anything to the core. Well, thanks anyway. I really appreciate your efforts.
Comment #7
MrPrise commentedI had this error when my content type has CCK fields which I don't currently installed. They remained in the database from the past, but since then I reinstalled my code without wiping out the database. CCK would try to use them from the db, but without the corresponding module installed it is unable to handle them. In my case when I installed the required modules (CCK_fullname and CCK_address), the warnings are gone.
Comment #8
christefano commentedThis has happened to me, as well, and I concur with MrPrise's explanation.