Opened 17 years ago
Closed 17 years ago
#1026 closed defect (bug) (fixed)
Inconsistence between param name in xprofile_insert_field() and BP_XProfile_Field attribute
| Reported by: | luka.bernardi | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | 1.1 |
| Component: | Version: | ||
| Severity: | Keywords: | ||
| Cc: |
Description
xprofile_insert_field() expect an assoc array, one of this key is field_group_id and is mapped in BP_XProfile_Field with
$field->field_group_id = $field_group_id;
but field_group_id isn't an BP_XProfile_Field's attribute nor a column in wp-bp-xprofile-field table.
Instead of field_group_id use group_id
Change History (5)
#3
@
17 years ago
- Resolution fixed
- Status closed → reopened
Can I suggest to accept group_id as a key of the array,otherwise the naming conventions could become inconsistent?
#5
@
17 years ago
- Resolution → fixed
- Status reopened → closed
Actually, I'm not sure exactly what you mean looking at it now. The member var in the field class is group_id, and so is the field in the DB. I don't really want to change that. Everyone will be interfacing with the class through the xprofile_insert_field() function, so it shouldn't matter a great deal.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
(In [1898]) Fixes #1026 props luka.bernardi