BuddyPress.org

i notice that it is somewhat working in the latest build. I’m running it on trunk MU 2.7 and buddypress 1.0 beta. i see that some of the fields are links and some are not. i can’t seem to find a consistent behavior. anyone else seeing this?

Oy, just upgraded to 1.0b1 and still have the same problem with messages not working. Here’s what I did for the upgrade:

trial 1) overwrote all plugins with the latest releases (combo download), tested site — messaging didn’t work;

trial 2) deleted all mu-plugins, re-downloaded 1.0b1 (in case the d/l botched the first time), uploaded everything it in their proper locations, tested site — messaging still didn’t work.

I tested private messaging by doing the following:

trial 1) My Account >> Messages >> Compose >> write a message >> Send — pressing Send cleared all fields (Send To, Subject, Message);

trial 2) My Account >> Friends >> My Friends >> click on friend’s profile >> Send Message >> write a message >> Send — pressing Send cleared all fields again;

trial 3) do the same stuff as trial 2 but with a different friend — still the same problem.

Here’s the funny part, when I checked off “This is a notice to all users” the Send button did work. One other piece of information that might help troubleshoot this is that I have this text “(Use username – autocomplete coming soon)” next to the Send To label.

It will be there, I just need to link them up to the member directory search.

This was likely removed by mistake, I will add it back now. I was changing things with JS and CSS inclusion according to WP coding standards.

I am having exactly the same problem…any ideas anyone?

The basics of what I did was edit bp-xprofile.php and removed these lines:

$sql[] = “INSERT INTO “. $bp . ” (

id, group_id, parent_id, type, name, description, is_required, field_order, option_order, order_by, is_public, can_delete

) VALUES (

1, 1, 0, ‘textbox’, ‘” . __( ‘Public Display Name’, ‘buddypress’) . “‘, ”, 1, 1, 0, ”, 1, 0

);”;

$sql[] = “INSERT INTO “. $bp . ” (

id, group_id, parent_id, type, name, description, is_required, field_order, option_order, order_by, is_public, can_delete

) VALUES (

2, 1, 0, ‘textbox’, ‘” . __( ‘Last Name’, ‘buddypress’) . “‘, ”, 1, 2, 0, ”, 1, 0

);”;

Then I went into my database and deleted those fields. Once those are gone BP defaults to using the username.

Sounds good!

These values are included in the PO file. If your translation file is present upon first install – then it should store the translated values. Can someone check this? This will change, it’s not ideal.

A bit of trunk ago it worked for me…so I think you can try!

Profile data is stored in the following tables:

wp_bp_xprofile_groups – The profile groups

wp_bp_xprofile_fields – The fields, what type they are, the name etc.

wp_bp_xprofile_data – The data for each user for specific fields

Avatars are stored in:

wp_usermeta – with the meta_keys:

‘bp_core_avatar_v1’ – the URL to the avatar thumbnail

‘bp_core_avatar_v1_path’ – the filesystem path to the thumbnail

‘bp_core_avatar_v2’ – same as v1 but the full size image

‘bp_core_avatar_v2_path’ – same as v1 but the full size image

Did you set up the profile fields under site admin?

Right now the basics on the front screen are done and it is live at: http//testbp.org

If you get hold of the trunk, it was checked in last night.

I need to use the __() function on the “First Name” and “Last Name” fields so they can be translated – after which you should be able to translate them the same way you translate WordPress. For now, you can simply edit the names in the database – in the “wp_bp_xprofile_fields” table.