search

justintadlock / content-type-standards

WordPress community-curated standards for common post types, taxonomies, and metadata.
302 stars 26 forks source link

Standard should also cover user meta #11

Closed bobbingwide closed 10 years ago

bobbingwide commented 10 years ago

There are times when it makes sense to store data in wp_usermeta. Plugins developed for managing membership, such as wp-members, and my own plugin that stores user specific data ( oik-user ) should also be able to share fields.

So the convention should cover user meta data as well as post meta data.

I have to admit that it's currently a bit of a mess.

WordPress provides some simple contact fields such as aim, jabber. WordPress SEO adds googleplus, twitter and facebook. So I used the same technique ( user_contactmethods filter) for information about other accounts: linkedin, youtube, flickr, etc.

But for other fields, telephone numbers, address and geo location, I re-used logic using serialised data; where the site wide data was originally stored in the the wp_options table.

If I use both oik-user and wp-members on the same site then the user's profile page can be quite confusing, as both plugins display address fields and phone numbers.

I'm not suggesting that the standard can help resolve this issue, just that usermeta should also be included.

justintadlock commented 10 years ago

If user meta is in the context of being used alongside custom post types, it can certainly be added to this project. Otherwise, it's outside its scope.

justintadlock commented 10 years ago

Closing since there's been no more discussion on this.

bobbingwide commented 10 years ago

What I meant was that you could add that the standard can be applied to naming user meta fields as well as post meta fields.

Note: For user meta data it's not necessary to prefix the field name with an underscore as there's no need to hide the fields from any Custom Fields meta box.