#3698 closed enhancement (fixed)
Required Profile Fields in BP 1.5+ no longer give an option for a null value in the drop down, but become pre filled with the first option.
Reported by: | rossagrant | Owned by: | Ross Grant |
---|---|---|---|
Milestone: | 1.6 | Priority: | normal |
Severity: | minor | Version: | 1.5 |
Component: | Core | Keywords: | needs-patch |
Cc: |
Description
Required profile field behaviour has changed in BP 1.5
When a user is selecting an option from the drop down menu on a registration page the required fields are pre filled with the first option in the dropdown.
This means that incorrect data can be saved if a person overlooks a field and it also hinders other plugins that use this core functionality, such as BP Profile Search.
There used to be an option above each list of potential answers that showed as ---------
Thus there was a null option.
I have created this screencast to explain this a little easier:
Boone suggested this solution but I am not a coder:
I would be happy to see a patch for BP that allows bp_get_the_profile_field_options() to take an argument along the lines of show_null_value_for_required (maybe not that wordy, but you get the idea). That way, we could default to false (1.5 behavior) but allow the 1.2.x behavior optionally, at http://buddypress.trac.wordpress.org/browser/trunk/bp-xprofile/bp-xprofile-template.php?annotate=blame&rev=5230#L431.
I will try to get around to this, but it's puntable if no one manages to squeeze it in.