Skip to:
Content
Pages
Categories
Search
Top
Bottom

WP profile fields not editable in BP profile

  • Avatar of Azinfiro
    Azinfiro
    Participant

    @azinfiro

    Parts of the WordPress/BuddyPress profile relationship has been covered elsewhere, but I haven’t been able to find a conclusive discussion on the subject, so I’m taking the liberty of bringing it up again.

    First, we have the WordPress profile with the usual such as email address, names, password, bio, along with the dashboard preferences.

    Then there’s the bbPress profile with its own forum-oriented tabs, however, it still preserves access to almost all the settings in the WordPress profile, except of course for the dashboard preferences that are no longer relevant in the front-end.

    Finally, there is BuddyPress, where only the account email and password are editable. Names, contact info, and the biographical info are not included. There are, however, the Extended Profile’s custom fields, but they do not substitute the above fields.

    I think a few things here need clarification (I have linked to existing relevant discussions):

    • What’s behind the decision to not include these settings in the BuddyPress profile?
    • Why aren’t the bbPress and the BuddyPress profiles merged? #4357
    • Why aren’t the BuddyPress and the WordPress profiles merged? #3335
    • In addition to above, If bbPress at least to an extent is merging its profiles with the WordPress profile, why is BuddyPress not doing the same?
    • Finally, can anybody explain, based on editing template files, how to add these settings, the same settings that WordPress offers at wp-admin/profile.php and bbPress offers in their profile, under the BuddyPress profile’s settings?

    Thank you.

    Additional reading:

    http://buddypress.org/support/topic/please-help-me-understand-a-wordpressbp-feature/

    http://architectedfutures.info/2011/08/23/bp-wp-profile-sync/

Viewing 6 replies - 1 through 6 (of 6 total)
  • Avatar of adamt19
    adamt19
    Participant

    @adamt19

    Thanks. Agree that it seems important to offer a single account-management area for users, who won’t care about the separation between WP/BP.

    In my case, we also don’t want to allow users to access the (unbranded) WP admin back end, which I believe is necessary until a more “front end” experience is available for managing all of these settings

    Avatar of r-a-y
    r-a-y
    Moderator

    @r-a-y

    #4357 – I agree that something needs to be done. bbPress already adds a “Forums” section on a BP profile, so perhaps bbPress can simply redirect /forums/users/USERNAME/ to BP’s /members/USERNAME/forums. I would say this is more a bbPress issue than a BuddyPress one. Please add a ticket to bbPress Trac about this. (Use the same credentials you use on buddypress.org to create a new ticket.)

    #3335 already has comments on it regarding why WP’s profile is not included with BuddyPress. I do find it odd that bbPress allows users to edit WordPress’ user profile though… I’ve created a new ticket with some further thoughts – #5619

    Avatar of Azinfiro
    Azinfiro
    Participant

    @azinfiro

    Thank you for creating #5619, I’m gonna be glued to that ticket.

    #3335 already has comments on it regarding why WP’s profile is not included with BuddyPress.

    Sorry if I’m missing something, but all I can find are comments about a two-way sync where the issue is moving BuddyPress feature support upstream to the WordPress profile; I can’t find any arguments for not including the WordPress profile in BuddyPress.

    About #4357, most bbPress profile pages already redirect to BuddyPress when it’s installed. Do you know if it’s bbPress or BuddyPress that’s doing the current overrides?

    Avatar of Boone Gorges
    Boone Gorges
    Keymaster

    @boonebgorges

    > I can’t find any arguments for not including the WordPress profile in BuddyPress.

    The arguments are:

    - The fields at wp-admin/profile.php are hardcoded in WP. There’s no way we can ask WP which fields it provides in a programmatic way; we’d have to hardcode them as well. This is inelegant; it causes problems when other plugins add their own (hardcoded) fields, which BP won’t know about; and it will require keeping up with WP if they decide to switch which fields are included on that page.
    - The fields at wp-admin/profile.php are very odd, and not appropriate for most BuddyPress installations (or most websites that were built after 2004 – who uses AIM, and who among them would want to store that information in their WP profile?)

    As noted in the ticket, First Name and Last Name are the two possible exceptions I see here.

    Avatar of Azinfiro
    Azinfiro
    Participant

    @azinfiro

    I think I need to clarify that it’s the not being able to configure the WordPress profile in BuddyPress that I think is the issue. Displaying the fields is another side of it that I might agree should be left to a plugin developer.

    …it will require keeping up with WP if they decide to switch which fields are included on that page.

    I agree that this is an issue, but realistically, the WordPress profile hasn’t been updated in several years, apart from very recently when they actually removed fields in an effort to simplify it, so I doubt they intend to add anything to it either.

    The fields at wp-admin/profile.php are very odd, and not appropriate for most BuddyPress installations…

    As I mentioned above, those fields (AIM, Jabber and Yahoo/gTalk) were recently removed.

    As noted in the ticket, First Name and Last Name are the two possible exceptions I see here.

    That just leaves display name selection, nickname and website; email and password are configurable in BuddyPress and you already display username and bio on the profile when Extended Profiles are disabled. Why not allow the user to edit them too and add the remaining three fields? This would effectively move the profile to the front-end and nobody would need to configure their profile in two places again, which I think is the underlying issue here.

    …it causes problems when other plugins add their own (hardcoded) fields, which BP won’t know about

    I’m getting into deep water, but wouldn’t adding a hook before and/or after the fields be sufficient to deal with that?

    Avatar of Azinfiro
    Azinfiro
    Participant

    @azinfiro

    Does anyone else have anything to add?

Viewing 6 replies - 1 through 6 (of 6 total)

You must be logged in to reply to this topic.