I have a site where multiple content profile node types are assigned to a single user (one for contact information, one for an extended profile, one for member-specific info, etc.). Real Name is enabled based on fname, lname fields in the contact information type. If after entering contact information the user then tries to create a different profile node (for example, to fill out member-specific information), the save of the second node is blocked with an error of the form "Username [realname] does not exist." Looks like CP is using the real name to try to generate the reference to user rather than the username (?)

Comments

bobgeier’s picture

Poking around in this a bit further...

The issue seems to be that when calling up a form for a new content profile node, Real Name replaces the authoring field username with the realname. This does not happen for the CP node type from which Real Name draws its fields, only for other node types being used as additional profiles for a user.

clarkburbidge’s picture

I am having a similar problem. If I erase the "Real Name" and opt for the "Leave blank for Anonymous." option it works. This is not how I want my users to have to deal with this. Any fix here or will we need to work with the "Authoring Information" folks?

bobgeier’s picture

Version: 6.x-1.1-rc3 » 6.x-1.1
Status: Active » Fixed

Just found a previous thread with a different title. This looks like it's fixed in the February 09 -dev release. I just tried that and it worked for me. Except now the title and breadcrumb path at mysite.com/user/# are displaying as raw username and not real name.

Fix one, break another. Sometimes code patching is just no fun.

nancydru’s picture

Okay, can we open that as a new issue, please? I know, strange as it may sound, that the User module is bad about not using its own theme('username',... function.

nancydru’s picture

Status: Fixed » Closed (fixed)

Cleaning up the issue queue.