BuddyPress.org

Have you checked out Buddypress Conditional Profile Fields ?

@fazla,

this plugin may do that

Conditional Profile Fields for BuddyPress

That’s a Firebug question, but not important anyway. Also, there is no need to use all rules, as they are handled by the original CSS. You declare only the part you want to modify for .label

Open /child-theme/style.css and add only this: (#xyz123 is the color hex you want to use)

#buddypress table.profile-fields tr td.label,{
   background-color: #xyz123!important;
   color: #xyz123!important;
}

Hi,

this feature is currently handled field by field when you’re on the field creation page.
dashboard > Users > Profile Fields
Edit an existing field and see in the right column the box named Autolink. From there you can choose to enable/disable it.

For more details about the concerned fields and autolinking, read comments in bp-xprofile/bp-xprofile-filters.php:322

Hi,
have you done this ?

– create a new field
– enter Birthday as title
– give a description
– Under Type section, select date selector
– save

When you’re on a profile’s edit page, you should see
– title
– date selector (day, mounth, year)
– This field can be seen by:….
– the field description

If you highlight the whole and check his source code, you would see something like:

<fieldset class="datebox">

	<legend>Birthday</legend>

	<div class="input-options datebox-selects">		
		<label for="field_xx_day" class="bp-screen-reader-text">Select day</label>
		<select id="field_xx_day" name="field_xx_day">
			<option value="">----</option>
		<label for="field_xx_month" class="bp-screen-reader-text">Select month</label>
		<select id="field_xx_month" name="field_xx_month">
			<option value="">----</option>
		<label for="field_xx_year" class="bp-screen-reader-text">Select year</label>
		<select id="field_xx_year" name="field_xx_year">
			<option value="">----</option>
	</div>
</fieldset>

If you can read this code but don’t see it’s ouput on your theme, you have to find which CSS rule is handling the labels.

Could be a simple contrast issue or something omitted somewhere.
To get sure of this, try first with one of Twenty’s theme.

And if possible, answer the questions you already received from Paul and give some details about your install: used theme and plugins at least.

Ah, what’s the profile field type for that? Is it a date field type or a “Birthday” field type?

Are you using the https://wordpress.org/plugins/buddypress-xprofile-custom-fields-type/ plugin ?

BuddyPress will try to sync the value of a user’s “Name” field to the First and Last Name fields in their wp-admin user profile.

To disable this, go to wp-admin Settings > BuddyPress, and disable Profile Syncing.

@mugwumpman,
first and last_name fields don’t belong to BuddyPress, but to WP profiles.

BP use only a field called Name at first install. User can enter their first AND last name in that field. Is this what you’re talking about ?

After reading your topic on wp.org, it seems that you use those fields to enter datas which are not first and last names, but more for company and company activity or such.

As you use BP, i would suggest you use the power of xprofile and offer to your user a much better experience by adding a field for a company and another for company activity (or something like that). So you can forget WP’s profile fields and use BP’s xprofile fields.

WP’s profile field used when BP is activated are: username, email and password.
And BP adds his mandatory Name field, which can be first, lastname, username or whatever other unique name belonging to a subscriber (which can be a human, a pet, a company….).

And yo can as many fields you want to the registery or for later on profiles.

The other problem related to font case is a mistery so far. Can be related to many things such as plugins or theme or custom function. This can be determined by debuging and using one of WP’s default theme and all plugins deactivated.

No matter to know if you fill a wp or a bp field for this. Both use a textarea, so it’s probably more a css thing somewhere.

“WP was finding it difficult to distinguish users on our current system with users of Buddypress”

correct cause bp adds additional profile fields…xprofile fields like name for example. rest gets stored in the wp_users database.

maybe u can try setting up different subdomains…bp on community.yoursite.com and forums on forums.yoursite.com

Use this:

BuddyPress Non Editable Profile Fields

@earl_d, this “issue” is mentionned in plugin’s FAQ. Have you done the recommended changes ?

There was no change to the Extended Profiles component in BP 2.6.2.

Also i created about 11 profile groups but when i checked extended profile for my users from the admin panel i found all the created profile groups plus one more group with no content to it called “Social” which i didn’t create and i can’t even find it under Profile fields tab.

Sounds like a plugin conflict. Did you also install or upgrade some BuddyPress plugins during your BP 2.6.2 upgrade? If so, deactivate those plugins and try to replicate your issue again. Also, try a different theme like twentysixteen since some themes try to add some of their own BuddyPress customizations, which may not work properly.

You should set up a test site so that you can do a proper evaluation.

Answers:

1. The reg form will include any profile fields you place in the ‘Base’ profile group.

2. Each member has a page that includes profile editing.

3. All active members are shown on the ‘Members’ page. That page can include profile details.

@eli225, please calm down. @sharmavishal is only trying to help you !

It’s not easy trying to help people asking questions without giving much details. It’s the case with this topic and your previous. Have you even read this before asking ?

This is not possible: Buddypress Profiles Display In Wrong Order as it is not BP but the site admin who determines this.

xprofile fields and xprofile field groups (what you call section i suppose ) are drag’n’dropable.

If despite a correct positionning in the backend, the order changed on front-end, two possibilities: the drag’n’drop was to fast or there is a js error/latentency/cookie somewhere. And this is generally due to the theme in conflict with a plugin (which could be BP).

Unfortunately, kleo is a premium theme for which you can’t expect assistance here, as we have no access to it’s code.

For the part related to BuddyPress, note that the actual version works flawlesly with the xprofile component. Nobody related a similar issue to yours recently.

So back to handcrafted annoying but very related questions:
What do you call section ?
Which type of field do you use ?

Also related to general debug work:
Have you tested with another theme ?
Have you tested without any other plugin as BP ?

On a default single install, all users can access their credentials via your-site/wp-admin/profile.php

From there they have access to the WP fieldss and to the extended profil fields.

From there, they can change email & password.

Admitting you closed admin access to all users, the only other way for them to modify there email and password is to use the “forgotten your password ?” at loggin stage.

All this is not really a BP thing, but how WP is working since 2003.
The 3 mandatory field (username, email and password) belonging exclusively to WP. They are showed on registration, ASIDE BuddyPress custom fields. BP doesn’t exactly handle them, it only show them. And as these fieds are WP territory and a bit sensible, they are not accessible from within frontend profile settings.

Guess the word “critical’ is a bit exagerated. Not every user change his mail or password every day. How long do you wait for a new phone number or new electricity supply ? Probably more critical things as a mail/password change !