I'm not sure if this is in the base module, or the user registration module...

I thought it might be a contemplate issue... so I opened #417824: Not clearing cache for contemplate display, shows old data from a location cck field that was updated

but then I found this old content profile issue #337182: Profile fields not updated in user data

Maybe I'm using the wrong php code in contemplate.... I'll go update the contemplate issue with more information.

Please let me know if you have any ideas!

Comments

yesct’s picture

yesct commented

content_profile_load()?

seaneffel’s picture

seaneffel commented

I also am having trouble with this. I am using the Mar 30, 2009 content profile dev module and I cannot edit the fields in any content profile node.

I've upgraded from bio in D5 to content profile in D6.

New users are able to create a content profile node, but the data in each of the custom fields is not stored. After editing and saving a content profile node there is still no data stored. As an admin editing values in the fields, or as a normal authenticated user entering values, or as an admin editing other content profile fields, nothing stores on submission of the node.

I've followed all of thinks above, all lead to points where someone thought that the issue had been resolved. It has not been resolved for me.

Any clues?

seaneffel’s picture

seaneffel commented
Status: Active » Closed (duplicate)

The issue is not with Content Profile, but actually with the Link module preventing data from being stored in CCK fields.

Marking this as a duplicate of this:

http://drupal.org/node/337182

kenorb’s picture

kenorb commented

It's not true, I've no Link module and this problem appears.

monan’s picture

monan commented

I have the link module and I see this behavior as well. I turn off the link module and this bug no longer manifests. If I get a chance, I'll try to track down what's going on: in xdebug it looks like all the associated CCK fields in $node (on node_save) are set with the error handler, but it looks malformed. I looked for an associated link issue in the link queue, but had no luck. Does anyone know the location of this issue on the link module side of things?