Active
Project:
Content Construction Kit (CCK)
Version:
6.x-2.x-dev
Component:
content.module
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
20 Jan 2011 at 21:19 UTC
Updated:
31 Aug 2013 at 23:26 UTC
Comments
Comment #1
karens commentedUnable to replicate this problem. And I can find no reference to anything called 'data' on that line, or anywhere else in that function in the current code.
Comment #3
gateway69 commentedSorry I had to open this, I just ran into this today on a fresh install of drupal on my ubuntu system..
I see about 4 or so undefined indexes when adding a new content to a content type.
the above one is valid but im also seeing these
this is the line of code
I no php guru but if i can help debug let me know..
Comment #4
chromix commentedI also started seeing this error pop up when using the Link module.
http://drupal.org/node/830432#comment-5263232
This is with 6.x-2.9, I should point out. Changing line 1031 to this worked perfectly, though:
Comment #5
brad.bulger commentedjust a note to anyone else researching this error - it looks as if CCK is expecting the node field value to have all of the keys returned by content_database_info() for the field type, and some modules that define field types are not doing that. see #2078651: Notice: Undefined index: url in content_storage(), for example. so i guess the question is, is that a reasonable expectation, so that the problem is really on the module defining the field type to meet it, or should CCK handle the case when the column is undefined? a change that would preserve current behavior but prevent notices would be more like
so that it still creates the key/value pair in
$record.