WordPress.org

Make WordPress Core

Opened 12 years ago

Closed 12 years ago

Last modified 12 years ago

#10209 closed feature request (wontfix)

user - additional fields / removing unnecessary fields

Reported by: F J Kaiser Owned by:
Milestone: Priority: low
Severity: normal Version: 2.7.1
Component: Users Keywords: user, additional, field, extra, data, unnecessary
Focuses: Cc:

Description

Diskussion:


When you look at wordpress there´s a strong focus on articels, users and comments. But what i still miss is adding addional data or removing unnecassary data.

What i´d like to see:
1) removing and/or renaming all those im-fields
2) adding additional fields with custom labels for extra data
3) a function where i can call the custom data

There are 2 or 3 PlugIns out there, but i´d like to see this in the core, because there´s too less support possible by only one plugin-author. Spreading this into the wp-community would bring a lot of possiblities.

Change History (10)

#1 @Denis-de-Bernardy
12 years ago

  • Milestone Unassigned deleted
  • Resolution set to invalid
  • Status changed from new to closed

There already are a post_meta and a user_meta table, and the needed functions to make use of them. There is a separate ticket that asks for a comment_meta table already.

#2 @F J Kaiser
12 years ago

I have done a lot of custom sql-queries for a project some months ago. And it´s a real pain if you want to add custom-meta-data and it´s even much more pain to get the meta-data back if you´re filtering for e.g. "everybody who´s a person" AND "goes to event xy" AND "got the age xy", etc. I´m just asking to enchance wp and the admin-UI handling and to bring it more to the top, closer to the user. Most WP-Users are not programmers and even those who are, often don´t bring the knowledge to retrieve everything they need from the db. Offering functions to display data in templates is something that makes wp that good.

#3 @Denis-de-Bernardy
12 years ago

I'm aware, but the general trend with core devs has been the following for as long as I can remember: "We put all of the custom stuff into the meta table, and leave the db tables untouched."

As you highlight in your example, one can end up needing three joins on a potentially huge meta table without any useful index to the rescue. If you really need queries like that, btw, seriously consider adding extra tables and/or columns using the dbDelta. It'll go *much* faster than anything user_meta will return.

On a separate note, don't miss the new the_author_meta() template function.

#4 follow-up: @thee17
12 years ago

just as an echo of DdB's last post, the_author_meta() was originally rooted because Jabber did not have a template tag like the_author_jabber etc. But then ended up replacing most other the_author_ tags, but the true development is that with this all you need to worry about is with a plugin add or remove the fields in admin as you can do anything including adding twitter or facebook urls or heck even be using users to admin a sports team/league cms.

#5 in reply to: ↑ 4 @F J Kaiser
12 years ago

  • Milestone set to Future Release
  • Priority changed from normal to low
  • Resolution invalid deleted
  • Status changed from closed to reopened

Replying to thee17:

(...)but the true development is that with this all you need to worry about is with a plugin add or remove the fields in admin(...)

true. but why not bringing this on one-click-base to the core, as users and usermanagement are one of the main parts of wordpress?

for that: this is a feature request. :) so, why should this ticket be invalid?

btw: i appreciate the_author_meta() as this is a step into the right direction.

#6 @Denis-de-Bernardy
12 years ago

I think that part of the problem is that nobody's understanding what you wanted. I had to think for about 10 minutes on your other ticket in order to rephrase what you wrote in a straightforward sentence, and I'm still not making any sense of this beyond that you had missed the new the_author_meta().

I'm assuming you're meaning it should be possible to add an author meta using a form like the one in posts. If so, be so kind to keep the ticket closed. That thing is cruft that has been left behind and that has yet to be eliminated. It is not possible (yet) to have multiple metas with the same keys. There is no notion of hidden user meta. And it would introduce potential security issues -- among other things, you could change your role to that of administrator, and I dare not imagine the implications for membership-related plugins.

#7 @F J Kaiser
12 years ago

Hi Denis, english is not my mother tongue and i´m no programmer. And i´m sorry if i confused you. And yes, i did miss the_authoter_meta().

Indeed, the_author_meta() makes a lot of things better, because you got only one function that can bring you every field you got or add. So 3) is solved.

What´s left are 1) and 2). Both are feature requests that would add functionality to the admin UI. Offering the ability to rename the IM-fields-labels in the UI (and DB) with for e.g. a button would be 1). Making a button at the bottom of an admin-"single user edit page" to add custom input fields would be 2). As far as i understood, the_author_meta() function could retrieve every data added there. Did i describe my feature request better now?

If you want to set it to invalid or close, just do it. I don´t know how to close a ticket.

#8 @thee17
12 years ago

  • Resolution set to wontfix
  • Status changed from reopened to closed

The reason behind what Denis-de-Bernardy said is basically you would want to set the fields by Plugin or admin settings and not a generic field as you suggest. This is the security problem behind this feature. A subscriber has access to this page for their entry, if wp_ is your database prefix as is 99% of WordPress installs and user sets the label as wp_capabilities and place a:1:{s:13:"administrator";b:1;} in the field they just made themselves an administrator.

#9 @Denis-de-Bernardy
12 years ago

  • Milestone Future Release deleted

#10 @F J Kaiser
12 years ago

ok. i now got the point. thanks for this one :)

Note: See TracTickets for help on using tickets.