[buddypress-trac] [BuddyPress Trac] #6783: Groups: Add Profile Fields and Profile Field Groups

[buddypress-trac]

#6783: Groups: Add Profile Fields and Profile Field Groups
--------------------------+-----------------------
 Reporter:  mercime       |       Owner:
     Type:  enhancement   |      Status:  reopened
 Priority:  normal        |   Milestone:  3.0
Component:  Groups        |     Version:
 Severity:  normal        |  Resolution:
 Keywords:  dev-feedback  |
--------------------------+-----------------------
Changes (by DJPaul):

 * keywords:  2nd-opinion => dev-feedback


Comment:

 I've been thinking about this idea this afternoon, and I'm pretty excited
 by it. I think if we can get some agreement on the DB schema changes, we
 can get *some* progress made on that and any API changes into 3.0, and
 target a subsequent release for UI/template changes (into Nouveau only, of
 course).

 I quite like how successful the XProfile tables schema has been (compared
 to say, the Activity tables schema), so I don't think we need to migrate
 all of this into a brand new table.

 I've looked at the current DB schema and attached example-1.jpg of
 proposed changes, which are:

 1) Rename `wp_bp_xprofile_data.user_id` to `object_id`.
 2) Add column `wp_bp_xprofile_data.object_type`. All existing records
 would be set to a value, e.g. "xprofile".
 3) Add column `wp_bp_xprofile_groups.group_type`. All existing records
 would be set to a value, e.g. "xprofile".

 1) is for clarity. 2) is to distinguish between User IDs and Group IDs. 3)
 is to distinguish group types.
 Indexes etc would also be set appropriately, I haven't included that on
 the graphic.

 This doesn't seem *too* complicated. Next work would be to amend the basic
 set/fetch methods to support a new "object type" (etc) parameter, then
 upgrade routines to update the schema, and then put all of that into 3.0.

 Thoughts?

--
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/6783#comment:17>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac