BuddyPress.org

Deactivate all plugins and the theme and test registering from WP using a Twenty theme as first.
Then activate BP and re-test.
Then activate S2 or whatever you use for paid membership and again, test.
And finally, you have to test your theme (if not a Twenty one).

FYI, BuddyPress doesn’t handle the password field, but WordPress.
You’ll probably get better answers on WP or S2 support forum.

Do you set up pretty permalinks ?
If you trashed pages, clear them definetly.

Give details about used plugins, theme, server type and php version.

Don’t hack core files. (never !) Which language do you use ?

Where have you done this ?
I’ve took a look at the files and found out that the working ones are using __( "Foo %s", "buddypress" ) and the wrong ones are using _x( "Foo %s", "Blah blah blah", "buddypress" ).

Actually all BP strings are working. If you need custom translation, you have to do that in po/mo and to use preferably the original strings. For example, if you build a template and want to use the notification count on it, you copy the original string to your work. If you don’t do that, you nedd 2 po/mo ! One for BP and one for your custom work. Which is certainly not the best and easiest solution.

The notification count is defined in wp-content/plugins/buddypress/bp-notifications/classes/class-bp-notification-component.php

The counter itself is inside a span and is defined separately.

/* translators: %s: Unread notification count for the current user */
_x( 'Notifications %s', 'Profile screen nav', 'buddypress' ),
sprintf(
	'<span class="%s">%s</span>',

The bla bla bla part you mention is a comment for translators who indicates him the context. This comment appears in the pot file like: Notification %s [Profile screen nav]

That’s BP’s default coding. You haven’t to modify this. Use it as is.

If you have difficulty to translate such a string, you have to check your theme or any custom function you added (by hand or another plugin).

The corresponding custom string should reflect the original one as gettext function wouldn’t translate a string which is not identic.

__( "Foo %s", "buddypress" ) and _x( "Foo %s", "Blah blah blah", "buddypress" ) are both working, and do technicaly the same thing (foo = something) which let you modify “foo” in both case, but as the original string is _x( "Foo %s", "Blah blah blah", "buddypress" ), you couldn’t replace it with __( "Foo %s", "buddypress" ). It is the translation prefix (_x or __) which is the important thing here.

Hope to be clear. And you’re right, unfortunately your changes will be overwriten at next BP update as you hacked core files.

This could be a CSS issue. Which theme are you using?

Hello,

I have the same problem here. I use WP 4.5.3 and the Theme Woffice from ThemeForest and BuddyPress 2.6.2. I translate all with the plugin Loco Translate but some translations are not working. There ist nothing to repair. What can I do? Any idea?

Best regards

Marco

The BuddyPress Plugin doesn’t apply any style when you hover over a suggested @mention. When using a default WP theme (which is what the BP developers base their testing on) there is no hover effect on the suggested username. Which indicates that it is probably something in the style of the theme you are using that is applying this additional effect.

The quickest way to see if it’s the theme or not, is to quickly change themes to one of the Twenty-xx themes that are packaged with WordPress, and if the hover effect disappears, you know where the problem is.

That’s only part one. The next part is to figure out where in the theme the issue is and patch it.

This might be helpful: https://www.studiopress.com/using-firebug/

Are you seeing the same thing in one of the WP default themes? That looks like a CSS issue within your theme. You’ll need to use a web inspector (like Firebug or the Inspect Element option in browsers) to sort out what the offending CSS code is. By default I don’t see any hover actions in Twenty Thirteen.

Can you share a link?

BuddyPress doesn’t affect user authentication or password resets. We leave that to WordPress.

WordPress’ lost password link can be found on the .com/wp-login.php screen. You can copy that link into your theme/navigation menu, etc, if you want it elsewhere.

‘#signup_username { border: green !important; }
#signup_email { border: yellow !important; }
#signup_password { border: blue !important’ }
#signup_password_confirm { }
ul.reg_groups_list_multiselect { }
#field_1 { }
#field_4 { }
#field_7 { }
#field_5 { }
#field_6 { }
iframe { }`

field 1 = name
field 4 = city
field 7 = age
field 5 = facebook
field 6 = other profile
iframe = about me

You may be able to write this without !important but if you can’t apply that to provide almost absolute over ride to existing and troublesome styles in your theme.

We’d need to see your theme’s markup in order to provide you with the relevant CSS help. Do you have a link to your website?

Get in touch with the chinese translation team:

Translation Teams

You don’t need to download GlotPress, you can translate BP online. Just go to https://translate.wordpress.org/projects/wp-plugins/buddypress/stable/zh-cn/default and log-in.

And read the translators handbook to learn more about translating WordPress, plugins and themes.

If you prefer to read in chinese, see here: https://cn.wordpress.org/

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.

Custom code for BP is generaly added to bp-custom.php.

Have you tried to adjust the size via child theme’s CSS ?
Some examples here: https://en.support.wordpress.com/custom-design/custom-css-media-queries/

You don’t need that plugin.

Instead, try this in your theme/functions.php or in bp_custom.php

function lisa_remove_xprofile_links() {
    remove_filter( 'bp_get_the_profile_field_value', 'xprofile_filter_link_profile_data', 9, 2 );
}
add_action('bp_setup_globals', 'lisa_remove_xprofile_links');

There is info on this codex page about replacing the default cover css.

I have the same issue … using the latest bbpress 2.6.2 along with latest wp install and using GameDayTheme.

Having issues with pending users list……

I am currently using the GameDay theme and after installing buddypress I now have two pending lists when I go to my users. this is causing issues with my registration process. I tried switching themese and still have pending link show up twice.

I have attached a screenshot here.

I also have deactived all other plugins except buddy press.

Can anyone help point me in the right direction as to what would be the cause here ?

Many thanks in advance

Having issues with pending users list……

I am currently using the GameDay theme and after installing buddypress I now have two pending lists when I go to my users. this is causing issues with my registration process. I tried switching themese and still have pending link show up twice.

I have attached a screenshot here.

I also have deactived all other plugins except buddy press.

Can anyone help point me in the right direction as to what would be the cause here ?

Many thanks in advance

The debug notice is telling you that the problem is with the rehub theme.

The rehub theme is calling is_user_logged_in() too early. They should preferably make their login user checks on the 'init' hook. Pass this info to the rehub theme author.

If you’re seeing these notices on a production site, you can turn off these notices by setting WP_DEBUG to false in wp-config.php.

The Notifications %s string looks like it is available:
https://plugins.svn.wordpress.org/buddypress/tags/2.6.1.1/buddypress.pot

If you’re using a custom translation from a previous version, you need to merge your language files together. Here’s a quick tutorial I found on Google:
http://www.marketpressthemes.com/blog/how-to-merge-two-po-files-using-poedit/

You might also benefit from a translation that is already available here:
https://translate.wordpress.org/projects/wp-plugins/buddypress