WordPress.org

Ready to get started?Download WordPress

Ideas

Custom user meta

  1. Stacy (non coder)
    Member

    It's shown when they joined, the site's they are on and ect, how about notes per user and ability to search by these notes.

    Posted: 2 years ago #
  2. WordPress already allows you to create custom user meta. Can you elaborate on your idea a bit?

    Posted: 2 years ago #
  3. joevansteen
    Member

    12345

    I would suggest a review of this BuddyPress TRAC item and my blog post that is referenced in the comment. I think the BuddyPress user profile facility should be moved into WP as an enhanced user profile CORE feature. That would provide an enhanced facility for user profile data management using field groups, etc. The user profile features by themselves should not make WP dependent on BP, but should enhance the WP experience. These are supposed to be 2 sibling systems that work together, aren't they? I see cleaner interfaces, better data integrity, and possibly some slight performance improvements and cleaner code. It should be a win-win.

    Posted: 2 years ago #
  4. Ipstenu (Mika Epstein)
    Half-Elf Support Rogue & Mod

    joevansteen - It's probably not going to come into Core as it's more than needed (if anything, the plan is to REMOVE profile stuff from WordPress - like AIM and all that junk).

    Posted: 2 years ago #
  5. joevansteen
    Member

    12345

    Ipstenu - is there a 'direction statement' to that effect written down anywhere that people could refer to when trying to plan? Along that line, if profile is to be removed, just how stripped down a 'user concept' is planned and where is it assumed that 'profile' would go? Is it assumed that an independent profile add-on facility would be created by someone in the community, or just that it isn't needed? Is there a group or other forum where these discussions take place on a more formal basis (i.e., a group whose intent and purpose is to do formal planning on this and/or other core topics) with recognized players?

    Posted: 2 years ago #
  6. Ipstenu (Mika Epstein)
    Half-Elf Support Rogue & Mod

    It's listed in trac (which I meant to link! My bad)

    http://core.trac.wordpress.org/ticket/11541

    The concept is if you want it, you can add it (it's plugable), but it's going to be removed from core.

    THIS is the right place to post that idea, however. And the official answer is "We're going the other way." So if you wanted to make a plugin, that's sort of ad-hoc. You can see if someone else did, or wants to with you, but it's left to the community at large, which is wildly informal. There is a formal Core team, if that's what you're asking, though.

    Posted: 2 years ago #
  7. joevansteen
    Member

    12345

    Thanks! I appreciate the link. From what I read in the TRAC post, it is talking about getting rid of specific fields in profile keyed to specific uses. The concept I was advocating was NOT along that path. It was to enhance the metadata capability along the lines of what BuddyPress offers to be able to group metadata fields, to offer dropdown offerings, etc. but all of that is 'as defined by the site admin' - not using specific data tied to any specific profile content.

    So, I would pose the question, is that in the desired direction for core features, or is that still something that is best offered by an add-on module. Because if it's an add-on, my question would be - do you plan on getting rid of usermeta? Because, in essence, my proposal is to enhance usermeta to be able to define groups and dropdown selections sets, etc. so there is better data quality associated with the feature.

    Posted: 2 years ago #
  8. Ipstenu (Mika Epstein)
    Half-Elf Support Rogue & Mod

    Which would still be a plugin thing and not a core functionality, since we're getting rid of custom profile tweaks, is what I'm saying :) Decisions, not options. In stall a plugin for it, if you want it.

    UserMeta has other information (like user permissions, full name, things that WordPress out and out requires for functionality), so you're safe to use that and expand on that for your plugin (which you keep calling an 'add-on' we call 'plugin' ;) )

    Posted: 2 years ago #

RSS feed for this topic

Reply

You must log in to post.

  • Rating

    12345
    4 Votes
  • Status

    This idea is under consideration