[buddypress-trac] [BuddyPress Trac] #5799: Bring profile fields back into template parts

buddypress-trac noreply at wordpress.org
Fri Oct 31 12:47:28 UTC 2014


#5799: Bring profile fields back into template parts
-----------------------------+------------------------------
 Reporter:  johnjamesjacoby  |       Owner:
     Type:  enhancement      |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  XProfile         |     Version:  2.0
 Severity:  normal           |  Resolution:
 Keywords:  needs-patch      |
-----------------------------+------------------------------
Changes (by boonebgorges):

 * keywords:  2nd-opinion => needs-patch


Comment:

 johnjamesjacoby discussed this in a bit more detail at WCSF. I think the
 conclusion we reached (John, feel free to correct me if I'm wrong) is
 that:

 (a) we should definitely allow plugin/theme authors to provide a template
 that will override the logic in `edit_field_html()` if found. This is my
 first bullet point here:
 https://buddypress.trac.wordpress.org/ticket/5799#comment:3
 (b) In order to make (a) work, it may be necessary to build some new
 procedural wrappers so that template files will have access to the
 required data in the global namespace
 (c) Depending on how clean all of the above is, we could consider moving
 the markup building logic itself into template parts that would actually
 be bundled with the theme (something like `members/single/profile/edit-
 fields/textbox.php` etc).

 I think we should go ahead with (a) and (b) for now, and maybe wait a
 version to see if this is enough to cover the relative edge case of
 wanting to override these templates. If so, we'll leave it at that.
 Otherwise, we can do something like (c) in a future release.

--
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/5799#comment:7>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac


More information about the buddypress-trac mailing list