[Mathieu Viet]

I confirm the issue, it will be fixed very soon:
https://buddypress.trac.wordpress.org/ticket/9248

[Mathieu Viet]

Activity favorites really need improvements, I agree. I’ve suggested many ways to do so but haven’t succeed to convince the team. Here’s my last attempt about it: https://github.com/buddypress/buddypress/pull/238

I’m not sure what you call “Notification” is an item of the Notifications component, as you can always mark as read notifications going into the corresponding profile page.

I guess what you call “Notification” is the amount of favorited activity that is added to nav items.

We’re aware of the issue but haven’t found the best way to deal with it.

[Mathieu Viet]

Thanks for your feedback, you’re right it should only load newest activities about the specific group. I’ll look at it asap.

[Mathieu Viet]

Hi @capexpe

I believe we’ve improved this part actually in 14.0, see https://buddypress.trac.wordpress.org/changeset/13936.

You shouldn’t put your custom language into /wp-content/languages/plugins because it will be replaced by the official translation after it has been updated by the Polyglots team.

Custom language files for BuddyPress should be in one of the locations we are looking for:
– /wp-content/languages/plugins/buddypress
– /wp-content/languages/buddypress
– /wp-content/languages

More informations are available from this documentation page: https://github.com/buddypress/buddypress/blob/master/docs/user/advanced/texts.md

I’ve just tested renaming “Groupes” with “Expé” in custom fr_FR translation files I’ve included in the /wp-content/languages/plugins/buddypress folder:
– /wp-content/languages/plugins/buddypress/buddypress-fr_FR.po
– /wp-content/languages/plugins/buddypress/buddypress-fr_FR.mo

And it’s behaving the way it should, see screenshot below:

@adjunkten I have no idea how Loco translate deals with translation files, but if you put their generated alternative language files at one of the three locations I listed above making sure they respect the WordPress default way of naming these, it should also fix your issue. Here’s the translated message for the “members-only” login page.

[Mathieu Viet]

Hi @oumz99

Thanks for this information. There’s no competition to me. BuddyPress is free & open source. Nobody gets any money in the BP Team. We contribute to BuddyPress and are doing our best to build great quality software because we love the community and we value the global interest over personal profit.

I think users should see this declining rate the other way around. This won’t happen but imagine the freedom they would lose if this BuddyPress fork was the only way to build communities in WordPress.

We are very lucky to have a completely free way to meet online inside WordPress sites: let’s protect this freedom and care for it 😍.

[Mathieu Viet]

A lot! 🍕 😁

[Mathieu Viet]

I also tested with Playground and it’s behaving as expected for me: clicking on the join button from the groups directory is adding the member to the group.

Here’s the link to test:
https://playground.wordpress.net/?blueprint-url=https://raw.githubusercontent.com/buddypress/buddypress/master/tests/blueprints/14-0-0-RC1.json

[Mathieu Viet]

Hi @koka777

Thanks for your feedback. I just tested and wasn’t able to reproduce.

Theme: Twenty Twenty-Four
BP Template pack: Nouveau & Legacy (tested with both template packs)
No other plugins than BuddyPress
No custom code into wp-content/mu-plugins or wp-content/plugins/bp-custom.php

I created a public group being logged as an Admin.
I created a subscriber, logged in as this subscriber, went to the Groups directory, clicked on the join button.
Result: the join button turned into a leave button and I was successfully added as a member of the group.
I created a group being a subscriber, logged out then logged in as an Admin. I was also able to join a group from the Groups directory.

Can you explain just like I did above, the steps you are doing to get the “Error joining this group.” message?

Please make sure to deactivate any plugins, custom code, and activate a WordPress default theme like Twenty Twenty-Four.

[Mathieu Viet]

Hi @wackao

Not yet, this is something we plan to work on: https://buddypress.trac.wordpress.org/ticket/1058

[Mathieu Viet]

Hi @koka777

You can add a buddypress.php template to your active theme directory, if this template is available it will be used instead of the page.php one.

[Mathieu Viet]

Hi Hana (@arjani1)

I just tested with latest WordPress (Twenty Nineteen theme) & only BuddyPress 12.4.1 as the active plugin and I can’t reproduce your issue, see screenshot below:

– There’s an avatar in the header
– The menu to change avatar is available & behaves as expected.

So to me it’s not relative to 12.4.1.

[Mathieu Viet]

Hi,

I will soon package a new maintenance release. I was a bit too much conservative during the Output escaping review I did to build the 12.4.1 security release.

I apologize. Thanks in advance for your understanding.

[Mathieu Viet]

Hi

Thanks for your feedback. I just checked. I confirm it’s behaving as expected, see screenshot below:

Please note this feature is only available in “Modern” BuddyPress, meaning if you activated the BP Classic plugin, it’s not available.

[Mathieu Viet]

Hi @windhillruss

Sorry to read you’re facing this issue. It should be resolved in next BuddyPress minor version. See #9108. If you are using a staging site (cloning your production site config), don’t hesitate to test the fix to be sure it’s also the case for your site’s config.

[Mathieu Viet]

Hi @pachat,

If one of your plugin or your theme is hooking to bp_uri then it means it’s not ready yet for BuddyPress 12.0 & up. For these situations we are making available a backwards compatibility add-on I advise you to install & activate:

BP Classic

[Mathieu Viet]

Hi @awol

Sorry to read about this issue. Have you checked deactivating all plugins but BuddyPress, activating a default WP Theme like Twenty Twenty-Four, and removing any custom code like wp-content/plugins/bp-custom.php or wp-content/mu-plugins/*.php ?

[Mathieu Viet]

Hi @gomle

Thanks a lot for your feedback. About Notifications, I believe using the Notification Web API can improve your “pulling the user to the site” need.

Hi @oumz99

I agree we should look into import/export. To comply with GDPR, users can export the data they created on the site from their profile settings. But a more global tool would be great to easily develop BuddyPress themes or move community generated content to another site.
See & contribute to it there: https://buddypress.trac.wordpress.org/ticket/1058

Hi @bclaim

So do I! I totally agree with you. We need to rethink the Private Messages component/feature with the goal:
1. to make it a chat like system for member(s) to member(s) discussions as well as between group members discussions. What are channels in Slack could be groups in BuddyPress Private Messages. I’m looking carefully to the Block Editor live collaboration system as it may help us to reach this goal.
2. to move the Community wide notice feature outside of it.

@priyam1234
It should be the case. So it’s not an evolution to me but more a bug. I’ll look into it.

@everyone:
I’ll make sure to talk about it with other members of the BP Core Developers team during our next development meeting.

Here’s my 2 main wishes for 14.0.0:
– Review our different registration flows and allow Administrators to easily disable these BuddyPress registration flows.
– Build new BP Blocks along with a new BP Blocks only Theme to start using the WP Site Editor to customize our community area.

[Mathieu Viet]

Hi @arielcrawford

Sorry to read about your issue. When you say you updated, if the BuddyPress version you were using before the update was < 12.0, then have you tried to install and activate BP Classic?

BP Classic

Have you tried to deactivate the Learndash integration you mentioned to see if these profile pages were back once done ?

If none of the above worked, can you try to add define( 'BP_LOAD_DEPRECATED', true ); into your WP-config.php file to see if some of your plugins are still using deprecated functions (we only load back to 2 previous versions of BuddyPress otherwise).

Best to be sure to narrow the possible causes is to deactivate every plugin but BuddyPress and to activate a WP bundled theme and then reactivate everything one by one to see what plugin/theme is conflicting with BuddyPress.

[Mathieu Viet]

Hi @hossin0241

Thanks a lot for sharing your expectations. We actually built a bridge between our xProfile component and regular WP user fields in version 8.0. Here’s a developer note we wrote about it, I believe it can help you reach your need.

[Mathieu Viet]

@emaralive Thanks for alerting me about this issue.

@kioubizin using BP Classic is the way to go with your config. The issue you get with the WP legacy widgets Admin Screen is due to the Latest Activities BP Legacy widget that comes with the BP Classic Add-on.

I’ll fix it asap and build a new minor release for it. In the meantime I believe you can get rid of the issue adding this code into your theme’s functions.php file.

remove_action( 'bp_after_setup_theme', 'bp_classic_template_pack_includes', 1 );

[Mathieu Viet]

Hi @portalciencia

Some plugins might not be ready with BuddyPress 12.0 or up. For this case we’ve built a Backwards compatibility Add-on. You can try to download and activate it to see it it’s fixing your issue:

BP Classic

[Mathieu Viet]

Hi @priyam1234

Thanks for your feedback 😍. My company has nothing to do with WordPress actually, I don’t make a living with code. I’m a hobbyist and contribute freely to BuddyPress, just like the other members of the team.

For everyone reading this topic:
Quick update about the 12.1.1 issue reported by @manni65929 when first installing BuddyPress with this version:
We’re actively working on it, I’ve tested the fix we built with various scenarios to make sure we don’t generate side effects. The ticket we use to track this issue contains a 12.2.0-beta version with this fix, we still need to run some tests but I’m confident we’ll be able to package the next 12.2.0 minor release very soon (I believe early next week).

[Mathieu Viet]

Hi @priyam1234

I’m aware of the issue, see: https://buddypress.org/support/topic/buddypress-12-1-1-maintenance-security-release/

I’m currently working on it from https://buddypress.trac.wordpress.org/ticket/9075. I need to make sure the fix is taking care of all possible cases, which means a lot of tests.

As soon as I have something solid I’ll package a new minor release. It will happen faster than 12.1.1 (which took a month). I hope I’ll make it happen early next week.

@ayayron sorry to read about it: please do participate to our beta testing period. We extended 12.0.0 to 5 months without receiving any issues from you or other Themeforest developers. It’s better to anticipate imho.

@roberthemsing I’m not sure, my guess is we’re not strict enough about the rewrite rule so I’ll need to review this asap.

I’m going to close this topic, please carry on giving us your feedbacks and issues from this topic:

BuddyPress 12.1.1 Maintenance & Security Release

[Mathieu Viet]

NB: if this is your first BP install, could you check what happens when youplease define the BP_LOAD_DEPRECATED constant to true to load 12.0.0 deprecated functions. We missed this case and will fix this issue asap.

[Mathieu Viet]

Hi,

1) bbPress is not ready for BuddyPress 12 or up, you need to install and activate BP Classic backwards compatibility add-on

BP Classic

2) it looks like you’re skipping deprecated code from being loaded, please make sure you don’t have the BP_IGNORE_DEPRECATED constant set to true.

If 1 & 2 doesn’t change anything, please describe your configuration in details :
Multisite ? How BP is activated (network or a specific site).