By yasheshb on
Hello:
I'm using drupal 5.1 and have enabled the profile module. I've also create a new profile category "Name" with 2 single line text fields "First Name" and "Last Name".
Now i logged in as admin (uid 1) and created a user with the following details
uid - user1
pwd -
...
...
Name
First Name - fname1
Last Name - lname1
Now when i submit the user create form
It enters the new user details into the table "users" but the values of the profile fields dont get inserted into the table "profile_values".
Could i be doing something wrong here ? Any admin settings that i missed ? Or is this standard behaviour ?
Thanks.
Yashesh Bhatia.
Comments
{users} data field
Profile module can be a bit of a mess. Some fields are stored in the "data" column of the {users} table. Check there too. I think it depends on how the field is set.
Try changing it to:
"Public field, content shown on profile page and on member list pages."
---
Work: BioRAFT
create operation flaky.. edit operation works fine.
thanks pwolanin. just checked that the data for profile fields is either stored in the profile_value table or in the "data" field. i also checked the settings for the fileds and changed the settings from "Public field, content shown on profile page but not used on member list pages" to "Public field, content shown on profile page and on member list pages" and created a new user on
http://www.mysite.com/admin/user/user/create
but it did not store the values in the profile_value tables but i do see the data in the "data" column of the "users" table.
another interesting point to note is that when i edit the profile for same user i created above
"http://www.mysite.com/user/17/edit?destination=admin%2Fuser%2Fuser
the first name, last name information is now moved from the "data" field in the "users" table to the profile_values table.
so to summarise.. when a new user creates an account and enters the profile data it's stored in the users table but when the user edits the profile fields they get moved to the profile_values table.
this looks like a bug to me rather than standard behaviour. thx for your help. appreciate it.
yashesh bhatia.
Yashesh Bhatia
I believe this is the
I believe this is the problem described here:
http://drupal.org/node/119114