BuddyPress.org

Deactivate loco translate and redo what i described previously.
Search also for evtl. issues mentionned on loco translate support.

Aside there is no reason to use that plugin if you don’t translated scecificcally BuddyPress to your nedd. sv_SE.po/mo are loaded automatically.
If despite this, you use your own translation version, see how to prevent your translation to be overidden. It’s explained in one of the sticky topics on the plugin support.

Yep, we missed a bug in testing. Will be fixed in 2.6.1.1 release later today.

We’re very sorry.

Bug report is https://buddypress.trac.wordpress.org/ticket/7153

https://downloads.wordpress.org/plugin/buddypress.2.6.1.zip

You have to debug.
Deactivate all plugins except BP and try again with one of Twenty theme.
If you use a cache software, clear it before testing.

https://codex.wordpress.org/Debugging_in_WordPress

BuddyPress 2.6.1 was just released, which fixes this issue.

wordpress.org still needs to be updated, but you can grab the release here:
https://downloads.wordpress.org/plugin/buddypress.2.6.1.zip

I’m using https://wordpress.org/support/plugin/mass-messaging-in-buddypress which seems to do the trick.

maybe this might help with 2.6

Custom Front Pages for your users profiles

https://wordpress.org/plugins/buddypress-docs/

@rintusibi – If you’re referring to this fix:
https://buddypress.trac.wordpress.org/attachment/ticket/7140/7140.01.patch

This will be part of BuddyPress 2.6.1.

@infrablue,

i haven’t see your topic. Typo error in Readme is fixed.
You can download the file from here:
https://translate.wordpress.org/locale/fr/default/wp-plugins/buddypress

Thank you @henrywright

Try this fix:
https://buddypress.trac.wordpress.org/attachment/ticket/7140/7140.01.patch

If you still see some notices, please post them in this thread.

I’ve created a bug report: https://buddypress.trac.wordpress.org/ticket/7148

There are some very good easy to implement chat plugin out there as well. I use the pro version of this one. Had it set up in minutes after install and it has a widget that seems like it would fit the bill for the quick conversation you mention.

https://wordpress.org/plugins/wise-chat/

Not affiliated with them in anyway BTW

There’s already a closed ticket about this:
https://buddypress.trac.wordpress.org/ticket/4825

🙂 I don’t think it’s one of the most requested feature: Core – Chat: 2.11% (bp survey graph – 2015).

And only 34.02% of BP users activate Friend Connections.

You’ve better to ask directly the devs on Slack or to open an enhancement ticket on Trac.

@sharmavishal – No, it isn’t.

That’s more of a hacky way of fixing things. I still invite @oddreal to send me a copy of the theme so I can debug.

To really address this issue, plugin and theme developers should check out this development post for more info:
Class autoloading and what this means for plugin developers

This will be fixed in BuddyPress 2.6.1.

For now, here’s the temporary fix:
https://buddypress.trac.wordpress.org/attachment/ticket/7141/7141.01.patch

@kookidooki,

BuddyPress doesn’t handle posts, but WP. BP only mention them on the site activity.
BuddyPres doesn’t handle the post author behave. If a post has a featured thumbnail, it’s the author who added it.
If a post is shown with a default featured thumbnail, it’s the theme who add that feaure, not BuddyPress.

Globally, a post thumbnail is a theme feature. BuddyPress stopped to use his own theme since 1.7 and was endless improved since to work with about any WP theme.

Read WP codex page related to Post Thumbnail.

Hi @denis24,

it’s difficult to tell without seeing exactly what your dev really did. But from what you explain:

1) If he modified directly BP’s core file, he’s right. Core files are irretrievably deleted at each update and any change will be lost.

2) There is always a solution to make things differently. Problem now is the cost. You already paid for custom integration, now you will have to pay for building it out and reinteger it differently, so as your site and custom work can be updated.

About #1

– Hacking core files is never recommended and against WordPress best practices. BuddyPress developers follow the same rules.

– Technically, there is no valid reason to do that, especially if it concerned only a few buttons addition!

– it could simply be an argument for a rogue developer, in case of a conflict with a not tech savy client.

About #2

– updating for updating is a non sense. Not each update is usefull for your install. Same remark for security updates. This point, even if it is sensible, generally concern specific configuration.
If you are sure that you don’t use that configuration or mentionned plugin, why would you need to update ? But it is more convenient to tell clients to update, as it is faster to do that as to explain why and where and how to update.

– web technology is in endless evolution, it’s a fact. This doesn’t mean that your site should be indefinitly in progress too. You can choose to freeze it at a given point. It’s your decision at least, despite many pro & contras debates or trend pressure. One of them could be the site trafic. You won’t probably manage FB like a kindergarden site.

Finally, it’s your liberty and your decision.

I don’t think it’s an issue, but more a latency thing. The search field can be lame sometimes.

Looking for John Doe.
You search John = ok
You search Doe = ok

Doe is still in the search box. You add John after to search: Doe Joe.
Result: nothing because the user is registered as John Doe

Same if you enter to rapidly search terms: johndoe This brings nothing.

Ensure that you entered correctly the terms. And test with one of WP’s default theme if you use a third party theme.
If you have some other plugin it can be possible there is a JS conflict somewhere, but imho, no as a single term search works.

More a PBCK issue for now.

If you need absolutely this functionnality to work at 200%, perhaps try one of these plugins:

https://wordpress.org/plugins/bp-profile-search/
https://wordpress.org/plugins/buddypress-global-search/

Hi @iamsickofusernames

Check first WordPress Settings: Dashboard > Settings > Comments
then BuddyPress Settings. Dashboard > Settings > BuddyPress > Options tab > Activity Option

If you need more specific settings, you could add more conditionnals to this snippet. Eg.
if( !is_user_logged_in() ) | if($can_comment == true) etc

https://buddypress.org/support/topic/blog-forum-comments/

Thanks for the debug help, @tse11.

One of your plugins (or yourself) is using this code snippet:
add_filter( 'bp_use_legacy_activity_query', '__return_true' );

This made our strict activity permalink access check fail.

I believe the following patch will fix your problem:
https://buddypress.trac.wordpress.org/attachment/ticket/7146/7146.01.patch

Can you confirm?

@metaverso – Can you revert your changes and try my fix?
https://buddypress.trac.wordpress.org/attachment/ticket/7140/7140.01.patch

If that doesn’t work for you, can you tell me what BP plugins you are using?

@metaverso – Your solution is a quick fix, but not the right solution.

We need to see what the underlying cause is.

If someone can pass me a copy of the LMS theme for solely debugging purposes, I can find out the problem. Contact me on wordpress.slack.com (r-a-y) or via email.

– BuddyPress pages have all an ID.
– BP pages are not ordinary static WordPress page, but dynamic pages, a kind of placeholder. They have no content and are only existing to have a slug (and a ID for DB magement) for WP/BP dialog.
Eg. your-site/activity/ URL is empty when you deactivate BP.

Let’s continue with the activity page as example.

This “page” is made of different parts, which are contextually loaded on their own template. Use the activity filter to see what is all coming up on the (url/activity/) page. About 10 items which would be 10 real pages on a WP site without BP ! And that’s just default. Many plugins use also BP’s activity…

For each component, there is a loop. As long as you are in such a loop, you can call what ever belong to that component from inside this loop. And for almost each loop, you have a template.

If you want the About page (default WP page) to show up on a profile, you load it on one of the profile templates, but not on the BP member page which is the “page” who host “profiles”, but also the “member director”y. And you don’t want About apearing there, isn’t it ? 😉

If you read the codex about theme develoment and template hierarchy, you may understand how all this is articulated.