BuddyPress.org

Not sure this will help but I just posted another way to get simular results here…

https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/different-profiles-for-different-user-types/

I’ve encounter the same requirements for a profile field to be editable only by admin that is non-editable by suscribers.
Someone could eventually commit a small plugin that allows this sort of administrative tagging.

Outside of buddypress perspective, I end up using wp_usermeta database table with a call to add_user_meta($user_id, $meta_key, $meta_value [, $unique] ) and when i need the info stored i use get_currentuserinfo()
references :
https://codex.wordpress.org/Function_Reference/add_user_meta
https://codex.wordpress.org/Function_Reference/get_currentuserinfo

Jeff, what’s the solution then? Or how do we prevent this in the future? I read the ticket, but I’m at a loss. I’m encountering this problem right now, and I had to go into phpmyadmin to correct all the user_nicename fields to remove the -2 at the end. do we simply ask people not to put spaces in their usernames?

Can you elaborate on “it crashed the site”, please?

Hey.. Ilyarogov and I are both work on the same project.

To clarify, we are creating a plugin. We will not be using the back-end as fields would be created dynamically on plugin installation.

Thanks

And why are you not simply using the backend ‘Profile Field Setup’ to add new profiles fields for users to complete, is there some particular requirement you have or is this a plugin you’re writing?

Humans always fill out required profile fields.

We should add more to the codex about profiles…. I’m tied up for a few days. If not tackled by Thursday then I’ll add a page with some text and links to questions (with answers).

Once the fields are populated by a user, they will show up within their public profile page.

Hi, I’m still seeing this issue. Not so much on the spam side, but I’ve got a field that is set to be required that isn’t actually required in order to sign up.

It’s in a 2nd group of profile fields, if that matters. Here’s the relevant code, which should be working … but isn’t.
http://pastebin.com/Gq5Ay5fH

@jvoss — are any of your fields required? If so, are they actually forcing users to fill them out?

I was able to add my 2nd and 3rd profile fields to registration, but the “required” fields can be bypassed without filling them out.

@EvanBerard ~ I hope this helps, but if not, let me know and I’ll see if I can help some more. The code is certainly not ready for prime-time but does give the ability to add profile fields for groups in Buddypress. You have to know your way around the code a little to understand what is going on though. You can see loader.php @ buddypress-group-fields.php @ http://pastebin.com/DfxwhLXU and compare it to my starting point which is the BP Group Extension API in the BP Codex @ https://codex.buddypress.org/developer-docs/group-extension-api/ to see what I’ve done, which isn’t much, but hopefully it helps you a bit! The ZIP is online for now at http://dl.dropbox.com/u/244479/buddypress-group-fields.zip if you want it but probably won’t keep that up there forever so I wanted to include the code as well.

Please don’t bump your post more than once per day, especially on the weekend.

The Base button corresponds to the Base profile fields group. There is no easy way to turn this off at this time.

There are hooks in place where form fields can be added and validated. You’d need to code it, though. Or get it coded. Just have a look through the group templates and you can find quite a few. For validation hooks you need to look in bp-groups.php.

I don’t know of anything like that at the moment and have poked around a little for it. Just curious, for your application, would it be the same profile fields for each group? Like Facebook groups have Location, Website, etc for each group but it’s the same list for each group I believe. I’ve been messing around with the Group Extension API (https://codex.buddypress.org/developer-docs/group-extension-api/) and have a basic plugin that has a few of these already pre-defined. It is certainly not very dynamic (yet) but if you have a set you need, I could send you that modified to your list, or the code changes from the base API to what I have if you’re interested in coding it yourself. That’s assuming someone else doesn’t come in and show us both a plugin that already does it which would not surprise me either

You can use xprofile fields to specify certain CSS values in the users profile. Then you can retrieve the field value in the profile and modify the profile CSS with jquery. Its a bit of a work around but it works for me. Here’s an example:

1. Create an xprofile field and name it ‘Profile Background’
2. Edit your profile in buddypress and insert ‘#000000’
3. Go to wp-content/themes/yourtheme/members/single/member-header.php
4. On the 2nd line, just after “ paste the following code:
`
$(“#wrapper”).css(“background-color”, “”);
`

This will modify the profile background color according to what ever value you put in ‘Profile Background’

This is just off the top of my head, I’ll check how I’ve done it once I’m home this evening. I will be writing a plugin for this. The only drawback is the user needs javascript enabled other wise its pointless.

To go about doing this would require fairly advanced PHP skills and experience with the BP API, it’s not a straightforward task. Not sure if anyone has attempted this, think it’s been discussed or touched upon briefly before

Not sure this does make sense though would it not result in possibly a very bloated xprofield table full of user created one off custom fields.

Try this on for size. Hackish but functional, until real exclude arguments exist (they’re coming in 1.3, I promise!) Put it in your bp-custom.php

`function bbg_disallow_name_edit( $has_profile ) {
global $profile_template, $bp;

if ( ‘edit’ != $bp->current_action || !bp_is_my_profile() )
return $has_profile;

foreach( (array)$profile_template->groups as $group_key => $group ) {
foreach( (array)$group->fields as $field_key => $field ) {
if ( $field->name == BP_XPROFILE_FULLNAME_FIELD_NAME ) {
unset( $profile_template->groups[$group_key]->fields[$field_key] );
$profile_template->groups[$group_key]->fields = array_values(
$profile_template->groups[$group_key]->fields );
break 2;
}
}
}

return $has_profile;
}
add_filter( ‘bp_has_profile’, ‘bbg_disallow_name_edit’ );`