#7425 closed defect (bug) (fixed)
XProfile: use filterable field input name in radio/checkbox field type
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | 2.8 | Priority: | normal |
Severity: | normal | Version: | |
Component: | Extended Profile | Keywords: | |
Cc: | lmoffereins@… |
Description
Perhaps there is a good reason, but currently the radio
and checkbox
profile fields do not use the filterable bp_get_the_profile_field_input_name()
for their input options name
attribute. Using this template tag requires the $field
global variable, but the docblock of the edit_field_options_html()
field type method requires its usage within the profile template, so that should be covered:
Must be used inside the {@link bp_profile_fields()} template loop.
Since the replacement of the current $field_id
value is equivalent to that of the template tag, no obvious damage will be done. The benefit of template parity and filter options with other field types is evident. Are there any objections to this fix?
Your patch removes the
[]
that gets PHP's$_POST
handling to parse into an array. :)