our site is set up to allow users to create accounts without email verification. we are using Content Profile module instead of Profile. the Content Profile type is included in the registration form, so people are supplying the name values used with RealName when they create their accounts. but their account aliases are created using their username, rather than their RealName value.
only after editing their account and saving it, does the alias get updated.
this also applies to changing the profile information. if i go in and change the relevant fields, the alias doesn't change. only if i then edit the user account and save it does the alias get rebuilt.
i have tried this on 1.2, 1.3 and 1.x-dev, using [realname] and [realname-link] in the Pathauto token (i don't really understand the difference between the two but thought it might matter).
is this just how it ought to be working? if so, then really this is a support request - i need to figure out how to get it to behave differently. maybe doing a user_save() call whenever the Content Profile node is updated?
(this seems similar to http://drupal.org/node/542400 though in 6.x not 5.x, if that's at all relevant...)
Comments
Comment #1
brad.bulger commentedan update: yes, explicitly putting the field values from the Content Profile node into the account of the node owner with a user_save() on insert & update to that node type does produce an alias as expected. so i guess, i'm just checking that i ought to need to be doing that.
Comment #2
liquidcms commentedi think this is the same as my issue here: #970080: realname creation is problematic
which i guess couldmore aptly be titled: "when does realname get created" as i have created an account, dumped caches, loaded user, etc... but the realname is still not created.
Comment #3
liquidcms commentedand.. doing a user_save(user_load($user->uid)) does finally create an entry in the realname table; but the value is simply the username not the realname
Comment #4
brad.bulger commentedi'm adding the field values from the profile node into the user record's 'data' field from a nodeapi function on insert and update:
that worked for us.
Comment #5
tommyk commentedAny advice on how to make this work using the core Profile module on Drupal 6?
I tried unsuccessfully modifying the code in #4 and putting it in a Rule that is triggered upon user account creation. I'm creating accounts through Feeds, if that makes a difference.
Comment #6
hass commented