Skip to:

Opened 22 months ago

Last modified 19 months ago

#7003 new defect (bug)

"Full name" field setting doesn't work on non-primary blog admin in multiblog mode

Reported by: boonebgorges Owned by:
Milestone: Future Release Priority: normal
Severity: normal Version:
Component: Core Keywords: needs-patch
Cc: espellcaste@…


Originally reported in by @rbaccaro :

I am using:
Fresh and New Install
WP 4.4.2
BP 2.5.2
Sync between WP and BP activated in all blogs
We changed the primary Xprofile field name to "Full Name", using the primary blog.
When we update the primary BP field, using the backend or frontend of a different blog in the network, the primary field is not updating the WP name, last name and display name.
But, if we try to update the field using the primary blog, the sync works fine.
Bottom line: the profile sync is not working in every blog of the network and the problem persists according to my experience.
I had to update the BP xprofile field_1 (in my case from Name to Last Name) from every blog, even if the BP settings was displaying the correct field name.

Change History (5)

#1 @boonebgorges
22 months ago

I have not verified this, but it looks like it's probably a legitimate bug with Multiblog mode. It's likely that we need to move the bp-xprofile-base-group-name and bp-xprofile-fullname-field-name settings out of the root-blog options and into the "site" options (bp_core_get_root_options()) so that it's synced across the network.

In fact, I'd say that this should be the case for a number of our options. Glancing over bp_get_default_options(), I'd say the following additional option should be moved to sitemeta:

'bb-config-location', 'bp-blogs-first-install', and possibly 'bp-deactivated-components', though I can't remember whether that's really a valid option in multiblog mode.

Let's try to clean this up for 2.6.

#2 @espellcaste
22 months ago

  • Cc espellcaste@… added

I tried to recreate the same error but I wasn't able. :(

Despite of that, I think the idea of organizing this area is worth pursuing. As WordPress is slowly working and improving the mu, I guess BuddyPress should do that same.

This ticket was mentioned in Slack in #buddypress by dcavins. View the logs.

20 months ago

#4 @DJPaul
20 months ago

  • Milestone changed from 2.6 to Future Release

#5 @DJPaul
19 months ago

  • Component changed from API to Core
Note: See TracTickets for help on using tickets.