Forum Replies Created
Thanks for your feedback & sorry for the inconvenient. In your
wp-config.phpfile are you setting the
true? If so, you shouldn’t use it on a production site, I think the WordPress Site Health tool should advise you to avoid this practice.
We’ll fix this notice in 11.2.0. In the meantime, you can use this filter to disable the REST controller causing this error:
add_filter( 'bp_core_rest_api_controllers', '__return_empty_array' );
Above the All groups tab is active and all public groups are displayed. When I click on the “My Groups” tab, here’s what I get with latest WordPress & BuddyPress (and no other plugins).
If the content is not refreshed for you, try to deactivate all your plugins (except BuddyPress), rename the file
/wp-content/plugins/bp-custom.phpto something else if it exists and activate a default WordPress theme like Twenty Twenty-Two. Once done, test again.
I was able to see the error message. You should rename
/.../wp-content/plugins/bp-custom-erroring.phpso that BuddyPress does not load it. The issue is with this custom file you added. This file is using a function that is not available when it tries to (undefined function
/.../wp-content/plugins/bp-custom.phpat line 44).
You can use any file hosting service and paste a link here or DM me on our Slack if you prefer: https://make.wordpress.org/chat/
Have you tried deactivating all plugins except BuddyPress and activating a WordPress default theme like Twenty Twenty-Three to be sure it’s a BuddyPress issue?
If so, what’s your setup?
WordPress Multisite or not? WordPress version?
If Multisite how BuddyPress has been activated? Network wide, on a specific site of the network?
Finally, could you check the error_log file of your server?
Hi try to replace:
if( bp_current_user_can( 'bp_moderate' ) || groups_is_user_mod( bp_loggedin_user_id(), $group_id ) )
if( bp_current_user_can( 'bp_moderate' ) || groups_is_user_mod( bp_loggedin_user_id(), $group_id ) || groups_is_user_admin( bp_loggedin_user_id(), $group_id ) )
Thanks for your report. I agree, we should check the needed placeholders are in place inside the translated string.
Thanks for your report, it will be fixed in 12.0 version: https://buddypress.trac.wordpress.org/ticket/8820
@adhamahmed: A better place to ask about this is: https://bbpress.org/forums/
@mpcd108: interesting, we don’t include such a view, what would be the benefit of it? Being able to see the awaiting requests to be able to withdraw some?
Your error log file says
bp_get_deprecated_functions_versions()is not available. This function was introduced in version 11.0.0 of BuddyPress. I’ve just tested BuddyPress 11.0.0 using WordPress regular and multisite configs and I confirm when I try to login everything behaves as expected. I cannot reproduce your error.
When I look at your previous messages in this thread, I thought you decided to roll back to BuddyPress 10.6?
Could you please provide more information about what BuddyPress version you are using, what WordPress config you are using (regular or multisite) and how BuddyPress has been activated on your site if you are using a multisite config (eg: on the network/main site or on a subsite of the network)?
This is really weird, because:
sprintf()is not used at line 233 in https://buddypress.trac.wordpress.org/browser/tags/11.0.0/src/bp-blogs/bp-blogs-activity.php#L233. Have you edited this file?
– “3 arguments are required, 2 given”: 3 arguments were required in BuddyPress 10.6.0 and below but only for multisite configs. Are you using multisite?
– It looks like you still had 10.6 code inside 11.0 for the
– Have you kept the
bp-blogs/bp-blogs-activity.phpfile you had when you upgraded to 11.0, I’d be curious to see it.
I’ve tested everything into this area for regular and multisite configs and I can’t reproduce.
Thanks a lot for your feedback. The issue is actually caused by some custom code wrongly using the
bp_get_send_message_button_argsfilter. Instead of returning an empty array to disable the private button on members profile header, this custom code retuns
That being said. We should be more cautious about this potential wrong usage, so we’ll have it fixed asap (next minor version 11.1.0).
See https://buddypress.trac.wordpress.org/ticket/8800 to follow our progress about it.
Here’s the link to download previous version of BuddyPress: https://downloads.wordpress.org/plugin/buddypress.10.6.0.zip
FWIW, I can’t reproduce the issue you shared about notifications. For me everything works as expected, see:
Hi @drivezone, @fantamily & @yoshibot
Thanks a lot for your feedbacks. We’re going to investigate about the issues you reported.
Thanks for your report, this issue seems to be caused by this plugin https://github.com/projectestac/wordpress-invite-anyone/ It hooks to
bp_core_install_emailsto run the function
ass_install_emailsthat does not exist see: https://github.com/projectestac/wordpress-invite-anyone/blob/master/by-email/by-email.php#L1710
I advise you to deactivate this plugin, update BuddyPress and then reactivate this plugin once done. The
bp_core_install_emailshook is only fired by BuddyPress when you install/upgrade and use the tool to reinstall emails, so it should be ok. But I strongly advise you to contact the plugin author so that he fixes this issue.
Thanks for your report, I’ll check BuddyX, but I doubt issue is with this theme.
I just tested & everything behaves as expected for me. Have you tried without any other plugins activated than BuddyPress?
Thanks for your feedback. We got it and it will be fixed in next major version. See https://buddypress.trac.wordpress.org/changeset/13311/
How can I help you?
Thanks for pinging me about it @teeboy4real. I confirm what @jamesosborne replied. Webp support has been added into BuddyPress 11.0.0. Don’t hesitate to test the beta to check it will solve your issue.
I don’t think such a resistance exists.
The first thing you need to introduce a change is the will to contribute to it and we, the BP core team members, will always spend energy to make this change happen in a safe way for all BP end users.
Some can consider we failed at listening to community needs.. I personally find it very unfair and very demotivating for me and the team. I can tell you I’ve tried at many occasions to let the community tell us what they need:
– Call for feature ideas, ticket fixes etc… Only the BP core team members contributed to this call.
– I tweet, post on bpdevel.wordpress.com before each development meeting to invite people to join and raise their voice.
– I’ve organized codex documentation contribution meetings for 6 months, only the BP core team members joined these meetings : improving documentation needs a lot more contributors.
– the last time we organized a survey we got 40 replies. One need was raised : Media in BuddyPress and I am working on it.
With so few inputs, we’re trying to guess according to what we notice using BuddyPress.
I think we can close this thread: we had interesting inputs, I’ve read/listen to everyone who expressed here. Now it’s time to DO 😉.
I will soon write a post recap to share how we will schedule the making of ideas / needs you all shared with us.
Thanks again 👍
Yes we still want to change & improve BuddyPress using more features as plugins to do it smoothly. So no “reboot” 💥, but progressive changes 🐢.
Thanks for your feedback. I’m happy to read you found the “platform” that was able to match your expectations. The customer support you get is probably included into the price you pay, that’s probably the reason it’s more efficient 😉
@mike80222 According to our tests, PHP 8.0 & 8.1 are fine with BuddyPress. Each time we commit we run PHP Unit Tests on PHP from 7.4 to 8.1 see: https://github.com/buddypress/buddypress/actions/workflows/unit-tests.yml
@fawp: for the error log’s notices, it’s relative to your theme, it looks like it’s trying to get some activity information without making sure an activity loop is being processed.
For the member’s cover header issue, it will be fixed in next beta/RC release, see https://buddypress.trac.wordpress.org/ticket/8761
Thanks again for your contribution.
Thanks a lot! That’s the right place to warn us about these issues. I’ll have a look at it.
Thanks a lot for your feedback. I agree making easier for users to know about BuddyPress would be great, this is what I understand about your point on marketing (the right product, at the right time, etc..).
About documentation, we’ve tried to work on it but temporarily stopped due to the lack of contributions, here’s our last meeting summary about it: https://buddypress.org/2022/04/march-documentation-contributor-meetings-summary/
We’d be very happy if you could help us into this area, we’ve put a staging site in place. If you want to be part of this work I can create an account for you on this staging site 😉