Opened 3 years ago
Closed 3 months ago
#12833 closed feature request (wontfix)
Custom User Fields
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Users | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | ian.gordon@… |
Description
This would be a change to wp_usermeta, which would allow custom fields to be added via the Admin Panel (just like in posts or pages) to allow administrators to request more information from registering users.
For example (i.e. phone #, city, state, zip code, etc)
Change History (10)
You can do it already, see Adding and using custom user profile fields and HOWTO: Custom Registration Fields.
Wontfix?
As of 2.8 it's easier than that for contact fields:
add_filter( 'user_contactmethods', 'my_user_contactmethods' );
function my_user_contactmethods( $methods ) {
// $methods is by default an array of aim, jabber, etc.
return array_merge( $methods, array( 'twitter' => 'Twitter', 'facebook' => 'Facebook', 'phone' => 'Phone', 'address' => 'Zip Code' ) );
}
The whole point is built in functionality. If I am the average WP user, I don't mess with the code outside of editing some HTML to add my logo. I am saying that without resorting to a plugin or a functions.php file that could be deleted or change with new WP versions. I would like to see it added as part of the "Users" menu in the Admin panel like with posts.
Plus the functionality I was talking about was to made the fields available when a new user registers as part of the default user meta information you take from them.
As part of the registration process, that's plugin material in my book.
As part of the profile screen, we could probably add more hooks and better handling for non-usercontactmethod fields if they don't already exist. Beyond that, user contact methods management would make an excellent plugin.
There's been talk to pull the three existing ones out of core if there was a viable (core?) plugin replacement. See #11541.
@nacin - I am not saying add the fields as default. I am saying add the hooks so if you wanted to customize the registration process it would be easier than hacking a core .php file which could change when you upgrade.
Essentially, I am trying to rely less on plugins and more on hooks and filters so you can have a more consistent functionality across the board. While agree a plugin fits the bill, you often have to rely on the will of a developer who would have to continually maintain the plugin and update as the hooks and filters changed and such.
We have a lot of out-dated plugins that are no longer supported by their authors.
A core hook and filter solutions would be better and more consistent across multiple WP releases in the future.
We have a lot of out-dated plugins that are no longer supported by their authors.
By that logic, everything should be a core plugin. Unfortunately, it's not possible.
A core hook and filter solutions would be better and more consistent across multiple WP releases in the future.
To clarify, a hook is an action or filter that a plugin (or theme) can use to extend WordPress.
comment:9
SergeyBiryukov — 3 months ago
#23441 was marked as a duplicate.
comment:10
SergeyBiryukov — 3 months ago
- Keywords user profile removed
- Milestone Future Release deleted
- Resolution set to wontfix
- Status changed from new to closed
No traction in 3 years, sounds like plugin material to me. Relevant plugins:

We are already in beta for 3.0, and no feature requests are permitted. Changing the milestone to Future Release, to be reviewed by the developers when we begin planning 3.1.