Skip to:

Opened 14 years ago

Closed 6 years ago

#1842 closed enhancement (maybelater)

Just the first Profile Field Group required for signup (but other fields set as "required" too)

Reported by: wemaflo's profile wemaflo Owned by: johnjamesjacoby's profile johnjamesjacoby
Milestone: Priority: minor
Severity: normal Version:
Component: Extended Profile Keywords: ux-feedback, trac-tidy-2018


On the registration page only the first field group is displayed. Even if other profile fields in other field groups are marked as "required" too, they are not required for registration progress.

I think that should be fixed so that all fields marked as "required" are required at signup.

Change History (7)

#1 @johnjamesjacoby
14 years ago

  • Keywords xprofile added
  • Milestone changed from 1.2 to 1.3
  • Owner set to johnjamesjacoby
  • Priority changed from major to minor
  • Status changed from new to assigned

This will be addressed in a future version.

#2 @DJPaul
13 years ago

  • Component set to Core
  • Milestone changed from 1.3 to Awaiting Review

I disagree as moving all of the required profile fields to the registration page will take those non-first group fields out of context; the field descriptions could make no sense. We probably won't have time to try this for 1.3, so I'm changing to 'awaiting review' so we can look at it for a future release.

#3 @DJPaul
13 years ago

  • Milestone changed from Awaiting Review to Future Release

#4 @boonebgorges
10 years ago

  • Component changed from Core to XProfile
  • Keywords ux-feedback added; xprofile removed
  • Severity set to normal

IMO it's weird that we only put 'Base' fields on the registration page. Seems to me that the proper fix is just to show all groups during registration.

#5 @johnjamesjacoby
10 years ago

Let's fix this by adding a checkbox in the field UI to choose which fields appear during sign-up. I've wanted this since the olden days but it's never been prioritized.

#6 @DJPaul
6 years ago

  • Keywords trac-tidy-2018 added

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
or find us on Slack, in the #buddypress channel:

#7 @DJPaul
6 years ago

  • Milestone Awaiting Contributions deleted
  • Resolution set to maybelater
  • Status changed from assigned to closed
Note: See TracTickets for help on using tickets.