BuddyPress.org

May be reading this topic can help you to debug ?

Fatal error on a BuddyPress 2.6.0 upgrade

Hi,

seems same issue as the one related here (has fix).

Notifications displaying “array”

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.

Hi,
I have the same problem like “Fatal error: Call to undefined function bp_get_current_group_id() in /home/…/public_html/…/wp-content/plugins/buddypress/bp-groups/classes/class-bp-group-extension.php on line 484”. The solution given above can fixed the issue, but it is affecting when i am updating the plugin. So, how can i override this file inside the theme so that the change wont lose when i update the plugin buddypress.

@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

Update – Thanks for reporting, @demon_ru.

I’m going to edit out the contents of your topic, so we can fix this up for BuddyPress 2.6.1.

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

Testimony to good coding?

Yep ! @imath is one of BP Core Developer.

About

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.

Repair the emails via tools-buddypress

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

No idea ! Google is your friend.
I would better let my users enter country, state and cities themselve as using a huge and complicated script.
I guess also that your question is not related to BuddyPress, but only to customizing a BP feature which is not intended for multisearch at all.

See Gravity Forms or a similar plugin for this.

Maybe you could adjust the email token ?

Email Tokens

Or try one of the snippets mentionned in this discussion
https://buddypress.org/support/topic/redirect-users-to-their-notifications-after-login/

@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.

Thanks, but how to fix it not touching buddypress files, I tried use remove_filter in functions.php of theme but it doesn’t work – http://pastebin.com/mgRe4e2Q

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/