Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
The user's profile data fields are not updated after you update the profile itself. So the cck fields get updated but the 'data' field in {users} table doesn't get updated.
I made a (ugly) patch for this. I'm not sure it is complete.
Comment | File | Size | Author |
---|---|---|---|
profile_fields_not_updated.patch | 946 bytes | andreiashu |
Comments
Comment #1
andreiashu CreditAttribution: andreiashu commentedI forgot to ask: why do we need to keep a copy of the profile's cck fields in the user's data field ?
It is 5 AM here so sorry if I asked a dumb question.
Comment #2
fagothere should be no such copy.. if it is, it's a bug. Probably caused by the hook_user integration.
Comment #3
fagoProbably this is fixed with the fix of this issue: http://drupal.org/node/332998#comment-1123924
So please test the next generated development snapshot and make sure to have your menu cache cleared when testing, e.g. hit submit at the admin modules page after updating the module.
Comment #4
igorik CreditAttribution: igorik commentedI have to reopen it, the problem persists.
It is weird that the problem is with new profile nodes only.
The fields in exists profile nodes (in my case it names uprofile) are changed and storered correctly, doesn't matter if user is admin or basic user.
But nothing is stored in new created node profiles (after this module enabled).
It is weird that there is a register button ABOVE node profile inside register page. It looks as node profile it is not correctly loaded...? just an idea. I thought that that it was on end of the page before, but maybe I am wrong.
I tried the patch above but it doesn't help me.
I am using new generation dev version from today(or yesterday)
Igorik
http://www.somvprahe.sk
Comment #5
igorik CreditAttribution: igorik commentedI found the problem is with all profile nodes created by content_profile.
I am using it last 4 days (testing) and I found that on these nodes no field is stored or updated.
before that I used drupal 5 and I did upgrade to drupal 6 a few days ago.
all fields from profile nodes from drupal 5 (created by node profile) are correctly updated and stored.
but nothing is stored when using content profile on new nodes created by content profile. Using conten profile for update fields on nodes created by node profile from drupal 5 works fine.
Igorik
Comment #6
fagohum? What's the issue here? *confused*
Please report clearly what you edit where exactly, and where exactly it works and where not. Is profile module involved in here? Registration integration?
Comment #7
igorik CreditAttribution: igorik commentedHi
the issue: profile fields are not updated/stored
What I found later
this bug shows only on profile nodes created from starting using content_profile.
When I edit profile fields (using content_profile) on profiles created before I start using content_profile, these fields are updated correctly.
Sorry for my english. Please let me know if it is more clear now.
Thanks
Igorik
http://www.somvprahe.sk
Comment #8
fagoWhich profile fields? content profile or core profile module profile?
>When I edit profile fields (using content_profile) on profiles created before I start using content_profile, these fields are updated correctly.
Are these profiles nodes?
Are you using the latest development snapshot?
Comment #9
igorik CreditAttribution: igorik commentedcontent profile fields.
Yes, I am using the latest new generation dev. snapshot.
Comment #10
fagoThen what profiles are those?
>When I edit profile fields (using content_profile) on profiles created before I start using content_profile, these fields are updated correctly.
Does editing at node/XX/edit work?
Be sure to use the snapshot from 2008-Nov-25.
Comment #11
igorik CreditAttribution: igorik commentedI am Sorry, I was wrong. It was CCK Link issue that no fields were stored.
I am closing this by mistake reopened bug
Igor
Comment #12
seaneffel CreditAttribution: seaneffel commentedCan you point me to the Link module issue that you found? I'm experiencing the same problem.
Comment #13
kenorb CreditAttribution: kenorb commentedThe same problem with latest content profile.
If there is solution, please provide any issue that solve that problem.
I've got CCK: 6.x-2.2
upgraded to CCK 6.x-2.5, the same problem
Created related Drupal support issue: #337182: Profile fields not updated in user data
Comment #14
kenorb CreditAttribution: kenorb commentedComment #15
kenorb CreditAttribution: kenorb commentedTested with updating userreference field and it's working fine
+1 for that patch
Environment:
Simple by going to: user/82/edit/parent (from admin where parent is the name of content profile)
and editing any cck field (tested with userreference), and basically without this patch it's not refreshing user->data
Comment #16
fagoThe issues bug is "Profile fields not updated in user data" which is as it should be, as I already state in #2. The bug was, that it happened previously. This is fixed now.
So again: There should be no content profile data in user->data, if it is, it's not intended and thus a bug.