XProfile superfield

[sooskriszta]

It would be good to have a replicable capsule of a superfield.

e.g. If like popular social networks, a BuddyPress-powered community wants its members to provide details of education or employment, they should be able to create a set of fields (e.g. from date, to date, employer name, job title) that the members can replicate over and over (say by clicking a button "add another job") if they need/want to to provide their education/employment history.

[imath]

imho, if the only use case is using the profile fields as a resume, then a BuddyPress plugin might be a better solution than modifying core.

[boonebgorges]

I think the suggestion here can be broken out into three items:

1. that BP support "multiplying" profile fields, those where you hit a little + to add another text field. So, for example, you could enter as many 'Favorite Colors' as you like.
2. that BP support grouped fields
3. that BP support groupied fields that are "multiplying"

I think 1 is definitely something we can look into. Let's look at how some form builder plugins do it for inspiration.

I'm not opposed to 2, but it's harder to envision how the UX would work. Again, form building plugins might be a good place to look.

If we can do 1 and 2, then 3 should follow pretty easily. 1 and 2 are the hard parts.

[sooskriszta]

Updated

[johnjamesjacoby]

I like the ideas proposed here.

Because of the way XProfile field data is currently stored, I'm not highly confident how exactly we would store the information for user-definable multi-fields. Maybe in bp_xprofile_meta linking the field_id to an object_id & object_type with a meta_key that helps identify each sub-field and its value? The problem with this approach is those values not appearing in search results unless we somehow combine them into bp_xprofile_data's value column.

I agree with Boone's assessment that once we are satisfied with where to store the data and how to introduce the UI elements (both in wp-admin and in bp-legacy) that everything kinda would/should/could fall into place pretty quickly.

[boonebgorges]

Related: #6789. If we started storing things like checkbox and multiselect fields in separate rows in wp_bp_xprofile_data, we could use the same technique here.

[DJPaul]

We're closing this ticket because it has not received any contribution or comments for at least two years. We have decided that it is better to close tickets that are good ideas, which have not gotten (or are unlikely to get) contributions, rather than keep things open indefinitely. This will help us share a more realistic roadmap for BuddyPress with you.

Everyone very much appreciates the time and effort that you spent sharing your idea with us. On behalf of the entire BuddyPress team, thank you.

If you feel strongly that this enhancement should still be added to BuddyPress, and you are able to contribute effort towards it, we encourage you to re-open the ticket, or start a discussion about it in our Slack channel. Please consider that time has proven that good ideas without contributions do not get built.

For more information, see ​https://bpdevel.wordpress.com/2018/01/21/our-awaiting-contributions-milestone-contains/
or find us on Slack, in the #buddypress channel: ​https://make.wordpress.org/chat/

[sooskriszta]

Perhaps deserves another look, now that xprofile fields have been reworked?

[imath]

I agree it's inspiring.

I believe we could start by making it easier to do Superfield-Frontend-Replicable-Example-2.png and what about conditional fields ?

[imath]

We need more time to progress on this.