Skip to:
Content

BuddyPress.org

Opened 13 years ago

Closed 12 years ago

#671 closed enhancement (worksforme)

Extended Profile Field Meta

Reported by: johnjamesjacoby's profile johnjamesjacoby Owned by: johnjamesjacoby's profile johnjamesjacoby
Milestone: 1.5 Priority: major
Severity: Version:
Component: Extended Profile Keywords: extended, profile, fields, meta
Cc:

Description

I think it would be great if the extended profile fields each had a meta associated with them in a separate table.

This would open up the ability for each specific field to have unlimited properties.

Say field ID=1 is the default textbox, and you've elected to call it "Real Name".

Real Name should include at least one space, and have min length of 5 chars.

This would include some default templates for specific field types, with room to create your own custom field type and template.

Because it's meta, it opens the door for plugins to come in and control specific fields also.

Attachments (1)

671.1.patch (6.5 KB) - added by boonebgorges 12 years ago.

Download all attachments as: .zip

Change History (11)

#1 @burtadsit
13 years ago

I second this motion.

#2 @windhamdavid
13 years ago

i third this motion.

#3 @(none)
13 years ago

  • Milestone Extended Profiles 1.1 deleted

Milestone Extended Profiles 1.1 deleted

#4 @cnorris23
12 years ago

  • Component set to XProfile
  • Milestone set to 1.3

#5 @boonebgorges
12 years ago

jjj - I wrote this patch as a special gift to you. Others: Please please please test.

@boonebgorges
12 years ago

#6 @boonebgorges
12 years ago

  • Resolution set to fixed
  • Status changed from new to closed

(In [3346]) Adds meta functions for xprofile field groups, fields, and individual data items. Fixes #671

#7 @r-a-y
12 years ago

  • Resolution fixed deleted
  • Status changed from closed to reopened

Might need to break xprofile group and xprofile field meta into separate tables if we are thinking about using WP's meta functions for BP 1.4.

Also to keep within WP meta conventions, should rename the "id" column to "meta_id".

#8 @boonebgorges
12 years ago

Re: separate tables. I'd like to avoid creating separate tables as much as possible. The current setup mirrors the way that bbPress handles metadata, which I happen to like :) In any case, migrating to WP's meta functions in 1.4 is no easier with a separate table. For the upgrade script, there'll just have to be a check for object_type.

Re: naming conventions. Other BP meta tables use 'id' as the primary key (see http://trac.buddypress.org/browser/trunk/bp-core/admin/bp-core-schema.php?rev=3346). I'd prefer to remain internally consistent rather than conform to WP. What do you think?

#9 @r-a-y
12 years ago

bbPress has some good ideas. I like it as well. Especially the global meta table.

But, it looks like we're going to take advantage of WP's internal functions as much as possible going forward. Just something to think about.

Re: naming conventions - you're right about that. Might want to consult with the other guys about naming conventions - BP vs WP.

#10 @johnjamesjacoby
12 years ago

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

I like it good enough as a first pass. Going to close this as the enhancement is in trunk now. Discussion can continue here if needed.

Note: See TracTickets for help on using tickets.