[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).

[Mathieu Viet]

Hi @jmchez

We’ll package a 12.1.0 minor release Monday which will improve the Reset Slugs tool you can find into WP Admin > Tools > BuddyPress. This should avoid some orphaned directory page that might cause the number suffix.

If you have regular pages using the same slugs than your BP Directories, I also advise you to edit their slugs to something different.

[Mathieu Viet]

Hi @dreamscape2

If you recently updated BuddyPress to 12.0, as this plugin hasn’t been updated for years, I’d advise you to install and activate the BP Classic backwards compatibility Add-on we specifically built for these situations.

BP Classic

[Mathieu Viet]

Hi @maciejatmyshca

There was a ticket where I did some tests, imaged were showing when not logged in for me:
https://buddypress.trac.wordpress.org/ticket/9066

if it’s lazy loading I believe it’s mainly a WordPress thing as we do it in activity and for avatars only if I remember well.

[Mathieu Viet]

Hello @ceraus

BuddyPress is overriding WordPress registration URL by default so that it is displayed into your theme instead of the wp-login.php file. From previous support topics on the same subject I’ve read some users were deleting the registration page BuddyPress was created to force the use of the WordPress registration page. This was a workaround that is not doing the trick anymore in BuddyPress 12.0.0.

Please see: https://buddypress.org/support/topic/buddypress-12-0-0/page/8/#post-332709 for a way to disable the BP Registration flow.

[Mathieu Viet]

For readers information: a ticket to track the above was opened here https://buddypress.trac.wordpress.org/ticket/9066

Using BuddyPress 12.0 on a regular config of WordPress is not blocking images, there’s probably a plugin/theme/custom code conflicting with BuddyPress on your specific config.

[Mathieu Viet]

Hi @roberthemsing

Making the BuddyPress registration flows « deactivable » is something we’ll think of during next major version. In the meantime using this gist I was able to disable it.

[Mathieu Viet]

@roberthemsing

Ouch, pretty annoying! Thanks for reporting it. I’ll check it asap. In the meantime, what happens if you go to Settings > BuddyPress > URLs and change the slug for the Register panel to sign-in for example?

[Mathieu Viet]

Hi @beoogo

Sorry to read about your issue. If you get a blank page that’s probably due to a fatal error. Your host should give you access to the error log of your site to find the issue. My guess is one of your plugin is using a deprecated function. If you’re trying to activate version 12.0.0 of BuddyPress, you can try to first activate the BP Classic backwards compatibility add-on.
If it doesn’t solve the issue or if you’re using a previous version of BuddyPress, add this constant to your wp-config.php file:
define( 'BP_LOAD_DEPRECATED', true );

[Mathieu Viet]

Hi @roberthemsing

What you describe is the typical behavior you get when you try to reach the registration page while you already logged in. Did you make sure to log out before trying to reach this page ?

[Mathieu Viet]

Hi,

Try to go to WP Admin > Permalinks and simply click on the save button to refresh your permalink settings

[Mathieu Viet]

Hi @clipcash

I have no idea, I’ve just searched our entire codebase and we’re not using such an error message. That’s probably a message generated by another plugin.

[Mathieu Viet]

Hi @lmstearn

To me it’s a bbPress issue. I believe there’s already one on bbPress Trac.

The workaround I posted here: https://gist.github.com/imath/24fdfa1b8625477e93c0daa0d90b2a44 is the way to go imho.