BuddyPress.org

BuddyPress doesn’t do anything with user authentication. Get it working with WordPress, and it’ll work with BuddyPress. For further advice, it’s probably worth searching the WordPress.org forums as I imagine […]

r-a-y was the person who built oembed into BuddyPress core.

There’s no limit to the number (or type) of profile fields that you can use at the same time.

Point 2. should work if you enabled the “Site Tracking” component (wp-admin BuddyPress Components)?
Point 3. is expected behaviour (assuming there is indeed more text than that warning message). Some browsers […]

Not easily* possible without changes to core. We’ve an enhancement ticket for sticky groups: https://buddypress.trac.wordpress.org/ticket/2242

Yeah, we don’t support nesting of the pages when those pages are mapped to BP components.

@r-a-y said his plugin https://wordpress.org/extend/plugins/oembed-for-buddypress/ would eventually offer this as an option.

Ok, I see. Next time I look at BP Labs, i’ll try to recreate the problem and fix it.

1) If you’re clicking on a name, there’s no point in autocomplete doing anything because you’ve already entered the name.

2) It’ll only work when *you* start typing an “@” character; I doubt the pre-fill […]

This is intentional. Until a user does something, such as log in to your site, after you’ve installed BuddyPress, they won’t be listed. Why do you want to show inactive users.

Not aware of any plugins that […]

Is this talking about when the button pre-fills the user’s name in to the text box for you?

This is more of a general question rather than a BuddyPress or a WordPress question. I would not worry about 200k. Obviously, the quicker the better. Load some of your favourite sites into […]

Right now, the forums component in BuddyPress is only used for BuddyPress Groups. These group forums don’t use the same version of bbPress that the sitewide forums do.

Are you getting the “forums not set up” […]

The bp_before_group_plugin_template action is much too late for a real redirect, because you’re already outputting HTML to send to the browser. Do it higher up the stack (before the template is rendered).

Thanks, I see. I’ve just tried recreating on a local test install of BuddyPress (no other plugins) and it seems ok. Hopefully someone else will see this thread and test, too, to check if i’m right or wrong.

Not a bug. It matches exactly how they work in WordPress posts. I think we’d need a good argument to change the behaviour.

I’m not asking you to disable it, but: IS it disabled?

Can you upload a screenshot showing a before/after?