I couldn't agree more. I have absolutely no idea what the idea of 'display name' is. Appearantly it is not unique so it could be anything and I therefore would be surprised to see modules actually make use of it.

As for me I decided to disable firstname and lastname in the profile to accomodate a need for simplicity for my users. I'm planning on writing a small scheduled job that synchronises the first and last name of the account with the fields in the profile, but I haven't decided on that matter yet. Anyway,

I think a common good practice for DNN developers would be to refrain from using profile fields without at least noting it in their module requirements or writing some decent error handling to manage the matter. Maybe we could appeal to the DNN Core members to address this issue as it probably won't go away automagically. Though I'm not sure how to do this. Some common guideline on the matter and an RFC to remove the profile firstname and lastname and possibly the account display name.

Any core members care to comment on the matter????

I know this is not the spot, but maybe somebody *could* explain what the display name is for?