Data not being saved

If this was a bug in CCK, then it would be happening to a lot of people out there, so it looks like there's seomthing odd in your environment that breaks the CCK fields in the node edit form.

Maybe a theme issue? Maybe incompatibility with another module?

If it is not possible to reproduce the problem, then it's hard to see what's happening.

We've been experiencing this bug lately, if it is indeed the same bug. We're using 6.x-2.1 on a site with lots of content and traffic (not sure if that's relevant atm but just thought I'd put it out there if it is). After submitting the node form while trying to create a new node, it took a few minutes before the created node was returned. The node was missing content in almost all of the CCK fields. When we tried to edit the node, sure enough, the CCK fields were blank.

What other info may be of help to the issue?

Maybe a DB issue? Is there anything in the logs?

Maybe short on memory? Maybe increasing the memory_limit option in PHP?

If that doesn't help, then maybe it is something else related to server configuration/resources.

Do you have any 'actions' (as in trigger.module) assigned to node creation or update ?

I have the same issues and do have actions assigned. When I removed them the CCK:s started working. So I guess the question now is what makes the CCK fields go bananas when a trigger is active? any ideas?

Have you tried disabling the actions?

Hi markus_petrux, it seems you wrote your post whilst I was updateing mine! ;)

simpelism : Then this is the core bug filed at #334243: trigger action kills all other module actions at node create/edit etc. (itself marked as duplicate of #298716: redirect to URL action troubles

I can't really mark this as duplicate until hochmania and bitsantos confirm that triggered 'actions' also explain their own bug reports.

@ #12 / yched - For about a month, I was having the same (weird) issue on my site www.lolsaints.com:

Upon node creation, all my CCK field data (two custom fields + an imagefield) was lost. I would have to edit the node, re-add the information, then save it again. I was scratching my head on this one, and had given up trying to figure it out.

Then I read this post, disabled the trigger/action I had on node creations (to send out an email once a new node was created), and, lo and behold, no problem any more.

Apparently, something with the trigger/action system causes CCK field data to not be stored in a node properly. I have a nagging feeling that if I set an action to be triggered upon node editing, the CCK field data would be lost at that point as well.

I can do more testing if you'd like.

@geerlingguy : trigger.module's actions ruin hook_nodeapi modules, not just CCK. This is a known bug in core's trigger.module, look the issue queue for this core component.

So all reports of this behavior so far are caused by external 'core or contrib) code, As far as CCK is involved, this is 'won't fix'

Hi, this exact problem is happening to me as well.
I have no triggers set up.
Interestingly, the data actually comes through OK in a View that pulls from these fields, but the fields themselves appear empty in the node and when I go to edit, they're mostly empty.

PHP memory limit is 256M.

Recently updated to Drupal 6.22.

In logs: here is error message "type PHP":
Column 'field_on_exhibit_view_vname' cannot be null query: INSERT INTO content_type_venue (vid, nid, field_venue_logo_fid, field_venue_logo_list, field_venue_logo_data, field_venue_location_lid, field_venue_url_url, field_venue_url_title, field_venue_url_attributes, field_venue_state_value, field_venue_type_value, field_on_exhibit_view_vname, field_on_exhibit_view_vargs) VALUES (568, 568, 735, 1, 'a:2:{s:3:\"alt\";s:0:\"\";s:5:\"title\";s:0:\"\";}', 119, 'http://www.mocajacksonville.org/', NULL, 'a:0:{}', 'Florida', 36, NULL, NULL) in /usr/local/4admin/apache/vhosts/folkart.org/httpdocs/sites/all/modules/cck/content.module on line 1213.

OK well I got it working. There was viewfield in the content type that seems to have caused this problem for some reason. I ended up removing the viewfield and the data could be entered and it would stick AOK.

Perhaps it's a problem with Viewfield then or with that particular view.

I have the same error. Only fails on update action and only in one of my content types. For me works fine on linux environments but fails on windows (IIS).
Node title and configurations saved correctly.

Note: I'm using contrib fields modules Link CCK Field and Embedded Video Field.