Skip to:
Content

BuddyPress.org

Changes between Version 1 and Version 2 of Ticket #7665, comment 11


Ignore:
Timestamp:
01/25/2018 10:45:53 AM (4 years ago)
Author:
hnla
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #7665, comment 11

    v1 v2  
    11<digressing-rambling> However an issue I have always had with these edit fields is the manner in which they have been separated into class functions so changes need to be made across multiple files, then when it comes to  working in the template as we loop things I have access to only one instance of `$field_type->edit_field_html( array( 'show_label' => true ) );` so have a problem identifying what field I want to target. It has always felt like xprofile was written for the convenience of the backend not frontend.
     2
     3Edit: // just re-factored the  datebox class method to take an additional param and changed the hardcoded 'screen-reader-text' class to a var, this at least now allows me the option in the template to turn on/off, that's one class though, the problem remains that I would need to re-factor all class functions to accept same param thus all profile fields would be shown/hidden without being able to be selective.