BuddyPress.org

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.

@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 c…[Read more]

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

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…[Read more]

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…[Read more]

NB: if this is your first BP install, could you check what happens when you define the BP_LOAD_DEPRECATED to true.

Hi,

1) bbPress is not ready for BuddyPress 12 or up, you need to install and activate BP Classic backwards compatibility add-on
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 confi…[Read more]

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…[Read more]

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

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.

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…[Read more]

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.

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.

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