BuddyPress.org

I stated that the visibility for WordPress Fields are “currently” not user selectable. Why this decision was made was unknown to me, until recently, and appears to be along the same lines of why the “Requirements” metabox doesn’t appear for the WordPress Fields, as well.

Given this conversation, I looked for a possible reason that might uncover a decision to not include such capabilities and found that ticket #8487 (Add visibility and required controls to the WordPress profile fields) provides the history behind why the decision was made not to include the capabilities (visibility and requirements) and why these capabilities have yet to be incorporated (no one has provided a patch).

Currently, the visibility for the following xprofile fields aren’t “user” selectable:

• 1st Text Field – labeled as “Name” by default
• Single Fields – Checkbox Acceptance
• WordPress Fields – Biography
• WordPress Fields – Text Field (First Name, Last Name, Website)

In your example, “surname” as you have applied would be “WordPress Field – Text Field – Last Name” and as indicated the visibility is not “user” selectable.

As to the other xprofile fields the visibility can be set for either:

• Allow members to override – visibility is selectable by users
• Enforce field visibility – visibility is set per selection

Admin can set the visibility during creation or editing of xprofile fields that allow for “Visibility” settings, e.g., Single Fields – Text Box will have a “Visibility” metabox whereby an Admin can set the “Visibility” parameters. See BuddyPress xProfile fields administration for other information.

The xprofile field that is indicated in your screenshots is a field that cannot be removed/deleted nor can the visibility be changed. IOW, there is one xprofile field that is required by default with a default label of “Name” and this field cannot be removed/deleted nor can the visibility be changed. The BuddyPress xProfile fields administration documentation states:

It also adds a primary profile field (to store the display “Name” of your members) inside these two groups. The “Name” xProfile field as well as the “Base” & “Signup fields” xProfile field group cannot be deleted.

Correct me if I’m wrong, but it looks like you changed the label from “Name” to “Your Trade Type” which is allowed, however this field has a relationship to the “Nickname” WP profile field and the available options for the “Display name publicly as” dropdown box (both located in any given User’s WP profile page), given that the “field_id” for this xprofile field is equal to 1 (numeric one).

Hi,

Search for bp_before_signup_profile_fields , that would allow you to add content above the registration fields.

Similarly, bp_after_signup_profile_fields allows you to add content below the fields.

Hi,

Some of the answers may have to come from the Theme developer, i.e. Re-Hub theme, for example:

1) How can I configure the user profile page? There are elements I find unnecessary for my website, and I’d like to remove them: the sharing buttons, the “write a note” option, etc.

The “sharing buttons” and “write a note” options are not standard for BuddyPress and are either introduced by your theme in use or possibly from a plugin you have actuated.

Additionally, without getting into a lot of detail, depending on the template pack in use, e.g., Legacy or Nouveau, there are an assortment of template pages that can be overloaded/overridden (requres advanced knownledge).

2) Users registered on my site can publish articles using a frontend plugin, comment, etc.
However, nothing appears in the “Activity” section: even if someone has published an article, nothing shows up. Similarly, nothing appears if they leave comments, someone replies to their comment, or tags them.
Also, what does the “Favorites” button correspond to? With the theme I’m using, users can save articles as favorites, which are then displayed on a dedicated page. Is that what it’s supposed to refer to?

As to “articles“, I’ll assume these are synonymous with “blog posts“, typically these are synced to “Activities” via BuddyPress settings (wp-admin > Settings > BuddyPress) by enabling the “Site Tracking” component within the “Components” tab and enabling the “Post Comments” option under “Activity Streams” within the “Options” tab. See Post comments

As to “Favorites”, think of these as “bookmarks”, IOW, Activity items may be marked as “favorites” or unmarked as “Favorites” which will be listed within the “Favorites” tab, if marked accordingly and, yes, Favorites behave as you have indicated.

3) On the profile page, users can change their username and select a username that’s already in use (which isn’t allowed during registration). How can I fix this?

Usernames are unique and cannot be changed. In a “users” profile, the username is preceded/prefixed with the @ symbol. What may be confusing is the “Name” field which is more akin to the display name, to be more precise, it appears to be the “Display name publicly as”, which can be the same as the username or can be different from the username. What’s confusing is that there specific BuddyPress profile fields that correspond WordPress profile fields that may or may not have the same nomenclature. See Your Profile Screen – names section.

It seems like you are trying to fix something like, there can only be one user with a display name of "Alice". Rightly or wrongly, I suppose confusion abounds when a “display name” is conflated as being a “username”.

Perhaps, someone else will have a better or more precise explanation than I have provided.

go to Users – profile fields
try found message on page “BuddyPress Multilingual – have no translated fields” something like that. there is a button in the message, we press it, wait and now we can translate into string translation.
I searched for a long time and why the authors of the plugin did not include this in the instructions.

Try this in the functions.php file of your child theme. I have put 777 as filed id but you will have to put in the correct field id and the correct field name:-

function validate_required_profile_fields() {
$required_fields = [
‘field_777’ => ‘The so and so field is required.’,
];

foreach ( $required_fields as $field_key => $error_message ) {
if ( empty( $_POST[ $field_key ] ) ) {
bp_core_add_message( $error_message, ‘error’ );
}
}
}
add_action( ‘bp_signup_validate’, ‘validate_required_profile_fields’ );

Hi @ph59,

I am unable to duplicate the issue that you are reporting. The following conditions were checked and the behavior is as expected:

• sites that are configured with SSL will load https when https is used in the xprofile URL field.
• sites that are configured with SSL will load https when http is used in the xprofile URL field.
• sites that are not configured with SSL will load http when http is used in the xprofile URL field.
• sites that are not configured with SSL will show security warning when https is used in the xprofile URL field.

IOW, I’m not finding any evidence that https is being changed to http or http is being changed to https.

Are you using any plugin(s) that may be modifying how the xprofile fields would normally work?

I figured out my issue with it not displaying and wanted to put my solution here in case others have the same issue.

I have the Conditional Profile Fields for BuddyPress plugin by BuddyDev activated. For some reason, for this field only, I had to change the visibility condition to “”Show” current field If ” and saved that. It will revert back to “”NA” current field If” but it made the biography field show in the user’s profile when you go to view it as a site visitor.

Regarding the edits not saving, maybe you need to purge the cache?

Hello

I’m just curious, but what is the “select2” supposed to do? – Is this a secondary plugin you’ve got or what is the purpose of this?

The Xprofile fields are capable on its own to support multi-select, so I’m just a bit confused on what you’re trying to accomplish here and what the actual issue is?

Maybe a more detailed description would make it easier to try and troubleshoot this. 🙂

Also please note that the name field marked in the Users > Profile Fields with “(Primary)” IS the display name itself. This should be the field users use upon registration of their user – and this is also the field the BuddyPress Member Directory uses to sort content Alphabetical.

Hello again 🙂

This might start to make sense then!

First, when you translate something within the code itself (not using a translation plugin and po/mo file) it will for the most part be overridden whenever you update your WordPress / plugins that are translated. So, this might be why it doesn’t work now after the update.

I personally use a combination of LocoTranslate and TranslatePress. This is because BuddyPress activity is updated the way it is and for that reason LocoTranslate itself is not able to translate the dynamic content (like when activity updates – without the page doing so) – this TranslatePress supports.

So, for the BuddyPress content that can’t be translated correctly using LocoTranslate, I use the TranslatePress for those. Both plugins are free to use, and it doesn’t require you to purchase any expensive addons.

It’s important that you pick the right placement for your translation-files (custom, author, system). If they’re not in the right place the translation might not show up on the front-end. Also make sure you setup the settings within the LocoTranslate plugin not to override your translated files upon updating WordPress: Loco Translate > Settings > File system access > Modification of installed files & Editing of POT (template) files must be set to Disallow.

For the display name, this should be the default value it sorts by. Mine by default sorts by display name. When you go to Users > Profile Fields – you can edit the different settings from within there with the names and what is mandatory/not mandatory.

For the sorting part (or other features in the future) if it still causes issues, maybe a snippet code using a plugin like WPCode Lite might be a better solution rather than going into the code and edit it from there. In this way it will not get affected in most cases when you update WordPress, plugins and theme.

Maybe some of this can help you – if not – then feel free to keep me updated. 🙂

Sounds weird, since I’m also using the user fields (xProfile fields) – my site is translated into Danish, but my site-admin back-end it set to English. This is due to it being easier to find items in the menu when troubleshooting (hate when settings and so on is translated lol).

So seems weird to me if the translation part of it is causing the issue, since I’m also using it, but not having the same issue?

Hope you find a solution and it ends up working for you though! 🙂

Not sure if I got the option because of third party plugin I’ve got installed.

But you should be able to change this as a setting under Users > Profile Fields.

Normally you can set the different visibility settings in there, but “Name/Username” is normally fixed and can’t be changed from what I know.