BuddyPress.org

Short of giving your users extra hugs and re-assuring them that their WordPress usernames aren’t particularly private bits of data, you’re going to have to get your hands dirty. 🙂

It might be down to how the other plugin creates user accounts. Most plugins that allow sign-in using other services’ authentication systems (such as Facebook) don’t “properly” create WordPress user accounts; they use MySQL statements directly instead of using WordPress’ APIs.

This can cause problems with plugins that expect certain user record fields to be in a particular format (if some other plugin came along and just inserted something in a custom format in place). I am not saying that this is the case with this plugin, as I haven’t looked at its code, but I’ve seen this sort of thing before.

If you can create a test account and then go into your DB’s wp_users table and find your test user, and let us know what the values of the user_login, user_nicename, display_name fields are — and which one of these @mentions is using, and which one you would like it to use.

I built @mentions in the last BuddyPress release and while I’m not sure if it’s possible to get it to change how it behaves like this, understanding what you’d want different with real data from a test account will help us help you, and at worse, give a suggestion for ways we could make advanced customisations possible for this in future BuddyPress releases.

Hmm. Using get_avatar to change the class for blog comments is an interesting approach, though I guess it has pitfalls like this. BuddyPress customises the entire string, so your str_replace is probably not matching.

How about hooking at priority 12 instead of 10, and doing some debugging so you can fix up your str_replace for when BuddyPress is active? You might need two str_replace statements to handle BP and no BP, or you might want to switch to a preg_replace or something like that.

@oshimamasara7,

I translated buddypress.pot from English to Japanese.(about 80%)

Guess you translated the wrong file.
Must be buddypress.po, not buddypress.pot. And you have to compile the po file into mo.

In the header information, they’re missing keywords. You have only
“X-Poedit-KeywordsList: _;＿;_e\n”

Should be
“X-Poedit-KeywordsList: __;_e;__ngettext:1,2;_n:1,2;__ngettext_noop:1,2;”
“_n_noop:1,2;_c,_nc:4c,1,2;_x:1,2c;_nx:4c,1,2;_nx_noop:4c,1,2;_ex:1,2c;”
“esc_attr__;esc_attr_e;esc_attr_x:1,2c;esc_html__;esc_html_e;esc_html_x:1,2c\n”

1. Rename the file to buddypress-ja.po
2. Add the above keywordlist manually, with a text editor.
3. Open the file with poEdit and run “update” from source or from a blank pot file (yours contain a translation, you’ll have to get a new virgin copy)
4. Translate !

@walshfilho,

to get buddypress menus, go to dashboard > apparence > menus and open screen options (top right corner) and check buddypress.

If you can’t edit the theme, try to deactivate BR language in wp settings for english and see if it helps.

@iburnthings
Please review:

Theme Compatibility & Template Files

Try this in bp-custom.php

remove_action( 'messages_message_sent', 'bp_messages_message_sent_add_notification', 10 );

add_action is ~L. 191 in buddypress\bp-messages\bp-messages-notifications.php

@r-a-y Yes mate, you have summarized it correctly.

May i add one other important note though, this has NOT just started happening, this has been happening in buddypress since i started using it in 1.9!

I have been mentioning this issue for a while , i have tested this on 3 different live servers and a home setup using desktopserver, all with fresh installs of wordpress and buddypress alone (NO OTHER PLUGINS EVERYTIME), How many times have i tested since 1.9? well lets say its gotta be at least 100 fresh installs of wordpress all with default themes since wordpress 3.7 ish.

if you want to go look for yourself there is a perfect example of this happening at buddyboss demo theme if you log in and hit the load more button then add over 5 comments to a test status then refresh it and scroll down and hit load more again, you can do this here where you will then notice they are not collapsed .

http://www.buddyboss.com/demo/buddyboss/

@walshfilho
Whats the theme? Sounds more like the theme is the issue rather than buddypress. Have you tried activating a known theme that works with buddypress like twenty thirteen or twenty fourteen to see if the issue persists? If you can edit the theme and menus with those themes then that should tell you that your theme is at fault and you should contact that themes author for support.

@r-a-y

[off topic – If you’ve a spare moment, lol…]
re: the use of count_total

It might be a factor in this bbpress ticket re Activity entries:
https://bbpress.trac.wordpress.org/ticket/2690

https://buddypress.org/support/topic/bbpress-post-edit-causes-multiple-activity-entries/

So to summarize, the activity comments are not being collapsed when you hit the “Load More” button, correct?

If so, this sounds like a javascript event delegation bug. Once someone else has duplicated this issue, can someone please post this on our ticketing system?
https://trac.buddypress.org/newticket

Use the same credentials as you use here on bp.org.

This might not answer your question, but try BP’s built-in activity comment / blog comment synchronization feature.

To try this, login to your WP admin dashboard. Navigate to “Settings > BuddyPress”.

Click on the “Settings” tab. Check “Allow activity stream commenting on blog and forum posts” and save.

Now make a blog post and comment from the activity stream or from the blog post. Activity comments and blog comments should now be synched.

—

The alternative is this older plugin:
https://wordpress.org/plugins/buddypress-activity-as-blog-comments/

It used to replace the WP comments section with the BP activity reply system, but it’s been awhile since I’ve tested this one so it might not work any more.

As hnla mentioned, if you’re using theme compatibiliy, /wp-content/themes/our-theme/registration/register.php is the wrong file to use for your overrides. This file is for older bp-default themes. BP 2.1 made the change so only bp-default themes can use this older template naming convention.

If you only want to modify the contents of the registration template part and not the entire page template, you should copy:
/wp-content/plugins/buddypress/bp-templates/bp-legacy/buddypress/members/single/register.php

to:
/wp-content/themes/our-theme/buddypress/members/single/register.php.

Then, you should compare your older registration mods and copy them to this file.

If you want to change the entire registration page layout (header, footer, etc), check out the Template Hierarchy codex article for more info:

Template Hierarchy

I’ve never done this, but…

I believe @mention uses a member’s login name – so it is unique.

I also believe you can change that so their user_nicename is used by putting:
( 'BP_ENABLE_USERNAME_COMPATIBILITY_MODE', false );
in bp-custom.php

Note: user_login, user_nicename and display_name are all the same unless changed in wp-admin or a user’s profile. But that change only applies to display_name afaik.

So if you want the functionality of @mentions, I believe you need to expose user_login.

@[name] is set via \buddypress\bp-members\bp-members-functions.php -> bp_core_get_username() which has a filter
apply_filters( 'bp_core_get_username', $username );
You could experiment with that filter and see what breaks :}