Closed (fixed)
Project:
Drupal core
Version:
6.x-dev
Component:
user.module
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
7 Aug 2009 at 14:43 UTC
Updated:
5 Oct 2016 at 16:57 UTC
Jump to comment: Most recent
Comments
Comment #1
kenorb commentedOr module which updating some fields should unserialize and serialize those changes manually? It's quite stupid.
Comment #2
damien tournoud commented$user->data is not a cache, but a storage mechanism for modules that do not provide their own storage and use
hook_user()to manage it. I'm not sure what you mean there.Comment #3
kenorb commentedI though it's kind of cache.
In example, Content Profile integrate content type fields with user object.
If one of the field has been updated, user object is not updated. So it have to load the user, update the fields and save it again.
So that's mean that module should update this storage mechanism manually?
Like: http://drupal.org/files/issues/profile_fields_not_updated.patch
Comment #4
kenorb commentedCode to manually refresh some some custom fields into user object:
where $node->uid is the user id.
It can be use for integrating user profile. In example: content_profile module
Comment #5
kenorb commentedComment #7
pieter_duijves commentedwrite:
read:
Comment #8
pdcarto commentedI tried storing entity data (membership_entity) in the user's data property and discovered that will not work because that entity type's controller does not yet exist when the user is loaded.