Skip to:

Opened 9 years ago

Closed 8 years ago

#6072 closed enhancement (wontfix)

Rename "Extended Profiles" component to "Profile Fields".

Reported by: djpaul's profile DJPaul Owned by: djpaul's profile DJPaul
Milestone: Priority: normal
Severity: normal Version:
Component: Extended Profile Keywords:
Cc: vivek@…


The component is described in the wp-admin as "Customize your community with fully editable profile fields that allow your users to describe themselves."

I'm suggesting we rename any user-facing strings from "Extended Profiles" to "Profile Fields". We can carry on calling it XProfile internally and perhaps in any developer documentation. Inside the plugin itself, I think the full component name only appears in the Components screen (XProfile's menu item under Users is already labelled "Profile Fields"). There would be more to change in docs.

I'm suggesting we make the change because I think "Profile Fields" adds clarity to what the component actually does.

Change History (12)

#1 @boonebgorges
9 years ago

I've never been a fan of "Extended Profiles" as a name, so I'm behind this. I'm not in love with "Profile Fields" - my intuition is that we want something about "customizability" in there, but I'm having a very hard time coming up with anything non-terrible. But I do think "Profile Fields" is better than what we've got.

A note that this kind of change will require changes throughout our documentation, website, etc.

#2 @espellcaste
9 years ago

I agree guys! When I started learning about BuddyPress a few months back, the "Extended Profiles" kind of scared me. Also, "Profile Fields" is a much better name. =)

I just disagree in keeping the name in the documentation. I think we could call it XProfile internally, as everybody is aware of it, but apart from that, if the change is gonna happen, it should be changed everywhere.

#3 @boonebgorges
9 years ago

I just disagree in keeping the name in the documentation.

I think we're all in agreement here. It would probably remain "xprofile" in dev-facing documentation, simply because it's difficult to change function names, but all other documentation would change.

#4 @r-a-y
9 years ago

+1 to changing the name.

"User Profiles" might be a better name similar to how we call the groups component -- "User Groups".

#5 @DJPaul
9 years ago

  • Milestone changed from Awaiting Review to 2.3
  • Owner set to DJPaul
  • Status changed from new to assigned

Let's do this in 2.3 which will give us some time to agree the preferred name.

#6 @sooskriszta
9 years ago

Why not just "Profiles"?

P.S. "User Groups" could be changed to "Groups" as well.

#7 @sooskriszta
9 years ago

  • Cc vivek@… added

#8 @DJPaul
9 years ago

Why not just "Profiles"?

What happens if one day Groups have Profiles, as well as Members having Profiles? We'd have to rename it again.

"User Profiles" might be a better name

Ah, but if xprofile is disabled, you still get user profiles. You just don't get all the custom profile fields. /members/paul/profile/ still exists, as does /members/paul/groups, etc.

I would be happy to compromise with "User Profile Fields" instead of "Profile Fields".

@johnjamesjacoby - would appreciate your thoughts on this.

#9 @johnjamesjacoby
9 years ago

Interesting ideas here. Obviously the name comes from it extending WordPress's otherwise primitive user profiles. I'm admittedly too close to this component to have an objective opinion, but the name has never bothered me, and I guess I like it better than 'Profile Fields' juxtaposed to beefier components like Activity and Groups.

Let's not make any moves on this until we have a firm decision and sign-off from everyone. 'Site Tracking' isn't a great name either, and I think we should more clearly define the goals of each component so we can more accurately name and describe them.

#10 @DJPaul
9 years ago

  • Milestone changed from 2.3 to Under Consideration

#11 @DJPaul
8 years ago

  • Milestone changed from Under Consideration to Awaiting Review

#12 @DJPaul
8 years ago

  • Milestone Awaiting Review deleted
  • Resolution set to wontfix
  • Status changed from assigned to closed

This has had no traction so I'm closing it.

Note: See TracTickets for help on using tickets.